The Ultimate Manual Accessibility Testing Checklist
While automated tools catch about 30% of accessibility issues, the remaining 70% require human judgment and manual testing. This comprehensive checklist provides QA testers with actionable steps to validate WCAG 2.1 AA compliance through hands-on testing techniques. Bookmark this guide for your next accessibility audit.
Pro Tip: Always test with actual assistive technologies. Automated tools can't simulate the human experience of users with disabilities. Your manual validation is what truly ensures inclusive design.
How to Use This Checklist
This checklist is organized by WCAG principles (POUR) and priority levels. Test each item systematically, documenting any violations with screenshots, screen reader recordings, and detailed reproduction steps. Aim for WCAG 2.1 AA compliance as your baseline target.
Core Manual Accessibility Testing Checklist
1. Keyboard Navigation & Focus Management
Complete Keyboard Accessibility Level A
All functionality must be operable through keyboard interface without
requiring specific timings for individual keystrokes.
Test Action: Unplug mouse. Use Tab, Shift+Tab, Enter, Space,
Arrow keys to navigate. Can you complete all user journeys?
Visible Focus Indicator Level AA
All interactive elements must show a clear visual focus state when
navigated via keyboard.
Test Action: Tab through page. Is there a clear highlight
(border, background change) showing current focus? Check contrast ratio of focus indicator against
background.
Logical Tab Order Level A
Focus must move in a logical sequence matching visual layout.
Test Action: Tab through form fields, buttons, links. Does
focus follow left-to-right, top-to-bottom reading order?
No Keyboard Traps Level A
Users must not get stuck in any component when navigating via keyboard.
Test Action: Enter modals, dropdowns, carousels. Can you exit
using Escape or Shift+Tab? Can you close all dialogs?
2. Screen Reader Testing (NVDA/VoiceOver/JAWS)
Proper Page Structure Level A
Headings must be properly nested (h1-h6) and landmarks used appropriately.
Test Action: Use screen reader shortcut to list headings
(NVDA+F7). Check hierarchy: Only one h1, proper nesting, meaningful headings.
Alternative Text for Images Level A
All informative images must have descriptive alt text; decorative images
must have empty alt.
Test Action: Navigate images with screen reader. For
informative images: Is description meaningful? For decorative: Is it skipped?
Link Purpose from Context Level A
Link text must make sense when read alone or with surrounding context.
Test Action: Use screen reader to list links (NVDA+F7). Does
"Read more" become "Read more about accessibility testing"?
Form Labels & Instructions Level A
All form fields must have associated labels; complex fields need
instructions.
Test Action: Navigate form fields. Does screen reader announce
label, required status, format hints, and error messages?
3. Visual & Color Accessibility
Color Contrast Ratio Level AA
Normal text: 4.5:1, Large text (18pt+): 3:1, UI components: 3:1.
Test Action: Use Color Contrast Analyzer tool. Test body text,
buttons, links, form borders, error messages against backgrounds.
Color Not Sole Indicator Level A
Information must not be conveyed by color alone.
Test Action: Check error states, success messages, required
fields. Is there text, icon, or pattern in addition to color?
Text Resize (200%) Level AA
Content must remain readable and functional when zoomed to 200%.
Test Action: Use browser zoom (Ctrl/Cmd +). Check for
horizontal scrolling, overlapping content, clipped text at 200% zoom.
No Seizure Triggers Level A
No content flashes more than 3 times per second.
Test Action: Monitor animations, auto-playing videos,
notifications. Do any elements flash rapidly? Use epilepsy analysis tools if needed.
4. Forms & Interactive Elements
Error Identification & Suggestion Level AA
Errors must be clearly identified and suggestions provided when possible.
Test Action: Submit invalid form. Are errors announced to
screen reader? Do they appear near relevant fields? Do they suggest corrections?
Labels & Instructions Level A
All form controls must have visible labels; complex fields need
instructions.
Test Action: Inspect form HTML. Do all inputs have associated
<label> or aria-label/aria-labelledby? Check password requirements hints.
Timing Adjustable Level AAA
Users must be able to turn off, adjust, or extend time limits.
Test Action: Test session timeouts, auto-refresh, timed tests.
Can users extend time? Is there warning before timeout?
Status Messages Level AA
Dynamic content updates must be announced to assistive tech.
Test Action: Test AJAX forms, live chat, notifications. Does
screen reader announce "Form submitted successfully" or "New message received"?
5. Multimedia & Mobile Accessibility
Video Captions Level A
Pre-recorded video must have synchronized captions.
Test Action: Play videos with sound off. Are captions accurate,
synchronized, and include speaker identification and sound effects?
Audio Descriptions Level AA
Pre-recorded video must have audio description for visual content.
Test Action: Watch video with eyes closed. Is all visual
information described audibly?
Touch Target Size Level AA
Touch targets must be at least 44x44 CSS pixels.
Test Action: On mobile/tablet, test button taps. Are touch
targets large enough? Is there adequate spacing between interactive elements?
Orientation Support Level AA
Content must support both portrait and landscape orientations.
Test Action: Rotate device. Does content reflow properly? Is
functionality preserved in both orientations?
Testing Tools for Manual Validation
- Screen Readers: NVDA (Windows + Firefox), VoiceOver (macOS/iOS), JAWS (Windows)
- Color Contrast: WebAIM Contrast Checker, Color Contrast Analyzer (Chrome extension)
- Browser Extensions: axe DevTools, WAVE Evaluation Tool, Accessibility Insights
- Mobile Testing: iOS VoiceOver, Android TalkBack, Accessibility Scanner (Android)
- Code Inspection: Chrome DevTools Elements panel for ARIA attributes and semantics
Documenting Accessibility Issues
When you find violations, document them with:
- WCAG Criteria: Specific success criterion violated (e.g., "1.4.3 Contrast (Minimum)")
- Impact Level: High/Medium/Low based on user impact
- Steps to Reproduce: Exact navigation path to replicate
- Assistive Tech Used: NVDA, VoiceOver, keyboard-only, etc.
- Screenshots/Recordings: Visual evidence of the issue
- Suggested Fix: Specific code or design recommendation
Critical Reminder: Manual accessibility testing is iterative. Retest after fixes, involve users with disabilities when possible, and integrate these checks into your regular QA cycles. Accessibility is not a one-time audit but an ongoing commitment.
Integrating Checklist into QA Workflow
To make accessibility testing sustainable:
- Include checklist items in test case creation
- Add accessibility column to bug tracking systems
- Conduct weekly accessibility review sessions
- Pair manual testers with developers during fix verification
- Use this checklist as part of Definition of Done for all features
To build a strong foundation in testing principles that underpin accessibility work, explore our Manual Testing Fundamentals course, which covers the essential skills needed for comprehensive quality assurance.
Frequently Asked Questions (FAQs)
1. How long does manual accessibility testing take?
For a medium-sized website (50-100 pages), initial comprehensive testing takes 40-80
hours. Maintenance testing after major updates typically takes 8-16 hours. Break it down by feature areas
rather than trying to test everything at once.
2. Do I need to test every page with a screen reader?
No. Test templates (header, footer, navigation, forms) thoroughly, then sample 2-3
pages of each content type. Focus on unique interactive components and critical user journeys like
checkout, signup, and search.
3. What's the difference between Level A, AA, and AAA in testing priority?
Level A = Basic accessibility (critical). Level AA = Standard compliance (target for
most organizations). Level AAA = Enhanced accessibility (specialized needs). Most legal requirements
mandate AA compliance. Start with A, achieve AA, consider AAA for critical user paths.
4. How do I test for cognitive accessibility issues?
Check: Is content written in plain language (8th grade level)? Is navigation
consistent? Are instructions clear? Is there enough white space? Are tasks broken into manageable steps?
Are error messages helpful? Use tools like Hemingway App for readability testing.
5. Should I test with multiple screen readers?
Yes. Test with at least one screen reader per major platform: NVDA on
Windows/Firefox, VoiceOver on macOS/Safari and iOS. If your user base includes JAWS users (common in
enterprise), include JAWS testing for critical workflows.
6. How do I handle accessibility testing for single-page applications (SPAs)?
SPAs require special attention for: 1) Dynamic content updates (use ARIA live
regions), 2) Focus management after route changes, 3) History navigation with screen readers, 4) Loading
states announcement. Test each "virtual page" change as a new page load.
7. What common mistakes should I avoid in manual accessibility testing?
Avoid: 1) Testing only with automated tools, 2) Not testing with actual assistive
tech, 3) Assuming mobile accessibility equals desktop, 4) Forgetting to test forms thoroughly, 5) Not
checking color contrast in different states (hover, focus, disabled), 6) Overlooking link purpose in
context.
8. How often should I run manual accessibility tests?
Run full manual tests: 1) Before major releases, 2) After design system updates, 3)
Quarterly for compliance monitoring. Run targeted tests: 1) With every feature release, 2) After
third-party component updates, 3) When adding new interactive elements.