Hi! My team creates web documentation on how to use software. These are step-by-step instructions that include screenshots of the appropriate area of the User Interface directly underneath each step in the text instructions.
I want to make sure we are using the appropriate alt text for these screenshots.
Should we mark these screenshots as decorative so that screen readers skip them? Since the text instructions are explicit and can stand alone, it seems like the alt text for the accompanying screenshots could be redundant and annoying for somebody using a screen reader.
That said, I also imagine those with low vision might be confused as to why the screenshots are being skipped.
Thanks for your advice! And, if the answer is to use alt text, how might it be best written? Should we write “Screenshot of XYZ Process from XYZ View?”
zersiax2 points2y ago
I'd say use the alts, but keep them brief. " Screenshot of Settings window" or " screenshot of settings window with "General" highlighted" or some such.
A more important thing is to try to keep in mind what screenreaders call a particular control. If a button has a play button icon on it but is called Run by a screenreader, pressing the play button may not always be accurate.
macmutant2 points2y ago
I agree with this approach. If the text instructions are comprehensive, a brief but descriptive alt tag for the image makes sense. This is how. we do it at the large public organization where I work.
beeabeja [OP]1 points2y ago
Thank you for taking the time to answer! I appreciate the advice.
VI_Shepherd1 points2y ago
If you already haven't, look up the WCAG 2.0/2.1 guidelines for what you need to do.
beeabeja [OP]2 points2y ago
Thanks! We have referenced it quite a bit, but it’s great advice nonetheless. We work at a university with an accessibility office, too. Every resource we’ve uncovered (including Reddit) has been helpful in our research as there doesn’t seem to be a cut and dry answer anywhere for this particular kind of screenshot. Thanks again!
CloudyBeep1 points2y ago
I quite like the way Apple describes screenshots in their user guides. Use a screen reader or view the source of the webpages to get an idea of what they do. To avoid the issue of screen readers having different labels of controls, whenever users are instructed to tap or click something, a visual representation of the thing is provided for sighted users, and the alt text of that, which is what VoiceOver would read it as, is also provided.
beeabeja [OP]2 points2y ago
This is good feedback, thank you. I’ll explore Apple’s approach.
Our mission is to provide everyone with access to large- scale community websites for the good of humanity. Without ads, without tracking, without greed.