3a - Frontend Template Build
Contractor: TBA
Main Contact: TBA
Start date: 1 March 2027
End data: 30 April 2027
RFP not published yet
Abstract
By building the new template entirely on the design system from Milestone 2, this milestone proves that the framework-agnostic approach works end-to-end and creates a reference implementation that template developers across the ecosystem can follow. Running this in parallel with the backend template (Milestone 3b) means both are ready for integrated validation in Milestone 3c without a sequencing delay.
Milestone 3a depends on the stable versioned design system delivered in Milestone 2b (tokens, core components, and complex components) and on the test protocols and acceptance criteria established in Milestone 1a.
Scope of work
Deliverable 1: WCAG 2.2 AA-Conformant Frontend Template
Produce a new WCAG 2.2 AA-conformant frontend template for Joomla core, built entirely on the design system and design tokens from Milestone 2 and serving as the reference implementation for accessible Joomla templates. The template must:
- Be built exclusively on the design tokens and components from Milestone 2 (no parallel, template-specific styling or component duplication)
- Conform to WCAG 2.2 AA across all template positions, module styles, layouts, and view overrides shipped with the template
- Support RTL layouts, responsive mobile behaviour, and reduced-motion preferences
- Be validated against the test protocols and AT/browser combinations defined in Milestone 1a (minimum matrix: NVDA + Chrome, JAWS + Edge, VoiceOver + Safari), with results recorded against the acceptance criteria
- Be delivered as a Joomla core template, ready for integrated validation in Milestone 3c alongside the backend template from Milestone 3b
Deliverable 2: Documentation and Milestone Report
Maintain the programme documentation framework and produce the milestone completion report in the format agreed at kick-off. This deliverable also includes template-level documentation (positions, layouts, view overrides, and the accessibility rationale for design choices) suitable for downstream template developers using this template as a reference.