7b - Transversal Features, Standardisation Phase 1
Contractor: TBA
Main Contact: TBA
Start date: 1 May 2027
End data: 31 July 2027
Abstract
Standardising the highest-impact transversal features in this phase means that an accessibility improvement only needs to be implemented once and automatically works everywhere the feature appears. This is one of the highest-leverage changes in the programme. Each fix multiplies across dozens of admin views in core and across the entire extension ecosystem. Starting with the most frequently used features (Phase 1) ensures the largest number of users benefit as early as possible.
Milestone 7b depends on the prioritised Phase 1 list produced and OSM-accepted in Milestone 7a, on the stable design system from Milestone 2b, and on the test protocols and acceptance criteria established in Milestone 1a.
Scope of Work
Deliverable 1: Standardisation of Phase 1 Transversal Features
Standardise the Phase 1 transversal features (as defined and accepted in Milestone 7a) so that each feature uses:
- The design system components from Milestone 2b
- A consistent coding pattern across all admin views where the feature appears
The standardised implementation must ensure that keyboard navigation, focus management, ARIA attributes, and screen-reader behaviour work the same way everywhere the feature appears.
Deliverable 2: Removal of Outdated Code and Legacy Patterns
Remove the outdated code and legacy patterns for the Phase 1 features that:
- Block accessibility improvements, or
- Prevent the design system components from being applied
Removals must be documented (what was removed, where, and why) so that downstream contractors and the wider community can follow the same pattern in Phase 2 (Milestone 7c) and in their own extensions.
Deliverable 3: Validation of Each Phase 1 Feature
Validate each Phase 1 transversal feature against the test protocols from Milestone 1a in at least three admin views where it appears.
Validation must:
- Use the AT/browser combinations defined in Milestone 1a (minimum matrix: NVDA + Chrome, JAWS + Edge, VoiceOver + Safari)
- Record results against the acceptance criteria from Milestone 1a
- Categorise any remaining issues by severity and map them to the relevant WCAG 2.2 success criterion
Deliverable 4: Documentation and Milestone Report
Maintain the programme documentation framework and produce the milestone completion report in the format agreed at kick-off.