Accessibility is a property of the complete experience, including content, code, design, forms, documents and third-party tools. This checklist is a starting point, not a claim of WCAG 2.2 AA conformance or a substitute for expert and user testing.
Start with keyboard use
Complete the main journeys without a mouse. Focus should be visible, ordered logically and never trapped or hidden behind sticky elements.
- Skip link
- Visible focus
- Logical order
- No keyboard trap
- Menus and dialogs operable
Check structure and meaning
Use one descriptive H1, logical headings, landmarks, lists and table markup. Links and buttons should describe their destination or action.
Review colour and visual presentation
Text and controls need sufficient contrast. Information should not depend on colour alone, and zoom or text spacing should not remove content or actions.
Test forms and status messages
Every field needs a persistent label. Errors should identify the field, explain the problem and preserve entered data. Success or failure messages need to be announced to assistive technology.
Provide useful alternatives
Meaningful images need purpose-based alt text. Decorative images should be ignored. Video, audio and important documents need appropriate alternatives.
Test the complete responsive page
WCAG conformance applies to the full page and its responsive variations. Automated tools catch only part of the problem, so combine them with keyboard, screen reader and human review.