- Article
- Intermediate
- 2 minutes read
- Reviewed August 4, 2026
Accessibility testing requires more than one tool or method.
Automated scanners can identify selected code patterns. Manual testing is required to evaluate interaction, meaning, focus, instructions and usability.
Define the Scope
Include representative:
- Templates.
- Content types.
- Forms.
- Account workflows.
- Navigation.
- Search.
- Media.
- Plugin interfaces.
- Error states.
- Mobile layouts.
- Logged-in and logged-out experiences.
Testing only the homepage provides limited coverage.
Automated Testing
Automated tools can detect issues such as:
- Missing accessible names.
- Some contrast failures.
- Duplicate IDs.
- Invalid ARIA.
- Missing form labels.
- Heading or landmark patterns.
They cannot determine whether alt text is meaningful, instructions are understandable or focus movement is appropriate.
Keyboard Testing
Complete every important workflow using the keyboard.
Check focus visibility, order, menu operation, modal behavior, traps, skip links and error recovery.
Screen Reader Testing
Test with at least one common screen reader and browser combination relevant to the audience.
Review headings, landmarks, links, controls, form labels, tables, dynamic announcements and reading order.
Screen-reader testing should complement standards review, not replace it.
Zoom and Reflow
Test browser zoom, text enlargement and narrow viewport widths.
Check that content reflows, controls remain visible and fixed elements do not obscure information.
Colour and Motion
Test contrast in normal, hover, focus, selected, disabled and error states.
Enable reduced-motion and forced-colour or high-contrast settings where available.
Document Findings
Record:
- Page or component.
- Reproduction steps.
- Expected result.
- Actual result.
- User impact.
- Relevant criterion.
- Severity.
- Owner.
- Retest status.
User Testing
Testing with disabled people can reveal workflow and usability issues that technical checks miss.
Compensate participants and integrate feedback into product decisions.
Frequently Asked Questions
Can an automated scan prove WCAG conformance?
No.
How many pages should be tested?
Test representative templates and all critical workflows, then expand according to risk and diversity.
Continue Learning
Previous: [Accessibility in the Block Editor](/resources/wordpress-manual/accessibility/accessibility-block-editor/)
Next: [Maintaining Accessibility Over Time](/resources/wordpress-manual/accessibility/maintaining-accessibility/)