Skip to main content

7c - Transversal Features — Standardization Phase 2

Contractor: TBA

Main Contact: TBA

Start date: 1 August 2027

End data: 30 September 2027

Abstract​

This milestone completes the standardisation of all transversal features identified in Milestone 7a. Combined with the design system from Milestone 2b, this creates a foundation where future accessibility regressions in transversal features become detectable, attributable, and fixable, rather than accumulating silently across a fragmented codebase.

Milestone 7c depends on the prioritised Phase 2 list produced and OSM-accepted in Milestone 7a, on the Phase 1 standardisation patterns established in Milestone 7b, 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 2 Transversal Features​

Standardise the Phase 2 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 same patterns established for Phase 1 in Milestone 7b, so the full transversal feature set behaves consistently end-to-end

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 2 features that:

  • Block accessibility improvements, or
  • Prevent the design system components from being applied

Removals must be documented (what was removed, where, and why) and must follow the documentation approach established in Milestone 7b so that the full transversal-feature record is coherent.

Deliverable 3: Validation of Each Phase 2 Feature​

Validate each Phase 2 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.

References​

  1. RFP on OpenSourceMatters