Workflow Test and Evaluation

Testing and Ensuring Accessibility

Accessibility testing is essential to verify the actual accessibility of digital products. It complements development work with quality control that considers not only technical but also user-centered aspects.

Goal: Ensure that developed content is accessible - both technically (e.g. with screen readers, keyboard) and understandable in terms of content.

Types of Tests:

• Automated Tests: Tools like axe, WAVE or Lighthouse check many technical criteria quickly and reliably. They are good for initial analysis and regression testing.

• Manual Tests: Require human judgment, such as for keyboard navigation, visible focus or semantic structure. Essential for WCAG conformance.

• Tests with Assistive Technologies: Tests with screen readers (e.g. NVDA, VoiceOver), zoom tools or alternative input methods are particularly meaningful.

Typical Test Questions:

• Is every element reachable and operable by keyboard?

• Are all interactive elements correctly labeled (accessible name)?

• Is the semantic structure read correctly?

• Are status changes recognizable and communicated clearly?

Workflow Tips for the Testing Phase:

• Testing in different browsers and on different devices

• Combination of automated and manual checks

• Documentation of results with screenshot, error description and solution proposal

• Use of specialized tools or platforms for central recording (e.g. gooda11y)

Don’t Forget Feedback Mechanisms:

• Digital products should include ways for users to report barriers or provide feedback

• Such feedback provides valuable insights into real usage barriers that may not have been identified in testing

• Feedback evaluations should regularly flow into maintenance and further development

Final Assessment:

• Testing against relevant WCAG success criteria (AA level)

• Document test coverage (what was tested and how?)

• Preparation of accessibility statement based on test results