Web Accessibility Checklist
A release checklist for making a website or web app usable with a keyboard, a screen reader, zoom and reduced motion. It follows WCAG 2.2 level AA, including the criteria new in 2.2, and every check says how much it matters and exactly how to confirm it, from page structure and focus to contrast, forms, ARIA and testing.
8
Sefism · Oct 2026
46
Sefism · Oct 2026
6
Sefism · Oct 2026
Stacks and tools
Sefism · Oct 2026
Checklist
Web Development
Sefism
25 min read
Intermediate
Free
What this checklist is
A release checklist for making a website or web app usable with a keyboard, a screen reader, zoom and reduced motion. It follows WCAG 2.2 level AA, including the criteria new in 2.2, and every check says how much it matters and exactly how to confirm it, from page structure and focus to contrast, forms, ARIA and testing.
It has 8 chapters and 46 checks, each with how to verify it and how much it matters. For web developers and designers shipping to production.
Chapter by chapter
1. Structure and semantics (6 checks)
Screen reader users move through a page by its headings, landmarks and lists. These checks make sure the structure in the code matches the structure people see.
2. Keyboard and focus (6 checks)
Everything a mouse can do must work from the keyboard, and people must always see where focus is. These checks cover the keyboard pass every release should get.
3. Images and media (7 checks)
Images, icons, audio and video need a text equivalent. These checks cover alternative text, icon buttons, captions and anything that moves or flashes.
4. Color and contrast (4 checks)
Low contrast text is the single most common failure on the web. These checks cover text contrast, the contrast of controls and focus rings, and meaning carried by colour alone.
5. Forms and errors (7 checks)
Forms are where most people give up when a site is not accessible. These checks cover labels, instructions, errors, sign-in and the new WCAG 2.2 rules for repeated entry.
6. Zoom, reflow, pointers and motion (7 checks)
Many people browse zoomed in, with larger text, on a small screen or with motion turned down. These checks make sure the layout still works when they do.
7. ARIA and dynamic content (4 checks)
ARIA can fix gaps that HTML cannot, and it can also make a page much worse. These checks cover custom widgets, live updates and the rule of using native HTML first.
8. Testing and process (5 checks)
Accessibility holds up only when it is checked on every release, not once a year. These checks put automated tools, manual passes and real assistive technology into your routine.
How it works on Sefism
The checklist is one page: each check has a severity (must, should or nice to have) and a concrete way to verify it, and members can tick checks off as they go. The opening chapters are open to everyone. Adding it to your account uses credits, opens every chapter and keeps your progress.
Every claim is checked against the sources listed on the page (6 cited).
Ready to start?
Opens on Sefism in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
Follow along
New writing, resources and project ideas land here first.