USWDS components used where applicable

OMB M-23-22 requires federal agencies to use USWDS components — not just tokens — to create the consistent, trustworthy experience the public expects from .gov sites. Custom or third-party component libraries (Bootstrap, Material UI, shadcn) introduce component patterns that differ from the established federal design language, forcing citizens to re-learn interaction patterns when moving between agency sites. More critically, third-party components often fail USWDS accessibility validation: USWDS button, input, and alert components are built to Section 508 and WCAG 2.1 AA specifications that custom implementations routinely miss.

Replace custom UI elements with USWDS equivalents. Start with the highest-traffic components: buttons, form inputs, and alerts. Target at least 50% usa-* class coverage across all UI component files.

// Before: custom button
<button className="btn-primary">Apply Now</button>

// After: USWDS button
<button className="usa-button">Apply Now</button>

// Before: custom text input
<input className="form-field" type="text" />

// After: USWDS input
<input className="usa-input" type="text" />

For the navigation and footer — the most visible agency-identity components — adopt usa-nav and usa-footer directly. Reference the USWDS component library at designsystem.digital.gov for markup patterns, and run the USWDS Compliance Checker to measure usa-* class coverage.