Accessibility Testing Guide

Last Updated: January 2025

Learn how to test your website for WCAG compliance using automated tools, manual testing, screen readers, and user testing methods.

Why Test for Accessibility?

Accessibility testing ensures your website can be used by everyone, including people with disabilities. A comprehensive testing approach combines automated tools, manual testing, and user feedback to achieve true WCAG compliance.

Automated tools catch ~30-40% of issues

Manual testing is essential for comprehensive compliance

Combined approach is best

Use automated + manual + user testing for best results

Testing Methods

Automated Testing

Use tools to quickly identify common accessibility issues

Tools:

axe DevToolsWAVELighthouseAI Audit Helper

Pros:

✓Fast and efficient
✓Catches common issues quickly
✓Can be integrated into CI/CD
✓Good for regression testing

Cons:

•Only catches ~30-40% of issues
•May produce false positives
•Can't test user experience
•Requires manual verification

When to use: Use for initial scans, continuous monitoring, and catching obvious issues

Manual Testing

Test with keyboard navigation and assistive technologies

Tools:

Keyboard onlyScreen readersBrowser DevTools

Pros:

✓Catches issues automated tools miss
✓Tests real user experience
✓Identifies usability problems
✓Validates automated findings

Cons:

•Time-consuming
•Requires knowledge and training
•Subjective results
•Can't test at scale

When to use: Use for comprehensive audits, validating fixes, and testing complex interactions

Screen Reader Testing

Test with actual screen reader software

Tools:

NVDAJAWSVoiceOverTalkBack

Pros:

✓Tests real assistive technology
✓Identifies navigation issues
✓Validates ARIA implementation
✓Tests content structure

Cons:

•Requires learning screen readers
•Time-intensive
•Different results per screen reader
•Steep learning curve

When to use: Use for testing content structure, ARIA labels, and navigation flow

User Testing

Test with people who have disabilities

Tools:

User interviewsUsability testingFeedback sessions

Pros:

✓Real-world validation
✓Identifies usability issues
✓Provides authentic feedback
✓Tests edge cases

Cons:

•Expensive and time-consuming
•Requires recruitment
•Limited sample size
•May need multiple sessions

When to use: Use for validating major changes, new features, and getting authentic feedback

Recommended Testing Workflow

Initial Automated Scan

Run automated tools to identify obvious issues

15-30 minutes

Tools:

axe DevToolsWAVELighthouse

Keyboard Navigation Test

Navigate the entire site using only keyboard

30-60 minutes

Tools:

Keyboard (Tab, Enter, Arrow keys)Browser DevTools

Screen Reader Test

Test with at least one screen reader

1-2 hours

Tools:

NVDA (free)VoiceOver (built-in)JAWS

Visual Inspection

Check color contrast, text sizing, and visual issues

30-60 minutes

Tools:

Color contrast checkerBrowser zoomResponsive design mode

Form Testing

Test all forms for accessibility

30-60 minutes

Tools:

Keyboard navigationScreen readerError testing

Document and Fix

Document findings and prioritize fixes

Ongoing

Tools:

Issue trackerTesting checklist

Comprehensive Testing Checklist

Keyboard Navigation

All interactive elements are keyboard accessible
Focus indicators are visible and clear
Tab order follows logical sequence
No keyboard traps
Skip links work correctly
Modal dialogs trap focus properly

Screen Reader

All images have appropriate alt text
Headings are properly structured (h1-h6)
Landmarks are properly defined
Form labels are associated with inputs
ARIA labels are used correctly
Content is announced in logical order

Visual

Color contrast meets WCAG requirements
Text can be resized up to 200%
Content reflows at 320px width
Color is not the only means of conveying information
Focus indicators are visible
Text spacing can be adjusted

Forms

All inputs have associated labels
Error messages are clear and associated
Required fields are indicated
Form validation is accessible
Error recovery is possible
Help text is available when needed

Media

Videos have captions
Audio has transcripts
Media controls are keyboard accessible
Auto-playing media can be paused
No flashing content (3 flashes per second)
Alternative formats are available

Quick Start: 5-Minute Test

Don't have time for a full audit? Start with these quick checks:

Run an automated tool: Use axe DevTools or WAVE to scan your homepage
Test keyboard navigation: Try navigating your site using only Tab, Enter, and Arrow keys
Check images: Verify all images have alt text (right-click → Inspect)
Test color contrast: Use a contrast checker on your main text
Check forms: Ensure all form inputs have visible labels

Related Resources

Testing Tools

Browse accessibility testing tools

Tool Comparison

Compare testing tools

Testing Methods

Automated Testing

Use tools to quickly identify common accessibility issues

Tools:

axe DevToolsWAVELighthouseAI Audit Helper

Pros:

✓Fast and efficient
✓Catches common issues quickly
✓Can be integrated into CI/CD
✓Good for regression testing

Cons:

•Only catches ~30-40% of issues
•May produce false positives
•Can't test user experience
•Requires manual verification

When to use: Use for initial scans, continuous monitoring, and catching obvious issues

Manual Testing

Test with keyboard navigation and assistive technologies

Tools:

Keyboard onlyScreen readersBrowser DevTools

Pros:

✓Catches issues automated tools miss
✓Tests real user experience
✓Identifies usability problems
✓Validates automated findings

Cons:

•Time-consuming
•Requires knowledge and training
•Subjective results
•Can't test at scale

When to use: Use for comprehensive audits, validating fixes, and testing complex interactions

Screen Reader Testing

Test with actual screen reader software

Tools:

NVDAJAWSVoiceOverTalkBack

Pros:

✓Tests real assistive technology
✓Identifies navigation issues
✓Validates ARIA implementation
✓Tests content structure

Cons:

•Requires learning screen readers
•Time-intensive
•Different results per screen reader
•Steep learning curve

When to use: Use for testing content structure, ARIA labels, and navigation flow

User Testing

Test with people who have disabilities

Tools:

User interviewsUsability testingFeedback sessions

Pros:

✓Real-world validation
✓Identifies usability issues
✓Provides authentic feedback
✓Tests edge cases

Cons:

•Expensive and time-consuming
•Requires recruitment
•Limited sample size
•May need multiple sessions

When to use: Use for validating major changes, new features, and getting authentic feedback

Recommended Testing Workflow

Initial Automated Scan

Run automated tools to identify obvious issues

15-30 minutes

Tools:

axe DevToolsWAVELighthouse

Keyboard Navigation Test

Navigate the entire site using only keyboard

30-60 minutes

Tools:

Keyboard (Tab, Enter, Arrow keys)Browser DevTools

Screen Reader Test

Test with at least one screen reader

1-2 hours

Tools:

NVDA (free)VoiceOver (built-in)JAWS

Visual Inspection

Check color contrast, text sizing, and visual issues

30-60 minutes

Tools:

Color contrast checkerBrowser zoomResponsive design mode

Form Testing

Test all forms for accessibility

30-60 minutes

Tools:

Keyboard navigationScreen readerError testing

Document and Fix

Document findings and prioritize fixes

Ongoing

Tools:

Issue trackerTesting checklist

Comprehensive Testing Checklist

Keyboard Navigation

All interactive elements are keyboard accessible
Focus indicators are visible and clear
Tab order follows logical sequence
No keyboard traps
Skip links work correctly
Modal dialogs trap focus properly

Screen Reader

All images have appropriate alt text
Headings are properly structured (h1-h6)
Landmarks are properly defined
Form labels are associated with inputs
ARIA labels are used correctly
Content is announced in logical order

Visual

Color contrast meets WCAG requirements
Text can be resized up to 200%
Content reflows at 320px width
Color is not the only means of conveying information
Focus indicators are visible
Text spacing can be adjusted

Forms

All inputs have associated labels
Error messages are clear and associated
Required fields are indicated
Form validation is accessible
Error recovery is possible
Help text is available when needed

Media

Videos have captions
Audio has transcripts
Media controls are keyboard accessible
Auto-playing media can be paused
No flashing content (3 flashes per second)
Alternative formats are available