What WCAG 2.2 adds to the conversation
WCAG 2.2 extends guidance in areas such as visible focus, alternatives to dragging, target size, and accessible authentication. It is a technical accessibility standard, not a visual style. Meeting selected checks does not establish that an entire website conforms; conformance requires evaluating all applicable criteria and complete processes.
Make the keyboard journey work
Our suggested first check is to navigate without a mouse. Can someone open the menu, follow links, complete a form, and recover from an error? Focus should be visible and follow a sensible order. Sticky headers must not obscure the focused control. Dialogs and menus need an intentional focus strategy, including where focus returns when they close.
Write forms that explain themselves
Give fields persistent labels rather than using placeholders as their only names. Explain required formats before submission, preserve entered values after validation errors, and associate error messages with the relevant input. An error should describe the next action in plain language. Do not rely on a red border alone to tell someone what needs attention.
Design for touch, zoom, and motion preferences
Check that controls have sufficient size and spacing, especially beside other actions. Verify that content remains usable when text is enlarged and on narrow screens. Keep reading order meaningful when layouts collapse. Respect reduced-motion preferences, and avoid animations that are essential to understanding a result. Contrast also needs checking across normal text, muted labels, borders, and interactive states.
Combine tools with human evaluation
Automated tools can find certain markup and contrast issues, but they cannot determine whether instructions make sense or a workflow is easy to finish. Include keyboard testing, appropriate assistive technology checks, and user feedback. Record findings by user impact, fix blockers first, and repeat checks after changes. Accessibility is ongoing product maintenance rather than a one-time badge.
Sources & further reading
Technology facts are linked to the original documentation. Implementation suggestions reflect our editorial analysis.
Sources checked October 22, 2026. Features and guidance may change.
Put this into practice.
Explore business solutions related to this guide.