The U.S. Web Design System (USWDS) is the design system of the US federal government, created by 18F and the U.S. Digital Service in 2015 and maintained by GSA's Technology Transformation Services. It provides usa- components such as the official government banner, design tokens and the Public Sans typeface, and it is the way agencies meet the website standards the 21st Century IDEA Act requires.
U.S. Web Design System (USWDS)
Details
- Full Name
-
U.S. Web Design System (USWDS), formerly the U.S. Web Design Standards
- Also known as
-
USWDS
Core Concepts:
-
The official government banner. "An official website of the United States government", the
usa-bannerat the top of the page; "most government sites should use the banner" (Banner). -
Components with the
usa-prefix.usa-header,usa-button,usa-alert,usa-accordion,usa-step-indicatorand form components, in the npm package@uswds/uswds. -
Design tokens as Sass settings. Theme colours and fonts are set by tokens such as
$theme-color-primary: "blue-60v"and$theme-font-type-sans. -
Public Sans. A typeface designed for the system by Dan Williams, based on Libre Franklin, released with USWDS 2.0 in 2019 (AIGA Eye on Design); Source Sans Pro and Merriweather ship as alternatives.
-
Accessibility and plain language as defaults. Components are built to meet Section 508, and the guidance covers forms, step-by-step services and content.
- Key Proponents
-
18F and the U.S. Digital Service, which created it in 2015; maintained by the Digital Services Division of GSA’s Technology Transformation Services (About). Version 2.0 came in 2019, version 3.0 in 2022
When to Use:
-
Building US federal, state or city government services. In our prior test, every anchor run of a parking-permit service set the government banner, a step indicator and
usa-form components. Both Opus baselines usedusa-classes even without the name, one of them with the banner; the Haiku and Sonnet baselines did not. -
As the US counterpart to the GOV.UK Design System when a service must look and behave like government
-
Meeting the federal website standards: agencies must follow GSA’s standards under the 21st Century IDEA Act, and USWDS is how the standards are met (Website standards)
Common Misunderstandings:
-
Thinking the law names USWDS. The 21st Century IDEA Act requires the website standards; the standards point to USWDS.
-
Using the banner on every site. The banner is for official government sites, and the guidance says some sites should not use it.
-
Expecting the GOV.UK patterns. USWDS has its own components and fewer service patterns; one question per page is GOV.UK’s pattern, not a USWDS rule.
Criticism:
-
Automated testing instead of people. In September 2026 a new team proposed automating the system’s accessibility testing. Matt Henry, former USWDS engineering lead, objected: "It is about what a human would experience" (Madison Alder, "A Trump team wants to automate U.S. Web Design System accessibility testing. Experts are worried.", FedScoop, 2026).
-
One defect reaches thousands of sites. An open letter from a coalition of technologists warns: "One accessibility defect, performance issue, or security vulnerability in USWDS can put thousands of systems at risk" (FedScoop, 2026).
Current Status:
-
Governance in dispute. In September 2026 GSA put the system’s longtime lead on leave and handed the repository to an engineer from the Treasury Department (Christian Robles, Nextgov/FCW); nearly 200 technologists announced a hard fork, while GSA said prior administrations had let USWDS deteriorate (Nextgov/FCW, October 2026). The latest release is 3.14.0 of 18 August 2026. The prior describes the system as it was before the dispute; check which repository and release you build on.
