Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll
Well done!
You have completed Accessibility for UX Designers!
You have completed Accessibility for UX Designers!
Preview
People with disabilities must be able to understand your content and use your interfaces.
WCAG Understandable Principle
- Set HTML language attribute
- Use plain language
- Create predictable navigation
- No unexpected changes in context
- Make errors easy to spot and correct
Vocabulary
- Change in context: To avoid disorienting users, the following should happen only when the user initiates a change by interacting with an interface element:
- opening a new window
- loading a new page
- significantly rearranging page content
- moving focus to a new component.
Resources
Related Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign upRelated Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign up
understand your content and
use your interfaces.
0:00
The understandable principle
is broken into three guidelines,
0:00
beginning with one called readable.
0:04
The level a requirement
is pretty simple.
0:07
Developers should set an appropriate
language attribute, so
0:11
screen readers know what
language to expect and
0:15
what accent to use in
pronouncing page content.
0:19
In the example shown here, the document's
primary language is English.
0:23
But this particular paragraph asks
the screen reader to switch to
0:29
You need to sign up for Treehouse in order to download course files.
Sign upYou need to sign up for Treehouse in order to set up Workspace
Sign up