8b - Automated Accessibility Testing in CI
Contractor: TBA
Main Contact: TBA
Start date: 4 January 2027
End data: 28 February 2027
Abstract
This milestone multiplies the value of the CI infrastructure across the thousands of extensions in the Joomla ecosystem. Each extension developer can now protect their own accessibility gains from regression without building a testing infrastructure from scratch. The violations dashboard makes regression and progress visible to the project team, the OSM board, and the STF.
Milestone 8b depends directly on the tests and CI gate delivered in Milestone 8a, on the baseline and test protocols from Milestone 1a, and on the remediation backlog from Milestone 1b.
Scope of Work
Deliverable 1: Violations Dashboard
Implement a violations dashboard: a continuously updated view of the current accessibility violation count across Joomla core, tracked over time against the baseline from Milestone 1a.
The dashboard must:
- Be continuously updated from the automated tests and CI gate delivered in Milestone 8a
- Track violation counts over time against the Milestone 1a baseline
- Make regression and progress visible to the project team, the OSM board, and the STF
- Be hosted and operated in a way that survives the end of the funded programme, with a documented operational plan
- Be accessible itself, in line with WCAG 2.2 AA and the test protocols from Milestone 1a
Deliverable 2: Reference CI Workflow and Extension Setup Guide
Publish a reference CI workflow and a setup guide so that extension developers can add the same automated accessibility testing to their own projects.
The reference workflow and guide must:
- Be drop-in usable for typical Joomla extension repositories
- Be aligned with the CI gate and test patterns established in Milestone 8a
- Include at least one worked example showing the workflow applied to a representative extension
- Be written for extension developers, not only for core maintainers, with a clear walk-through of setup, common failures, and how to update tests when behaviour intentionally changes
Deliverable 3: Documentation and Milestone Report
Maintain the programme documentation framework and produce the milestone completion report in the format agreed with OSM at kick-off.
The documentation must also include a maintainer-facing operations guide for the dashboard, covering data sources, hosting, and how to evolve the dashboard as the test base grows.