CometWeb tools
A11y checklist
30 WCAG 2.2 checks before you ship
/ Structure
/ Images
/ Forms
/ Keyboard
/ Contrast & visuals
/ WCAG 2.2 (newer criteria)
Why you still need a manual checklist
Automated audits catch only part of accessibility issues. The rest needs manual review.
The list organizes a pre-release review around selected WCAG 2.2 AA topics. Check an item after performing the test, rather than just reading its description.
The scope is a selection of checks. Checking every item does not establish whole-site accessibility or legal compliance; all requirements applicable to the site still need assessment.
Test a task, not just a screen
Choose a specific path: opening a menu, finding a product or submitting a form. Complete it with the keyboard, checking visible focus and error messages. Repeat with a screen reader; appearance alone does not reveal what will be announced.
W3C WAI, Easy Checks ↗WCAG levels
- AWCAG Level A
- Minimum. Without it, whole user groups are blocked.
- AAWCAG Level AA
- Includes Level A and AA criteria. This checklist result does not confirm that all of them are met.
- AAAWCAG Level AAA
- Highest level, rarely for an entire site.
- 2.2WCAG 2.2 (2023)
- Adds Focus Appearance, Target Size, Consistent Help, and more.
No. It covers key AA points, but full compliance needs specialist audit and screen-reader testing.
Before major releases. Automate axe in CI; use the checklist in sprints.
Checkmarks last while the page is open and disappear on refresh. Print a copy before closing it. Save issue descriptions and evidence separately, together with the tested page URL.
WCAG covers web/webview. Native iOS/Android have separate guidance.
What else might come in handy
Automated WCAG 2.2 tests with a fix list and an action plan.