Accessibility Testing Workflow
A well-defined workflow is essential for systematically and efficiently testing accessibility, documenting problems in a way that is understandable, and continuously implementing improvements. This chapter shows typical phases and roles in a well-thought-out test workflow.
Preparation and goal definition
- Define relevant standards (e.g. WCAG 2.2 AA)
- Define the scope of the test (e.g. homepage, central functions)
- Clarify roles and responsibilities (e.g. QA, UX, development)
Preliminary analysis (optional)
- First review using automated tools (e.g. WAVE, Axe)
- Recognition of obvious barriers
- Comparison with existing knowledge or previous versions
Detailed test execution
- Manual tests (see chapter 3.2.1)
- Screenreader test (see chapter 3.2.2)
- Combination with automated tests for completeness
Documentation and evaluation
- Document all found barriers including WCAG reference (see chapter 3.3)
- Assessment of relevance for user groups (critical, notice, etc.)
- Recommendation for fixing or passing on to responsible teams
Communication and improvement
- Transfer of results to development / design
- Discussion of unclear points with experts
- Definition of deadlines and priorities
Re-test / regression testing
- Check if fixed barriers have actually been resolved
- Validation by repeating central test steps
- Comparison with previous version or reference status
Conclusion and reporting
- Summary of results (e.g. in gooda11y or as PDF report)
- Optional: evaluation for training or governance
- Derivation of lessons learned for future projects
Recommendations for a smooth process:
- Integrate tests early into the project (“Shift Left”)
- Regular team discussion about process and results
- Use tool-supported documentation and progress control
- Plan testing with real user groups, where possible
A well-defined workflow lays the foundation for efficient accessibility testing that not only meets legal requirements, but also improves user experience and the quality of digital offers.