1b - Remediation Plan, Quick Wins and Community Publication
Contractor: AccessOne
Main Contact: Michael Beganyi, M.A., Principal Accessibility Consultant
Start date: 1 September 2026
End data: 31 October 2026
Abstract
The expert audit from Milestone 1a tells us what is broken. This milestone turns that knowledge into action. The prioritised remediation backlog gives every subsequent milestone a clear, agreed brief. The community publication is equally important, because it closes the loop with Joomla's global community of developers, agencies, and site owners, and builds confidence that the STF investment is being used transparently and systematically. Extension developers who learn about the upcoming design-system and component changes can begin planning their own accessibility improvements, multiplying the impact of the work across the roughly 4,800-extension ecosystem.
Milestone 1b depends directly on the outputs of Milestone 1a (the categorised audit findings, the baseline metrics, and the agreed test protocols and acceptance criteria).
Scope of Work
Deliverable 1: Prioritised Remediation Plan
Produce a severity and effort-rated remediation plan, structured as a prioritised issues backlog in the Joomla GitHub tracker. Each audit finding from Milestone 1a must be:
Mapped to the milestone or milestones that will address it (MS2a through MS10) Rated by severity (carried over from Milestone 1a) and by implementation effort Tagged with the relevant WCAG 2.2 success criterion Given acceptance criteria tied to the test protocols defined in Milestone 1a This backlog is established as the shared source of truth for all subsequent milestones and for STF reporting.
Deliverable 2: Quick-Win Fixes Merged to Core
Fix and merge all audit issues that meet the quick-win threshold, defined as issues solvable in approximately one hour or less, with no architectural dependencies on later milestones. Typical candidates include missing aria-label attributes, missing or unusable text in HTML alt attributes on images, incorrect contrast values in CSS, incorrect ARIA role attributes, and missing <label> elements on simple form controls.
All quick-win fixes must be merged to the Joomla main branch, not only submitted as pull requests.
Deliverable 3: Re-Run of Baseline Metrics
Re-run the baseline metrics established in Milestone 1a after the quick-win fixes are merged, to capture the immediate improvement and to establish the true starting point for all deeper implementation milestones. The metrics must be produced using the same method documented in Milestone 1a, so that the results are directly comparable.
Deliverable 4: Community Publication of Findings and Roadmap
Publish a clear, accessible summary of the work results. The summary must be written for a general Joomla audience and not only for developers, in order to build awareness and to invite feedback from the extension ecosystem.
Deliverable 5: Documentation and Milestone Report
Maintain the programme documentation framework and produce the milestone completion report in the format agreed to at milestone kick-off with.
References
This page is unfinished, please use the Edit this Page link at the bottom of this page to help make it more useful.