What the standard is, which version applies, and how the levels translate into design decisions.
Accessibility · Standards
WCAG in practice, assistive technology and inclusive defaults
Accessibility
Requirements mapped to the decisions that produce them, written for designers rather than auditors.
20 entries across 6 categories
Accessibility19Workflows1
Type
Category
Level
20 entries
Everything must be operable with a keyboard alone, which is the single most load-bearing accessibility requirement.
Accessibility · Operable
The visible marker showing where keyboard focus is, which must never be removed.
Accessibility · Operable
Deliberately moving focus when the interface changes, so keyboard and screen reader users are not stranded.
Accessibility · Operable
Software that reads the interface aloud, navigating by structure rather than by layout.
Accessibility · Perceivable
Headings are the table of contents screen reader users navigate by, so levels must follow structure rather than appearance.
Accessibility · Perceivable
The text equivalent of an image, which depends on the image's purpose in that specific context.
Accessibility · Perceivable
What assistive technology announces for a control, which must match what a user would call it.
Accessibility · Robust
Telling assistive technology that something changed, when focus did not move to say so.
Accessibility · Robust
Colour may reinforce meaning but must never be the only thing carrying it.
Accessibility · Perceivable
Interactive targets need to be large enough and spaced enough to hit reliably.
Accessibility · Operable
Large-scale motion can cause nausea and dizziness, so the system preference must be honoured.
Accessibility · Operable
Content must work at 400 percent zoom without horizontal scrolling, which is the same as working at 320 pixels wide.
Accessibility · Perceivable
Text must scale to 200 percent without breaking, which means never sizing type in absolute units.
Accessibility · Perceivable
Users must be able to increase spacing without content being clipped or lost.
Accessibility · Perceivable
Errors must be identified in text, described specifically, and accompanied by a suggested fix where one is known.
Accessibility · Understandable
Every input needs a persistent label, and format requirements must be stated before the user types.
Accessibility · Understandable
Content that appears on hover or focus must be dismissible, hoverable and persistent.
Accessibility · Perceivable
Single-character shortcuts must be switchable off, remappable, or active only on focus.
Accessibility · Operable
A structured assessment against WCAG, combining automated tooling with the manual testing that finds most real problems.
Workflow · Practice
Everything in Accessibility, by category
The full contents of this section, so you can see the shape of it rather than only what a filter returned.