Accessibility Awareness

Accessibility Awareness's avatar
Accessibility Awareness
npub1xjxf...xuhx
Helping you better understand web accessibility for people with disabilities, whether you're a student, teacher, journalist… whomever! Run by @patrickmgarvin
When creating PDFs, avoid using "Print to PDF." A screen reader user may still be able to access the text of PDFs created this way, but heading structure, alternative text, and any other tag structure will be lost. Using "Save As" or "Export" can preserve these tags.
Don’t stuff your alt text with keywords without context. If your alt text is just a collection of keywords, it will just sound like a gibberish string. It won’t describe what’s actually in the image, and won't help a blind user get a context or content of the image.
Audio descriptions are necessary for making videos accessible. They narrate the crucial visual elements that would be necessary for understanding the plot without the ability to see the screen. They describe non-verbal cues like gestures, facial expressions, or eye contact.
Some are suggesting you deliberately write inaccurate or confusing alt text, because they say this confuses AI scrapers that are analyzing images. The purpose of alt text is to help people who cannot see the image. Deliberately misrepresenting the image is a gross misuse of alt text. Don't do it.
For screen readers to recognize headings, heading text can't just be body text or normal text that's been made to look bigger and bolder. It must be formatted as a heading. In Microsoft Word and Google Docs, this can be done in the styles box. In HTML, use the tags h1 through h6.
You don't necessarily need to say "image of" in your alt text for users to know it's an image. Screen readers will announce that it's an image. But it can help readers to specify if it's a hand-drawn image, Polaroid, infographic, screenshot, chart, map, diagram, or so on.