Understand web accessibilityModule 3 of 4 · 0 done
Operable & understandable interfaces
Keyboard access, focus, target size, forms and plain language.
By the end you’ll be able to
- Design logical focus order and visible focus
- Build accessible forms
- Write labels and errors for assistive tech
Keyboard first
Everything clickable must be reachable and usable with a keyboard, in a logical order, with a clearly visible focus indicator. Modals trap focus while open and return it when closed. Provide a “skip to content” link.
- Never remove focus outlines without a replacement
- Targets at least 24×24 CSS px (WCAG 2.2)
- No keyboard traps
Forms that talk
Every input needs a visible, programmatic label. Group related fields, mark required ones in text, and put errors next to the field, linked programmatically, saying how to fix it.
Plain language
Short sentences, common words, one idea per paragraph. Link text that makes sense out of context (“Download the 2026 report (PDF, 2 MB)”, not “click here”).
Make a form fully accessible
Pick a sign-up or contact form online.
Deliverable: An annotated accessible form redesign. 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 operable interactions scores
A free test adds Operable interactions to your skill report and shows how close you are to the 75% job-ready target.