Web Accessibility principles Flashcards
Name the 4 principles in WCAG
Perceivable
Operable
Understandable
Robust
You have to be able to PERCEIVE web content through at least one of your biological senses. Which 3 senses are important as it is know?
Sight
Sound
Touch
When can you use ARIA?
To make dynamic interactions accessible, for example to announce when a tab is “expanded” or “collapsed”
When should you use ARIA Live?
To announce new content.
If new content is injected into a page — such as an error message or a confirmation message — blind users need to hear this new information.
Describe PERCEIVABLE
Make sure your users know what’s on the web page.
This means making the content and functionality available through sight, sound, and touch.
Digital text — whether visible or hidden (using valid accessibility techniques) — is the most universal method of accomplishing the broadest perceivability.
Describe OPERABLE
And name some of the devices
Operability is about making the input methods of web content functionally available to a wide range of input devices.
- mouse or touchpad
- keyboard
- touchscreen
- voice recognition software
- other specialized input devices (most of which emulate the keyboard or mouse)
Describe OPERABLE using:
- into
- within
- through
- out
You have to be able to navigate into web components,
use the features within them,
navigate through them,
and navigate out of all of them,
No matter what input device you’re using.
Why is keyboard access so important to achieve?
If you can use web content with a keyboard and with a mouse, chances are very high that you can use it on most every other device. There are exceptions, as you might imagine, but those exceptions are uncommon.
Two important aspects to make web content OPERABLE (Keyboard access is not the answer here)
- Keyboard/programmatic focus
- Timing, enough time to interact with the content
How could you make the content UNDERSTANDABLE?
- Specify language
(for example: <html lang="en">) - Simplify the Reading or Vocabulary level
- Limit or Avoid Terminology or Concepts that are Unfamiliar or Complex
- Provide Supplemental Formats. Some people can’t read at all. Provide alternative formats, such as images, audio, or video (Accessibility guidelines don’t require).
How could you make Interfaces and Interactivity UNDERSTANDABLE?
- Consistency and Predictability
(Web sites with multiple pages or views should maintain a consistent look and feel - links, navigation, form control…) - Provide Instructions, Hints, and Contextual Help
- Provide Feedback with Confirmation and Error Messages
Why is ROBUST important?
Robustness is about ensuring compatibility with a broad range of user agents (browsers and other web devices), including assistive technologies.
The best way to make the code ROBUST?
- One of the best ways to increase the likelihood of robust markup and code across user agents is to use standard markup.
- Use ARIA (or other means) to Indicate the Name, Role, and Value of Interactive Components
