digital.gov valid

U.S. Web Design System (USWDS)

USWDS is the design system for the U.S. federal government. It provides accessible, mobile-first HTML components, CSS utility classes, and design tokens, along with the design guidance and user research behind them. It is maintained by the Technology Transformation Services at the U.S. General Services Administration, and it helps agencies meet federal website standards. This file indexes the authoritative documentation at designsystem.digital.gov.

Visit publisher ↗

For agents: Index to USWDS, the U.S. federal government design system with accessible HTML components, CSS, design tokens and install and theming guides.

usws design system accessible html css components federal web standards sass

Authority: 64 reach 18 · trust 10 · quality 21 · freshness 15
Tier: listed
llms.txt: https://designsystem.digital.gov/llms.txt
Sections: 9
Links: 117
Size: 17335 bytes
Popularity rank: #6970
Registered: 2017-05-15
Country: — Publisher location unknown; CDN address excluded
Country evidence: No published address evidence collected yet
Categories: Design · Documentation and reference · Developer tools · Government and public services
For agents: Documentation: developer or product docs worth reading, nothing to call
Inferred actions: Read documentation About these labels
Audience: developers · agents can: read docs · en
First seen: 2026-10-18T15:08:53.022Z
Last checked: 2026-10-27T16:49:25.519Z
Badge

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T16:49:23.625Z. Cached copy · Source on digital.gov

# U.S. Web Design System (USWDS)

> USWDS is the design system for the U.S. federal government. It provides accessible, mobile-first HTML components, CSS utility classes, and design tokens, along with the design guidance and user research behind them. It is maintained by the Technology Transformation Services at the U.S. General Services Administration, and it helps agencies meet federal website standards. This file indexes the authoritative documentation at designsystem.digital.gov.

The current USWDS release is 3.14.0.

When writing code for a project that uses USWDS:

- Use the markup and class names published on the component's page. USWDS components carry keyboard behavior and accessibility semantics that hand-written markup does not reproduce.
- Reach for design tokens and utility classes before raw CSS values, so a project stays on the system's type scale, spacing units, and color palettes.
- Customize through Sass settings rather than by overriding compiled CSS.
- Do not introduce a React, Vue, or Angular wrapper unless the project already uses one. USWDS ships framework-independent HTML, CSS, and JavaScript; community implementations exist but are not maintained by the USWDS team.
- Using USWDS does not by itself make a site Section 508 compliant. Follow the accessibility guidance below, and run the accessibility tests published at `/components/{component}/accessibility-tests/` against the finished implementation.

## Start here

- [How to use USWDS](https://designsystem.digital.gov/how-to-use-uswds/): What the design system provides and how a team adopts it.
- [Getting started for developers](https://designsystem.digital.gov/documentation/getting-started-for-developers/): The three phases of adopting USWDS in a project.
- [Phase one: install](https://designsystem.digital.gov/documentation/getting-started/developers/phase-one-install/): Add USWDS to a project.
- [Phase two: compile](https://designsystem.digital.gov/documentation/getting-started/developers/phase-two-compile/): Compile USWDS Sass and assets.
- [Phase three: customize](https://designsystem.digital.gov/documentation/getting-started/developers/phase-three-customize/): Theme the design system for a project.
- [Developer documentation](https://designsystem.digital.gov/documentation/developers/): Installation, and how to use USWDS CSS and JavaScript.
- [Settings](https://designsystem.digital.gov/documentation/settings/): The Sass settings variables that tell USWDS how to build.
- [Packages](https://designsystem.digital.gov/components/packages/): Import only the components a project needs.
- [Getting started for designers](https://designsystem.digital.gov/documentation/getting-started-for-designers/): Design assets and how to use them.
- [Migrating to USWDS 3.0](https://designsystem.digital.gov/documentation/migration/): Moving a USWDS 2 project to Sass modules and unbundled packages.
- [Component lifecycle status](https://designsystem.digital.gov/components/status/): Which compo
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Domain	Title	Category	Country	Authority	llms.txt	llms-full.txt
atlassian.design	Atlassian Design System	documentation Design Developer tools Read documentation	—	62	✓	✓
colorsontheweb.com	Colors on the Web	documentation Design Read documentation Search content	US	51	✓
meshdesignsystem.com	Mesh Design System	documentation Design Documentation and reference Read documentation	—	46	✓
habitusnet.com	Design System Documentation (LLM Optimized)	documentation Design Read documentation	—	50	✓	✓
riverty.design	llms.txt - Riverty Design System	documentation Design Developer tools Read documentation Download data	ZA	52	✓
cloudscape.design	Cloudscape Design System - Documentation for LLMs	documentation Design Developer tools +1 Read documentation	—	51	✓
carbondesignsystem.com	Carbon Design System	documentation Design Documentation and reference +1 Read documentation	—	59	✓
wpwebinfotech.com	WPWeb Infotech	documentation AI and machine learning Business software Read documentation	IN	49	✓

Machine-readable: GET /v1/resolve?q=digital.gov · GET /v1/domain/digital.gov · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Own or manage this website?

If you own or manage digital.gov, you can update its listing and review file health, discovery activity and score history.

Manage this listing — optional

What verification unlocks

See how your site is discovered—and control what agents see.

See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.

Free. No account registration, backlink or payment required. Public discovery remains available without verification.

Verify your website—free

Preview the owner dashboard · All verification benefits

Let your coding agent verify it

If your coding agent is authorized to manage this website, paste these instructions into it.

Claim my listing on Agent Web Map for digital.gov:
1. POST https://agentwebmap.com/v1/sites/digital.gov/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://digital.gov/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/digital.gov/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/digital.gov).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.