Understand web accessibilityModule 1 of 4 · 0 done
Why accessibility, and how WCAG works
Who you’re designing for, the POUR principles, and how to read WCAG success criteria without drowning.
By the end you’ll be able to
- Describe permanent, temporary and situational disabilities
- Explain POUR
- Find and read a WCAG success criterion
Who benefits
The WHO estimates about 1.3 billion people — one in six — live with a significant disability. Add temporary (a broken arm) and situational limits (bright sunlight, a noisy train, a baby in one arm) and accessibility affects everyone at some point.
POUR
WCAG organises everything under four principles: Perceivable (people can sense the content), Operable (they can use the controls), Understandable (they can follow it) and Robust (it works with assistive technologies).
- Level A: the minimum
- Level AA: the usual legal and policy target
- Level AAA: enhanced; not required everywhere
Reading a success criterion
Each criterion has a number (e.g. 1.4.3 Contrast Minimum), a level and a testable rule. The “Understanding” document explains intent and examples — read it whenever a rule seems arbitrary.
Experience barriers firsthand
Spend 30 minutes using sites differently.
Deliverable: A barrier log mapped to POUR and WCAG criteria. Add it to your skills passport as a project when it’s done.
Check your understanding
Answer 3 scenario questions. Get 2 or more right to complete the module.
See how your wcag & principles scores
A free test adds WCAG & principles to your skill report and shows how close you are to the 75% job-ready target.