Checklist progress is saved in this browser on this device.
Use this checklist throughout design and implementation, then repeat it on representative pages and flows. It draws on WCAG 2.2 and the WAI evaluation guidance. Automated scans are useful, but cannot establish conformance on their own.
Structure and content
- Use semantic landmarks, a meaningful page title, and a clear heading hierarchy.
- Give links names that make sense out of context; label buttons by their action.
- Provide text alternatives for meaningful images and hide decorative images from assistive technology.
- Identify the page language and explain unusual abbreviations or instructions.
- Ensure instructions do not rely on color, position, shape, or sound alone.
Keyboard and interaction
- Complete every primary flow using a keyboard without a pointer.
- Keep focus visible and in a logical order; restore focus after dialogs close.
- Ensure menus, dialogs, tabs, and custom controls expose expected names, roles, and states.
- Avoid keyboard traps and provide a way to skip repeated navigation.
- Make touch targets practical and avoid interactions that require precise gestures.
Forms and feedback
- Associate every field with a persistent visible label.
- Explain required formats before entry and identify required fields in text.
- Show errors in text, connect them to the affected fields, and preserve valid entries.
- Announce important asynchronous status changes to assistive technology.
- Confirm destructive actions and provide a clear recovery route where possible.
Visual and responsive checks
- Check text and controls at browser zoom and narrow viewport widths.
- Verify text and non-text contrast against the selected WCAG target.
- Confirm content reflows without requiring two-dimensional scrolling for ordinary reading.
- Respect reduced motion preferences and avoid flashing content.
- Test with keyboard and at least one screen reader/browser combination used by your audience.
- Record issues, severity, owner, and retest result; include people with disabilities when feasible.
References
Every business and project is different. Treat this as general planning guidance, then confirm platform-specific, legal, tax, and security requirements with the appropriate provider or qualified professional.