Congratulations!
You've mastered this deck.
What is the capital of France?
What is 2 + 2?
(Click to flip)
Paris
4
Card of
| Design Consideration | Why? |
|---|---|
| All content must be presented in text or via a text equivalent (e.g., alt text for images or other non-text objects). | Screen readers cannot read non-text content (e.g., images) directly, but they can read alt text that you provide. |
| Information must not be conveyed by visual attributes alone (e.g., color, spatial location, thickness of text, background highlighting, etc.). | Not all visual information is available to screen readers. Even the visual attributes which are available to some screen readers, such as text color, are typically not announced by default. |
| All functionality must be available using only the keyboard (Note: be sure to test with the screen reader turned on, because there are subtle differences in keyboard behaviors when the screen reader is on). | |
| The content must use markup with good structure and semantics (headings, landmarks, tables, lists, etc.). | |
All custom controls (e.g., expand/collapse buttons, media player volume control, dialogs, etc.) must have the correct name/label, role (either with HTML or with ARIA), and value, and must change value when appropriate (e.g. aria-expanded="false" changes to aria-expanded="true" after activating the button). | |
| Users must receive immediate feedback after all actions, via their screen reader. Silence after activating a feature is always bad! | |
| Videos require audio descriptions (additional narration of visual content) if the video’s original audio track (dialog, sounds, narration) does not explain everything that a person who is blind would need to know to understand the video. | |
On mobile devices:
|