100 Days of A11y

Day 98: WCAG and Hearing Impairments

Published on

Yesterday's learning about how WCAG benefits people with visual impairments pushed me forward into more WCAG overview to see how it benefits people with hearing impairments (deaf and hard of hearing). Deafblind benefit from using the combined design techniques of visually impaired and hearing impaired.

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"

Tips from Giles Colborne's book Simple and Usable (as quoted in Web for Everyone:

aria-describedby and aria-labelledby WILL access content that is inside a container hidden using aria-hidden="true".

aria-labelledby, aria-describedby, aria-label, and hidden text are some ways to let a screen reader user know of current page. Or use aria-current="page" which has some support.

The following lists target WCAG success criteria that benefit people with visual impairments. The main concern for hard of hearing is to provide text or sign language alternatives to any sound provided.

Level A

Permalink for "Level A"

Level AA

Permalink for "Level AA"

Level AAA

Permalink for "Level AAA"