For the OpenSourceMatters Accessibility Project, this page lists all relevant deliverables and information.
Web Content Accessibility Guidelines (WCAG) Report
Alternative formats/exports:
Authoring Tools Accessibility Guidelines (ATAG) Report
Alternative formats/exports:
The baseline metrics have been collected using a mix of automatic (axe) and user testing. These metrics can be used in subsequent milestones to track progress and its velocity. Find the overview of the results in the following table and the details further down on the page:
| Journey | axe errors |
User 1 | User 2 | User 3 | User 4 |
|---|---|---|---|---|---|
| Journey 1 | 3 | Friction | Completed | Completed | Completed |
| Journey 2 | 8 | Blocked | Blocked | Blocked | Friction |
| Journey 3 | 7 | Blocked | Friction | Friction | Friction |
| Journey 4 | 10 | Not tested | Completed | Friction | Friction |
| Journey 5 | 8 | Friction | Completed | Friction | Completed |
| Journey 6 | 3 | Workaround | Not tested | Blocked | Completed |
| AUS score | ∅ | 35 | 73 | 28 | 50 |
= Lower is better / = Higher is better / All metrics are based on the “blog” example installation.
For the axe scores above, the Accessibility Checker is used. See the Guide and readme file for more details.
In addition to the numbers from the automated testing, four users tested the user journeys. Each journey was rated on a scale of completion. Afterwards the users answered questions to determine the AUS (Accessibility Usability Scale) score.
The Accessible Usability Scale (AUS) is a free tool to measure the usability of a digital product for assistive technology users. Inspired by the System Usability Scale (SUS), the Accessible Usability Scale consists of ten questions administered at the end of a user experience to calculate a score.
The scale for completion for every journey is:
Find detailed guidance and results here:
To repeat the user testing, see this template manuscript (in Google Docs) , and the results spreadsheet template (Zipped HTML export) (as Open Document Spreadsheet, in Google Sheets).
To ensure that testing can be integrated and re-used, these test protocols have been produced, including acceptance criteria for common components.
This is this page.
Reports are delivered to OSM in a separate format.