Skip to main content

5b - Configurable Authoring Forms - Accessible UI & Documentation

Contractor: TBA

Main Contact: TBA

Start date: 1 September 2027

End data: 31 October 2027

RFP not published yet

Abstract​

By building the graphical management interface on the design system components from Milestone 2b, this milestone ensures that the configuration experience itself is fully accessible. Site administrators using assistive technologies can set up and manage editing profiles without barriers. For extension developers, the integration documentation means that third-party components can offer the same simplified, accessible editing experience, extending the benefit across the ecosystem.

Milestone 5b depends directly on the configuration system and internal API delivered in Milestone 5a, 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: Accessible Graphical Management Interface​

Establish an accessible graphical interface to manage field visibility and to configure different editing profiles. The interface must support, at a minimum, profile patterns such as:

  • A simplified profile for authors who only need title, text, and images
  • A full profile for administrators

Beyond these examples, the interface must allow site administrators to define their own profiles by selecting which fields appear in which editing context.

Deliverable 2: Configuration UI and Form Views Built on the Design System​

Build all configuration UI and the resulting form views using the design system components from Milestone 2b. The implementation must ensure WCAG 2.2 AA conformance, including:

  • Keyboard operability across all controls and flows
  • Screen-reader support, with proper labels, descriptions, and live-region behaviour where applicable
  • Proper labelling for grouped controls and complex form patterns
  • Validation 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

Deliverable 3: Extension Developer Integration Documentation​

Document how to integrate the form configuration system into extension developers' own components, so that third-party editing forms also benefit from customisable, accessible layouts. The documentation must include:

  • A clear overview of the Milestone 5a internal API as it is consumed by the Milestone 5b UI
  • At least one worked integration example for a third-party component
  • An accessibility checklist that extension developers can use to verify their own configurable forms

Deliverable 4: Documentation and Milestone Report​

Maintain the programme documentation framework and produce the milestone completion report in the format agreed at kick-off.