The complete manual
accessibility checklist
A structured, print-friendly PDF covering the accessibility checks that automated tools can’t catch. Built for testers, developers, and designers who want to go beyond the scanner.
- Beyond automated scans
- 30+ manual checks
- Print-friendly
- Screen reader + keyboard
Organised around four testing methods
Each section focuses on a specific manual testing method. Every check includes step-by-step instructions so anyone on the team can run it — no specialist tools required.
Keyboard testing
Can users navigate and operate your entire site using only a keyboard?
- Tab order is logical and follows visual layout
- No keyboard traps in modals or widgets
- All interactive elements reachable and operable
- Dropdowns and menus work without a mouse
Screen reader testing
Does your content make sense when read aloud by assistive technology?
- Images announced with meaningful alt text
- Form errors announced without losing context
- Headings create a logical reading structure
- Custom widgets use correct ARIA roles and states
Zoom & reflow
Does content remain usable when users zoom in or increase text size?
- Content reflows at 400% zoom without horizontal scroll
- Text remains readable at 200% browser zoom
- No content or functionality is clipped or lost
- Spacing overrides don’t break layout
Cognitive & motion
Is your site safe and usable for people with cognitive and vestibular conditions?
- Animations pause, stop, or can be hidden
- No content flashes more than 3 times per second
- Instructions don’t rely on shape, colour, or position alone
- Session timeouts warn users in advance
Built for teams who want to go beyond the scanner
Automated tools catch around 30–40% of accessibility issues. This checklist covers the rest — the checks that require a human to run.
Developers
Verify keyboard behaviour, focus management, and ARIA implementation before code review. Catch issues that linters and scanners will never flag.
Designers
Test focus indicators, motion, and cognitive load before handoff. Confirm that your design holds up under real assistive technology conditions.
QA testers
Add manual accessibility checks to your existing test plan. Each item is written as a clear pass/fail check so you can log and track results easily.
Digital agencies
Pair it with automated scanning for a complete audit deliverable. Share it with clients to show the depth of your accessibility process.
Start with an automated scan, then go manual
Run a free scan first to find the quick wins, then use this checklist for the rest.
Automate the checks you can, then audit the rest
Manual testing is essential — but starting with an automated scan saves hours. WebYes Accessibility identifies WCAG failures across your entire site instantly, so your manual effort goes where it matters most.
Full-site scanning
Scan every page against WCAG A and AA automatically in minutes
AI-powered fixes
Get code-level remediation suggestions you can apply directly
Scheduled monitoring
Catch regressions automatically before users or auditors do
Compliance reports
Detailed audit reports covering ADA, Section 508, and EAA
-
Manual accessibility testing means checking your site by hand, using a keyboard, screen reader, or browser tools, rather than relying solely on automated scanners.
Automated tools can detect around 30–40% of WCAG issues. The rest require a human tester to evaluate context, logic, and real-world usability.
-
Not for every check. Many items in the checklist only require a keyboard and a browser. Screen reader checks are clearly labelled so you can complete the rest first.
For screen reader testing, NVDA (Windows, free) and VoiceOver (Mac/iOS, built-in) are the most commonly used tools.
-
The WCAG checklist covers the full range of success criteria across all four WCAG principles, a great starting point for any audit.
This manual checklist focuses specifically on the checks that require human judgment: keyboard behaviour, screen reader output, zoom and reflow, and cognitive accessibility. Use both together for the most complete coverage.
-
A keyboard and zoom review of a single page typically takes 20–40 minutes. Screen reader testing takes longer depending on your familiarity with the tool.
Working through this checklist page by page is the most efficient approach. Pair it with an automated scan first to eliminate known issues before you start.
-
Yes. The PDF is designed to be shared and worked through collaboratively. Developers, designers, and QA testers each have relevant sections.
Each check is written as a clear pass/fail statement so results can be logged in any project management or bug tracking tool.
-
This checklist covers the manual testing layer, a critical part of any complete accessibility audit. Combined with automated scanning and the WCAG checklist, it gives you strong coverage.
True accessibility also involves testing with real users who have disabilities. Think of this checklist as the technical floor, not the ceiling.
