Issue: A screen reader will try to “sound out” hashtags or handles that run together. The result can sound like gibberish. All-lowercase hashtags can also be misunderstood by on-disabled users.
Who’s affected: Screen reader users, people with cognitive disabilities
WCAG standard: Guideline 3.1.2 – Readable: Language of Parts
What to do: Use camel case on Continue Reading »
Issue: Google Sites are free to use, but keyboard navigation is difficult to impossible when site structure is more than a couple of layers deep.
Who’s affected: People who navigate by keyboard (hand mobility disabilities), people who use screen readers
WCAG standard: Guideline 2.1: Keyboard accessible
What to do: Avoid using Google Sites when possible. Continue Reading »
The WebAIM color contrast checker includes an eyedropper tool that lets you sample colors from a graphic or image before you upload it to the web. Use it to make your graphics accessible before you finalize and share them.
Color contrast ratio comes from comparing the relative luminence of the foreground and background colors. The Continue Reading »
Checking that a page can be navigated without a mouse is one of the easiest accessibility tests you can do. It ensures that people who need to – or prefer to – navigate the web with their keyboard can get to the functionalities they need.
Issue: If you don’t use meaningful language in your header and set your top row (and your left column if applicable) as a header, a screen reader will read your table from left to right, line by line and the listener will lose all context for relationships between headers and data.
Who’s affected: Screen reader Continue Reading »
You’ll hear a lot about making things accessible to screen readers, and it might make you wonder if we care about people with disabilities who aren’t blind. It’s true that screen readers, which parse through a web page’s underlying code and speak the content out loud, are critical to helping people with visual impairments use Continue Reading »