evidoria

← Back to browse

Good practice Imported

GOV.UK Design System — Four Years of Disabled-User Testing Behind the UK Government's Shared Components

United Kingdom · London · See the United Kingdom profile · See the London profile

Evidence: Descriptive / self-reported Top 10% 96/100 · Ask Evidence Copilot about this practice

Launched by GDS in 2018, the GOV.UK Design System requires WCAG 2.1 AA components tested with disabled users; three rounds of accessibility user research over four years now underpin components shared across hundreds of government services.

GOV.UK Design System — Four Years of Disabled-User Testing Behind the UK Government's Shared Components

Details

Maturity
Established
Promoter
Government Digital Service (GDS)
Period
2018-present
Keywords
digital government, design systems, accessibility research

Context

Launched by the UK's Government Digital Service (GDS) in July 2018, the GOV.UK Design System brings together design principles, accessible interface components and patterns that were previously scattered across separate government toolkits, so teams across UK government can build services from pre-tested, accessible-by-default building blocks.

Results

All components must pass WCAG 2.1 AA success criteria, verified through automated testing (jest-axe, axe-core/puppeteer) on every deployment plus manual checks. Over the four years to January 2023, the GDS accessibility team ran three dedicated rounds of user research testing components directly with disabled people and assistive-technology users, and the Design System underpins hundreds of services across UK government.

Conclusions

GDS's own strategy acknowledges that passing automated and component-level tests does not guarantee that every individual service built with the system is fully accessible in practice, since teams still must test their own service-specific content and flows.

Implementation
Indicative cost
Medium (€50k–€500k) — Sustained by a dedicated GDS accessibility team plus tooling; no published budget figure.
Time to results
Long (> 3 years) — Running continuously since July 2018 with no end date.
Staffing & skills
GDS accessibility team, cross-government service delivery teams

Conditions for success

  • binding WCAG 2.1 AA gate enforced on every component
  • automated regression testing (jest-axe, axe-core) on every deployment
  • direct user research with disabled and assistive-technology users

Common failure modes

  • individual services still must test their own content and flows; shared-component compliance does not guarantee whole-service accessibility

Where it fits

Governance type
national government
Scale
national
Income level
high-income

Commonly funded by

National / regional programmes

Indicative funding routes for practices of this type — always check each programme's current calls and eligibility rules.

Replication kit

Reusable artefacts from this practice — as published by their sources.

Do you run this practice? Claim it — verified implementers get a public contact pathway and can propose corrections.

Data sources

Where this practice's information was retrieved from, and when.

Attachments

Similar practices you may find useful