Skip to content
Logo mtc Berlin - Zur Startseite Logo mtc Berlin - Zur Startseite

Documenting Test Results

The systematic documentation of accessibility tests is a crucial component of any quality assessment. It creates traceability, enables targeted improvements, and is in many cases a prerequisite for legal proof requirements (e.g., under BFSG).

Why documentation is important:

  • Support for internal quality processes
  • Verifiability for audits, certifications, or authorities
  • Basis for communication with development and management
  • Reusability and comparability for re-tests

What should be documented:

  • Tested pages and components (URL, description)
  • Testing methods used (automated, manual, screen reader)
  • Barriers found with description, screenshot, and/or code reference
  • Affected success criterion according to WCAG (e.g., 1.1.1 Non-text Content)
  • Assessment (e.g., critical, relevant, note)
  • Recommended solution / action
  • Responsible role or team for remediation

Formats and tools:

  • Tables (Excel/Sheets) for simple projects
  • Ticket systems (Jira, GitHub Issues) for direct integration into the development workflow
  • Specialized tools for structured WCAG-based recording and reporting

Digital support:

For structured recording and management of test results, specialized platforms can be used. A solution like gooda11y offers, for example, the ability to:

  • centrally record various testing methods (automated, manual, screen reader),
  • categorize according to WCAG success criteria,
  • create reports for internal purposes or legal requirements,
  • assign tasks and comments within the team.

Such tools help ensure traceability and make the testing process efficient – especially for recurring test cycles or complex projects.

Practical tip:

  • Screenshots and brief descriptions of problems facilitate communication
  • Use consistent terms and tags (e.g., #keyboard, #contrast, #labelmissing)
  • Version tests and results regularly

Distinction from the accessibility statement:

The test results documentation is the internal basis for publicly visible documents such as an accessibility statement. This should be based on consistent data but formulated in a reduced and layperson-friendly manner.