Government Design Systems

Government design systems are arguably the most successful sustained civic-tech win of the last fifteen years. The US Web Design System, GOV.UK Design System, and their international cousins are MIT-licensed, accessibility-tested, and quietly running thousands of public services. Pair with Civic Tech Overview, UI Component Libraries, Accessibility Testing, Color & Theming, and Forms.

US

• ★ ★ USWDS (US Web Design System) — public domain (CC0-equivalent / no rights reserved); HTML/CSS/Sass; built by 18F + USDS (now somewhat reorganized post-2025). Used across whitehouse.gov, sec.gov, va.gov, login.gov, IRS digital services, and most modern federal redesigns. Section 508-compliant by default. Maintained on GitHub by GSA. Version 3.x in 2026.
• CMS Design System (HHS / Centers for Medicare & Medicaid Services) — MIT; healthcare.gov / medicare.gov foundation; React + Sass; built on top of USWDS principles.
• VA Design System (Department of Veterans Affairs) — MIT; va.gov; React; one of the most mature US federal design systems alongside USWDS.
• Login.gov design tokens — MIT; consumed via USWDS.
• California Design System — MIT; built on USWDS; powers california.gov.
• NYC Web Performance Toolkit / NYC Design System — partial; NYC-specific.

UK

• ★ ★ GOV.UK Design System — MIT; HTML/CSS; built by Government Digital Service (GDS). The original "let's do this seriously" gov design system (2012-era predecessor; current GDS public DS launched 2018). Used across nearly all UK gov.uk service domains. Notoriously rigorous accessibility + research — every pattern has user-research evidence behind it.
• ★ GOV.UK Frontend — MIT; the actual implementation library.
• ★ GOV.UK Prototype Kit — MIT; Express-based prototype kit for service designers; widely used inside GDS.

Canada

• ★ GC Design System / Canada.ca DS — MIT; bilingual (EN/FR); built by Canadian Digital Service / Treasury Board Secretariat; React + Web Components; covers canada.ca.

Australia

• ★ Australian Government Design System — MIT; "Gold" components; built by Digital Transformation Agency (DTA); React + Web Components.

Singapore

• ★ Singapore Government Design System (SGDS) — MIT; built by GovTech Singapore; React; powers singpass / gov.sg properties. SGDS is one of the most ambitious because GovTech Singapore is genuinely well-funded and runs on it.

Other notable

• New Zealand Design System — MIT; smaller but well-maintained.
• Ontario Design System (Canada province) — MIT.
• Scottish Government Design System — MIT; built on GOV.UK Frontend.
• France's Système de Design de l'État (DSFR) — MIT; built by SIG (state information service); marianne / french-flag color palette; used across .gouv.fr.
• NL Design System — Netherlands; community-led across municipalities.
• Italian Design System (designers.italia.it) — AGPL-3.0; Italian gov; well-maintained.
• Estonia, Finland, Norway — each has a maintained gov DS; smaller but principled.

What government design systems actually deliver

• ★ Accessibility by default — typically WCAG 2.1 AA-tested patterns; the components have been tested with screen-reader users. Worth more than 90% of corporate design systems on this dimension. See Accessibility Testing.
• ★ Plain-language patterns — radio buttons / error summaries / form layouts honed against actual user research with citizens at all literacy levels.
• ★ Print + email-safe styles — services print correctly, mail clients render notifications correctly.
• Permissive licensing — MIT or public domain across the board; a private startup can adopt USWDS or GOV.UK Frontend without licensing concern.
• Living style guides + research repositories — GOV.UK in particular publishes the user research behind every component change.

Honest take (2026)

• GOV.UK Design System is the gold standard of the category — quality of research + writing + components is unmatched.
• USWDS is the clear US leader — politically resilient (it survived the 2017–21 and 2025+ administrations), well-maintained, and broadly adopted.
• Singapore's SGDS deserves more attention — it's quietly one of the most polished and best-funded.
• You can absolutely use these for non-government work. A non-profit / NGO / civic-tech project that adopts USWDS gets an entire accessibility + i18n / l10n story for free.
• The post-2025 USDS / 18F reorganization has slowed USWDS development but not killed it; the codebase is on GitHub with broad contributor base.

Pick this if…

• You're building a US gov-facing or gov-adjacent service: USWDS.
• You're building a UK gov-facing service: GOV.UK Design System (mandatory for service-standard certification).
• You're a civic-tech project that wants accessibility-by-default: USWDS or GOV.UK Frontend; either is a defensible default.
• You want to learn how to do design-system documentation right: read the GOV.UK Design System docs as a reference.
• You're internationally distributed: Singapore SGDS or France DSFR are good non-Anglophone references.
• You don't need any of this: a corporate design system from UI Components is fine — but the gov ones are surprisingly good general-purpose foundations.