100 Days of A11y

Day 97: WCAG and Visual Impairments

Published on

Yesterday's learning about how WCAG benefits people with cognitive disabilities inspired me to look over WCAG again to see how it benefits people with visual impairments (blind and low vision).

Things I accomplished

Permalink for "Things I accomplished"

What I reviewed today

Permalink for "What I reviewed today"

What I learned from it

Permalink for "What I learned from it"

The support among screen readers is better for the simple two-letter language codes (like "en" for English) than for the localized language codes (like "en-au" for Australian English).

Screen readers list forms only if marked as role="form" (the <form> element will be ignored in landmark lists).

The name of a link is calculated as follows (in order of precedence by screen readers):

  1. aria-labelledby
  2. aria-label
  3. Text contained between the opening <a> and closing </a> elements (including alt text on images)
  4. title attribute (note that this is considered a last resort method for screen readers to find something; it should not be considered a primary technique for giving names to links)

If headings have images, the alt text will be show up in the headings list. Linked images (whether HTML img or CSS background image) can be assigned aria-label or aria-described by. Spans can hide extra meaningful content for screen readers. All these alternatives make me wonder how that impacts people with cognitive disabilities or people who use speech recognition. It's so important to design for more than one disability.

There are so many success criteria for this disability, compared to cognitive disabilities, but I imagine that's because it is more objective and measurable. The following lists target WCAG success criteria that benefit people with visual impairments.

Level A

Permalink for "Level A"

Level AA

Permalink for "Level AA"

Level AAA

Permalink for "Level AAA"