Release notes

The Design System is an ever-evolving product. We’ve been listening to your feedback and using it as a basis for improvements and additions.

Here you’ll find our release notes — summaries of bug fixes, new features, and other updates introduced in each release.

Have suggestions for a new feature or bug fix? Open an issue in our repo.

Version 2.10.0 Alpha 0

September 25, 2020

Alpha release for testing only.

Version 2.10.0 Beta 0

September 28, 2020

About 2.10.0 Beta 0

This release is a port of USWDS 2.9.0 to the most recent Sass syntax, the Sass Module System [SaMS]. This new syntax allows a couple specific improvements to the design system:

There’s a lot of reorganization under the hood to reflect our focus on modularity (and more to come as the beta integrates a new library structure) but this reorganization should have minimal impact on how you load and use the design system. Just how you load the new code depends on how extensively you want to use namespacing or subsetting

⚠️ Note: Throughout this guidance, we’ll be referring to the Sass entry point, your project’s .scss file that points the compiler to the files it needs to compile the design system CSS. If this is an unfamiliar concept we discuss it in greater detail in our USWDS Fundamentals and quickstart guide.


This currently requires a compile path that uses Dart Sass.

⚠️ Note: Many compilers based on libsass or other libraries do not fulfill these requirements. Notably, this includes the native compiler built into Jekyll (jekyll-sass-converter), node-sass, and likely others. If this beta package doesn’t work for you, it’s probably due to this requirement. We’re working to see what kinds of compile workarounds are possible in the most common environments. Your feedback and experimentation during the beta process will help us evaluate the practicality of integrating SaMS into USWDS.


The most important thing to remember is that you can’t use @import in the same file that you use a new SaMS rule like @use or @forward. Each individual file can play by its own rules, but you can’t mix old and new rules in any individual file. In effect, mixed implementations need to create a SaMS entry point imported from the primary Sass entry point. In the examples below, we’ve named that SaMS entry point theme-modules.

Note: In mixed implementations, the SaMS entry point must @forward either uswds or a USWDS package (like packages/uswds-core) to apply the imported settings upstream of using @use to load mixins and functions into a stylesheet.

Additionally, each example in this section assumes that you’re keeping all your project sass files in a single directory in the project root. Your project can have a different structure, you’d just have to adjust the load paths to fit.

Simple: Use USWDS as in earlier versions

You should be able to use this beta release without making any changes to your Sass entry point. Conventional @import rules will work with this release just as they did with earlier USWDS releases.

// styles.scss
@import "uswds-theme-general";
@import "uswds-theme-typography";
@import "uswds-theme-spacing";
@import "uswds-theme-color";
@import "uswds-theme-utilities";
@import "uswds-theme-components";
@import "../node_modules/uswds/dist/uswds";
@import "uswds-theme-custom-styles";

Intermediate: Package subsetting

Subsetting means loading only the packages and styles you need for your project. Each USWDS component has a package (typically the same as its class name, usa-[component]). There are also a few special packages:

package description
uswds-components all components
uswds-core only the USWDS core internals — tokens, functions, and mixins
uswds-elements limited styling for unclassed html elements
uswds-fonts the font-face generator
uswds-form-controls all form controls
uswds-form-templates all form templates
uswds-global core, elements, and helpers + normalize
uswds-helpers non-utility helper classes, like usa-sr-only and usa-focus
uswds-layout-grid the layout grid classes
uswds-typography styles related to text and headings
uswds-utilities utility classes
uswds-validation components related to form validation

Find packages in the dist/packages directory in the USWDS npm package.

// styles.scss
@import "uswds-theme-general";
@import "uswds-theme-typography";
@import "uswds-theme-spacing";
@import "uswds-theme-color";
@import "uswds-theme-utilities";
@import "uswds-theme-components";
@import "theme-modules";
@import "uswds-theme-custom-styles";
// theme-modules.scss

@forward "../node_modules/uswds/dist/packages/usa-banner";
@forward "../node_modules/uswds/dist/packages/usa-identifier";
@forward "../node_modules/uswds/dist/packages/usa-button";
@forward "../node_modules/uswds/dist/packages/uswds-form-controls";

Intermediate: Namespacing

Namespacing adds a custom prefix to variables, mixins, and functions loaded with the @use rule. Use custom namespacing to prevent collisions between similarly-named functionality in multiple libraries.

// styles.scss
@import "uswds-theme-general";
@import "uswds-theme-typography";
@import "uswds-theme-spacing";
@import "uswds-theme-color";
@import "uswds-theme-utilities";
@import "uswds-theme-components";
@import "theme-modules";
// theme-modules.scss
@forward "../node_modules/uswds/dist/uswds";
@forward "theme-custom-styles";
// theme-custom-styles.scss
@use "../node_modules/uswds/dist/uswds" as usa;
.foo {
  @include usa.u-margin-x(1)
  color: usa.color("primary-vivid");

Intermediate: Package subsetting and custom namespace

You can also do both subsetting and namespacing with a hybrid implementation.

// styles.scss
@import "uswds-theme-general";
@import "uswds-theme-typography";
@import "uswds-theme-spacing";
@import "uswds-theme-color";
@import "uswds-theme-utilities";
@import "uswds-theme-components";
@import "theme-modules";

In the SaMS entry point, include both packages and custom styles.

// theme-modules.scss
@forward "theme-packages";
@forward "theme-custom-styles";

For packages, include individual component packages…

// theme-packages.scss
@forward "../node_modules/uswds/dist/packages/usa-banner";
@forward "../node_modules/uswds/dist/packages/usa-identifier";
@forward "../node_modules/uswds/dist/packages/usa-button";
@forward "../node_modules/uswds/dist/packages/uswds-form-controls";

…or include just the USWDS core internals

// theme-packages.scss
@forward "../node_modules/uswds/dist/packages/uswds-core";

Load custom styles as before, using the uswds-core package with the desired namespace.

// theme-custom-styles.scss
// Use packages/uswds-core to include core internals only
@use "../node_modules/uswds/dist/packages/uswds-core" as usa;
.foo {
  @include usa.u-margin-x(1)
  color: usa.color("primary-vivid");

Advanced: Use native SaMS instead of imports

The big change in using a SaMS-only implementation is that your packages forward needs to include all changed settings as a single map object passed as its config.

// styles.scss
@forward "theme-modules--packages" with (
  $theme-show-notifications: false,
  $theme-color-primary-vivid: "orange-20v",
@forward "theme-modules--custom";

Include any packages or USWDS core internals, as before.

// theme-modules--packages.scss

@forward "../node_modules/uswds/dist/packages/usa-banner";
@forward "../node_modules/uswds/dist/packages/usa-identifier";
@forward "../node_modules/uswds/dist/packages/usa-button";
@forward "../node_modules/uswds/dist/packages/uswds-form-controls";
// or
@forward "../node_modules/uswds/dist/packages/uswds-core";

Include any packages or USWDS core internals, as before.

// theme-modules--custom.scss
@use "../node_modules/uswds/dist/packages/uswds-core" as usa;
@forward "custom-styles-one";
@forward "custom-styles-two";

Each custom styles file needs to @use the uswds-core package.

// custom-styles-one.scss
@use "../node_modules/uswds/dist/packages/uswds-core" as usa;
.foo {
  @include usa.u-margin-x(1)
  color: usa.color("primary-vivid");

Stylesheets can reference other sheets if they @use that stylesheet explicitly.

// custom-styles-two.scss
@use "../node_modules/uswds/dist/packages/uswds-core" as *;
@use "custom-styles-one" as *;
.bar {
  @extend .foo;
  @include u-margin-y(1)
  color: color("secondary-vivid");

What we expect from a beta tester

Version 2.9.0

September 22, 2020

What’s new in USWDS 2.9.0

New components

We have three new components in this release. Learn more about each of them on our website:

Improvements and bug fixes

Added flex-align-self utilities. Now you can apply the align-self property to an element using flex-align-self utilities. The align-self rule is conceptually similar to flex-align, except align-self applies at the flex child level instead of the flex parent level. Thanks @taylorsolomon! (https://github.com/uswds/uswds/pull/3588)

Added an accent-warm button variant. Now you can use accent-warm buttons with usa-button--accent-warm. (https://github.com/uswds/uswds/pull/3623)

Generating SHA-256 hashes for our ZIP releases. We’re now generating a SHA-256 hash with the ZIP download and documenting this hash in our repo and on our website. Anyone can now check the integrity of a release ZIP file by generating a hash for their local file and comparing it to the hash we post in the github repo and on our site. (https://github.com/uswds/uswds/pull/3577)

Proper disabled radio buttons. We fixed the display of disabled radio buttons so both the label and radio button both appear disabled. Thanks @brayfe! (https://github.com/uswds/uswds/pull/3613)

Proper secondary button active state. We fixed the active state of the secondary color button. Thanks @maya! (https://github.com/uswds/uswds/pull/3615)

Improved styling of lists inside alerts. We improved the styling of simple and complex lists inside alerts. (https://github.com/uswds/uswds/pull/3507)

More consistent styling of legend element. We improved the styling of the usa-legend element to better match other labels in a form, and improved the spacing between legends and both radio buttons and checkboxes. We added a usa-label--large variant to mimic the older, less consistent styling for backward compatibility. (https://github.com/uswds/uswds/pull/3465)

Dependencies and security

package old new
@babel/preset-env 7.11.0 7.11.5
@types/node 14.0.27 14.11.1
axe-core 4.0.1 4.0.2
eslint 7.6.0 7.9.0
mocha 8.1.1 8.1.3
prettier 2.1.1 2.1.2
sass 1.26.10 1.26.11
stylelint 13.6.1 13.7.1
typescript 3.9.7 4.0.3
yargs 15.4.1 16.0.3

0 vulnerabilities in regular dependencies (dependencies for USWDS projects installed with npm install uswds) 3 low, 2 high vulnerabilities in devDependencies (development dependencies)

Release ZIP SHA-256 hash: 4b3928e5a292ee4a2ac0b1a5106c179c4cfadd9355e56f5fb6b8e6e1954cfdb2

Version 2.8.1

August 17, 2020

What’s new in USWDS 2.8.1

Improvements and bug fixes

Allow custom colors in link calculations. Now projects that use custom hex colors in their theme colors can generate CSS without errors. For standard USWDS tokens, the link color calculator generates a hover color one system grade level above or below the link color in the same vivid state. Now the calculator does the same with custom hex theme tokens, except using the theme color grades. (https://github.com/uswds/uswds/issues/3568)

Added a max-width setting to the footer. We added a $theme-footer-max-width setting to constrain the footer content, similar to what we already provide for the banner. (https://github.com/uswds/uswds/issues/3532)

Improved date picker focus state. We fixed a bug that cut off part of the date picker’s date focus ring in IE11. (https://github.com/uswds/uswds/issues/3578)

Improved combo box resizing. We fixed a display bug with the combo box where custom combo box sizing wasn’t reflected in its input. Thanks @fafnirical! (https://github.com/uswds/uswds/pull/3583)

Improved combo box dropdown overlapping. We fixed a display bug with the combo box where neighboring combo box UI elements could overlap with the combo box dropdown. Thanks @Pharmasolin! (https://github.com/uswds/uswds/pull/3572)

Dependencies and security

package | old | new – | – | – elem-dataset | 1.1.1 | 2.0.0 @babel/preset-env | 7.10.4 | 7.11.0 @types/node | 13.13.13 | 14.0.27 autoprefixer | 9.8.4 | 9.8.6 browserify | 16.5.1. | 16.5.2 eslint | 5.16.0 | 7.6.0 eslint-config-airbnb-base | 13.2.0 | 14.2.0 gulp-eslint | 5.0.0 | 6.0.0 gulp-rename | 1.2.2 | 2.0.0 jsdom | 16.2.2 | 16.4.0 mocha | 7.2.0 | 8.1.1 node-notifier | 6.0.0. | 8.0.0 prettier | 1.19.1 | 2.0.5 resemblejs | 3.2.4 | 3.2.5 sinon | 7.5.0 | 9.0.3 typescript | 2.4.1 | 3.9.7 yargs | 15.4.0 | 15.4.1

0 vulnerabilities in regular dependencies (dependencies for USWDS projects installed with npm install uswds) 3 low, 2 high vulnerabilities in devDependencies (development dependencies)

Version 2.8.0

July 09, 2020

What’s new in USWDS 2.8.0

New components

We’re excited to release a new batch of components. Learn more about each of them on our website:

Updates to the banner

We’ve made some important updates to the banner text. Our new banner text incorporates feedback we’ve received over the last year or so, and incorporates a few key enhancements:

Teams should work to update this banner text as soon as possible. Consistency improves the reliability, trustworthiness, and awareness of this important component. Thanks @h-m-f-t, @konklone, @wslack, @lggsa, and @leilanimartinez!

These banner updates also include better settings support for the banner, including support for custom banner background and link colors, and improved readability at wide display widths.

⚠️ The banner code requires Autoprefixer to work properly. See https://designsystem.digital.gov/documentation/developers/#sass-compilation-requirements

.gov domains

| Official websites use .gov | Secure .gov websites use HTTPS | — | — | A .gov website belongs to an official government organization in the United States. | A lock (🔒) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

.gov domains (Spanish)

| Los sitios web oficiales usan .gov | Los sitios web seguros .gov usan HTTPS | — | — | Un sitio web .gov pertenece a una organización oficial del Gobierno de Estados Unidos. | Un candado (🔒) o https:// significa que usted se conectó de forma segura a un sitio web .gov. Comparta información sensible sólo en sitios web oficiales y seguros.

.mil domains

| Official websites use .mil | Secure .mil websites use HTTPS | — | — | A .mil website belongs to an official U.S. Department of Defense organization. | A lock (🔒) or https:// means you’ve safely connected to the .mil website. Share sensitive information only on official, secure websites.

.mil domains (Spanish)

| Los sitios web oficiales usan .mil | Los sitios web seguros .mil usan HTTPS | — | — | Un sitio web .mil pertenece a una organización oficial del Departamento de Defensa de EE. UU. | Un candado (🔒) o https:// significa que usted se conectó de forma segura a un sitio web .mil. Comparta información sensible sólo en sitios web oficiales y seguros.

New settings

Setting | Accepts | Default | Usage – | – | – | — $theme-link-reverse-color | color token | "base-lighter" | Default link color for reverse (dark) backgrounds $theme-link-reverse-hover-color | color token | "base-lightest"| Default link hover color for reverse (dark) backgrounds $theme-link-reverse-active-color | color token | "white"| Default link hover color for reverse (dark) backgrounds $theme-banner-background-color | color token | "base-lightest" | Banner background color $theme-banner-link-color | color token or default | default | Banner link color. default uses the value in $theme-link-color. The system will calculate hover, active, and visited states. $theme-breadcrumb-background-color | color token | “white” | Breadcrumb background color. Note that the system needs to evaluate color contrast, so this cannot be any transparent-based token. $theme-breadcrumb-font-size | font size token | “sm” | Breadcrumb font size $theme-breadcrumb-font-family | font family token | “body” | Breadcrumb font family $theme-breadcrumb-link-color | color token or default | default | Breadcrumb link color. default uses the value in $theme-link-color. The system will calculate hover, active, and visited states. $theme-breadcrumb-min-width | spacing token | "mobile-lg" | Breakpoint at which the breadcrumb switches to non-mobile display $theme-breadcrumb-padding-bottom | spacing token | 2 | Breadcrumb bottom padding $theme-breadcrumb-padding-top | spacing token | 2 | Breadcrumb top padding $theme-breadcrumb-padding-x | spacing token | 0 | Breadcrumb left and right padding $theme-breadcrumb-separator-color | color token | "base" | Color of the breadcrumb chevron separator

Dependencies and security

package old new
@types/node 13.13.12 13.13.13
yargs 15.3.1 15.4.0
@babel/preset-env 7.10.2 7.10.4
autoprefixer 9.8.0 9.8.4
axe-core 3.5.4 3.5.5
chrome-launcher 0.13.3 0.13.4
eslint-plugin-import 2.21.2 2.22.0
sass 1.26.8 1.26.10
stylelint 13.6.0 13.6.1
stylelint-config-prettier 8.0.1 8.0.2
stylelint-scss 3.17.2 3.18.0

Version 2.7.1

June 17, 2020

What’s new in USWDS 2.7.1

Improvements to combo box

We listened to your feedback and made a number of improvements and upgrades to our new combo box.

Show proper focus in combo box. Hover and keyboard events transfer focus to individual options, and now the styling reflects that. (https://github.com/uswds/uswds/pull/3493)

Disabled combo boxes remain disabled after enhancement. The disabled attribute now correctly results in a disabled combo box. (https://github.com/uswds/uswds/pull/3484)

Use data attributes to set combo box placeholder and default. We now use data attributes to set the default value (data-default-value) and placeholder (data-placeholder). (https://github.com/uswds/uswds/pull/3486)

Improved combo box interactions. Allows list toggling with the toggle button, and adds a “clear input” button to start a subsequent combo box interaction. Makes a number of additional improvement to how the combo box handles changes and new selections. (https://github.com/uswds/uswds/pull/3505)

Combo box now triggers a change event on input and select change. Now we fire proper change events on the <select>. Thanks @ConnorDY! (https://github.com/uswds/uswds/pull/3487)

We fixed the punctuation on the default combo box. Now there’s no more colon, consistent with other input guidance. (https://github.com/uswds/uswds/pull/3473)

The combo box scrollbar works. Now you can scroll a combo box with the scrollbar! (https://github.com/uswds/uswds/pull/3483)

Other improvements and bug fixes

Improved the reliability and cross-browser compatibility of our flexbox usage. We rebuilt how the design system outputs its flex utilities and mixins so any flex-based rules display properly and as expected in browsers from IE11 up. (https://github.com/uswds/uswds/pull/3480)

Improve display of media block. This element now uses flexbox instead of floats, so text in a media block is no longer cut occasionally cut off at the end of a line in IE11. Thanks @maya! (https://github.com/uswds/uswds/pull/3453)

Mobile menus can now be closed with the esc key in IE11. Now, the escape key will properly close mobile menus in IE11. Thanks @joncasey! (https://github.com/uswds/uswds/pull/3468)

Improved our Autoprefixer and Browserslist settings. We added not dead to our Autoprefixer settings and now use a .browserslistrc file for these options. This gets us more in line with Autoprefixer and Browserslist best practices. Thanks @ai! (https://github.com/uswds/uswds/pull/3458)

Fixed IE11 display issue in mobile nav. Now nav elements display as expected at mobile width on IE11. (https://github.com/uswds/uswds/pull/3470)

Fixed a potential Unhandled rejection Parsing error in the codebase. Thanks @hursey013! (https://github.com/uswds/uswds/pull/3497)

Added role="img" to SVG images. Thanks @sslawrence521! (https://github.com/uswds/uswds/pull/3501)

Fixed spacing in nested lists. Now nested lists will have proper formatting and spacing regardless of the value of $theme-global-content-styles. Thanks @jonraedeke! (https://github.com/uswds/uswds/pull/3495)

Fixed a color contrast issue in our accent-cool button. Now all our buttons have the proper AA contrast between the button background and the button text. And we’ve built our code to be smart enough to adjust the text color to adapt to any project’s theme color definitions. (https://github.com/uswds/uswds/pull/3492)

To better provide resilience in our color contrast, we’re introducing two new mixins to help provide a more resilient codebase:

@include set-text-from-bg( 

@include set-text-and-bg( 

preferred-text-color default: "white"
fallback-text-color default: "ink"
WCAG-level default: "AA"


For a given background-color token, each mixin checks contrast against the preferred-text-color and uses that as the text color unless it doesn’t pass the contrast requirements of the WCAG-level. Then it checks fallback-text-color and uses that color unless it doesn’t meet contrast requirements, in which case it returns an error.

set-text-from-bg(): Sets only the text color. set-text-and-bg(): Sets both the background color and the text color.

Dependencies and security

package old new
@types/node 13.9.1 13.13.12
@babel/preset-env 7.8.7 7.10.2
@frctl/fractal 1.2.1 1.3.0
@frctl/nunjucks 2.0.1 2.0.2
autoprefixer 9.7.4 9.8.0
axe-core 3.5.2 3.5.4
browserify 16.5.0 16.5.1
chrome-launcher 0.13.2 0.13.3
chrome-remote-interface 0.28.1 0.28.2
cross-spawn 7.0.1 7.0.3
eslint-config-prettier 6.10.0 6.11.0
eslint-plugin-import 2.20.1 2.21.2
gulp-cli 2.2.0 2.3.0
gulp-sass 4.0.2 4.1.0
jsdom 16.2.1 16.2.2
mocha 7.1.12 7.2.0
nyc 15.0.0 15.1.0
sass 1.26.3 1.26.8
stylelint 13.2.1 13.6.0
stylelint-scss 3.15.0 3.17.2

Version 2.7.0

May 11, 2020

What’s new in USWDS 2.7.0

New components

Read more about these components on our website, but we’re excited to start releasing the first of a number of new design system components planned for 2020:

Improvements and bug fixes

Improved mobile experience for numeric fields. We updated our guidance and code for numeric fields to follow the lead of gov.uk’s recent guidance and research. This updates those fields to use text rather than number inputs with an inputmode of numeric. (https://github.com/uswds/uswds/pull/3392)

Fixed color token errors. We made some mistakes adding the new color tokens into the system in 2.6.0. Now the values of Indigo cool 60v, Indigo cool 70v, and Indigo cool 80v fall within our grade guidance, and match both the documentation and the design assets. (https://github.com/uswds/uswds/pull/3455)

Improved styling of Skipnav component. Now the Skipnav includes proper link formatting. (https://github.com/uswds/uswds/pull/3393)

Improved display of the Here's how you know link in the gov banner. Now there’s no distracting change to the length of the underline on hover. (https://github.com/uswds/uswds/pull/3427)

Assure external link icon wraps properly. Now the external link icon won’t get stranded as a widow on a new line. It will break to a new line only with its link text. (https://github.com/uswds/uswds/pull/3428)

Provide a more reliable treatment for dropdown menus. Now dropdown menus won’t get cut off if they come too close to the header boundary (https://github.com/uswds/uswds/pull/3438) and menus with usa-current nav elements won’t display an unnecessary underline at desktop widths (https://github.com/uswds/uswds/pull/3434).

Dependencies and security

package old new
chrome-launcher 0.12.0 0.13.2
handlebars 4.7.3 4.7.6
mocha 7.1.0 7.1.2

Version 2.6.0

March 18, 2020

Use more consistent search markup. We made the markup of usa-search more consistent and assured that the styling worked properly regardless of what version of the markup you’re using. This is not as breaking change, but we recommend updating your search markup to the most current version. (https://github.com/uswds/uswds/pull/3327)

Utilities output specified pseudoclasses correctly. We fixed a bug that prevented the utilities from outputting certain pseudoclass prefixes like active:, visited: and focus:. (https://github.com/uswds/uswds/pull/3346) Thanks @greenca6!

Improved letterspacing function. This fixes a bug that caused the letterspacing functions to output the wrong value for 1. Now the utilities and the functions output the same values. (https://github.com/uswds/uswds/pull/3343) Thanks @maya!

Provide complete vivid color families. Now each color family has vivid grades from 5-80. Changing families in settings is more reliable and will no longer result in pointing to false values. Each new color is normalized to our new color grade luminance range guidance. (https://github.com/uswds/uswds/pull/3351) Thanks @jlarmstrongiv!

Provide a more reliable and consistent color system. Each new color is normalized to our new color grade luminance range guidance, so all magic number combinations will work as promised. (https://github.com/uswds/uswds/pull/3351) Thanks @darekkay!

Standard color wheel 2.6.0

uswds-standard-color-wheel-2 6 0

Vivid color wheel 2.6.0

uswds-vivid-color-wheel-2 6 0

changed-colors-in-2 6 0

Dependencies and security

package old new
@types/node 13.5.0 13.9.1
@babel/preset-env 7.7.6 7.8.7
yargs 12.0.5 15.3.1
autoprefixer 9.7.3 9.7.4
axe-core 3.4.1 3.5.2
eslint-config-prettier 6.7.0 6.10.0
eslint-plugin-import 12.19.1 12.20.1
gulp-stylelint 10.0.0 13.0.0
handlebars 4.5.3 4.7.3
jsdom 16.0.1 16.2.1
resemblejs 3.2.3 3.2.4
sass 1.25.0 1.26.3
stylelint 11.1.1 13.2.1
stylelint-config-prettier 6.0.0 8.0.1
stylelint-config-recommended-scss 4.1.0 4.2.0
stylelint-scss 3.13.0 3.15.0

Updated our recommended version of Node to the current LTS (12.16.1)

Version 2.5.1

March 03, 2020

Removed media query sorting. CSSO’s forceMediaMerge wasn’t exporting media queries in the expected order, so we’re disabling it for more reliable CSS output. While both the minified and unminified CSS files are modestly larger as a result: 268 KB unsorted vs. 259 KB sorted, our testing indicates that once the files are compressed server side with gzip, the unsorted CSS is actually smaller: 36 KB unsorted and gzipped vs. 38 KB sorted and gzipped. As a result, we recommend that teams do not use media query sorting at this time.

Note: This release also temporarily removes the best practice tests from our aXe testing until we can reinstate these tests as warnings rather than errors (#3333). This aXe change should come in the next minor version this month (2.6.0).

Version 2.5.0

February 14, 2020

What’s new in USWDS 2.5.0

:warning: Improved component accessibility and testing. We upgraded our accessibility testing with aXe from 2.6.1 to 3.4.1 and improved the accessibility of our markup in the process. This introduces minor changes to the markup of 5 components and our documentation template — you should update your markup, but existing markup will not break:

PR: https://github.com/uswds/uswds/pull/3280

Allow non-token values in state color settings. Now state tokens (like "warning") can accept non-token colors, just as we introduced for theme colors in 2.4.0. Teams using non-token values can now keep colors consistent between theme and state. Using non-token values will throw a warning in the compile process, but this, like all compile warnings, can be disabled by setting $theme-show-compile-warnings: false. Thanks @sawyerh! https://github.com/uswds/uswds/pull/3289

Updated to the canonical Sass compiler. We’re now using Dart Sass to compile the system Sass. Dart Sass is the canonical Sass compiler, so using it will keep us at feature parity and help prevent inadvertent inconsistencies. https://github.com/uswds/uswds/pull/3304

Output utility classes in proper order without media query sorting. We no longer require media query sorting for proper utility class output. We no longer use a dedicated media query sorter in our dependencies, and do all our optimization with csso (deprecating cssnano). https://github.com/uswds/uswds/pull/3308

Improved performance. We’ve improved the time it takes to compile the design system and its overall file size:

version build:sass gulp sass unminified minified
2.4.0 14s 6.5s 359 KB 270 KB
2.5.0 7.5s 5.2s 357 KB 259 KB

Allows USWDS notifications to render in all environments. We removed the multiline strings that were causing our notification to cause build failures in environments like webpack. Now the Sass should compile properly in all environments. https://github.com/uswds/uswds/pull/3290

Update to the most recent version of Public Sans. Updated to Public Sans 1.008 for better readability and display. https://github.com/uswds/uswds/pull/3275

Added missing add-aspect() mixin. This adds the mixin equivalent to the add-aspect utility classes. https://github.com/uswds/uswds/pull/3283

Improved error messaging for the lh() function. Now it lets you know why it failed and how to fix the error. https://github.com/uswds/uswds/pull/3284

Disabled JS in our Fractal library to remediate an out-of-date jQuery vulnerability. https://github.com/uswds/uswds/pull/3274

Package updates:

package old new
@types/node 12.12.20 13.5.0
axe-core 2.6.1 3.4.1
cssnano   deprecated
css-mqpacker   deprecated
gulp-spawn-mocha 5.0.1 6.0.0
jsdom 9.0.0 16.0.1
jsdom-global 2.1.0 3.0.2
mocha 5.2.0 7.0.1
nyc 14.1.1 15.0.0
postcss-csso 4.0.0
sass 1.25.0

7 vulnerabilities (5 low, 2 high) in 29833 scanned packages All but one low vulnerability are related to Fractal.

Version 2.4.0

December 18, 2019

What’s new in USWDS 2.4.0

Allow non-token values in theme color settings. While USWDS promotes and encourages using our system tokens in theme color settings, agencies have a real need to occasionally use non-token colors. This includes instances where certain colors are mandated by law and cannot be easily changed. Now, teams can add non-token colors to theme color settings like $theme-color-primary: #f00. This new non-token value of 'primary' will apply anywhere the 'primary' token is used: functions, mixins, settings, and utilities. Using non-token values will throw a warning in the compile process, but this, like all compile warnings, can be disabled by setting $theme-show-compile-warnings: false. (https://github.com/uswds/uswds/pull/3258)

Handle deprecations more gracefully. Occasionally the design system will deprecate variables or functionality. Now we’ll display a deprecation message in the terminal when compiling USWDS Sass to better communicate these changes. (This notification can be disabled in settings.) We’re also improving backward compatibility by supporting deprecated variables, functions, and mixins throughout the major version cycle. This way, we can continue to improve how our code is structured while minimizing the effects of this restructuring on your projects. (https://github.com/uswds/uswds/pull/3261)

This is how the deprecation warning prints in the terminal:

✉ USWDS Notifications
2.4.0: If your component settings aren't working as expected, make
sure you're importing the components settings in your Sass entry
point (often styles.scss) with `@import "uswds-theme-components"`.
A bug in 2.0 omitted that import.
2.2.0: We changed the names of some settings.
$theme-navigation-width → $theme-header-min-width
$theme-megamenu-logo-text-width → $theme-header-logo-text-width
2.0.2: We changed the names of some settings and mixins.
$theme-title-font-size → $theme-display-font-size
@include title → @include display
@include typeset-title → @include typeset-display
These are notifications from the USWDS team, not necessarily a
problem with your code.

Disable notifications using $theme-show-notifications: false

Now components reliably respect their font settings. Setting values like $theme-footer-font-family should set the font face for the entire component, but some CSS specificity quirks were overriding these values in some instances. Now, setting a component’s font face works as expected, with no secret overrides. (https://github.com/uswds/uswds/pull/3253)



npm audit: found 7 vulnerabilities (5 low, 2 high) in 30585 scanned packages Both High vulnerabilities are related to Fractal and lodash

Version 1.6.13

November 26, 2019

Starting point

npm audit: 965 vulnerabilities (96 low, 236 moderate, 623 high, 10 critical)

What we did


npm audit: 4 moderate severity vulnerabilities

All current moderate vulnerabilities related to jsdom > hoek

Version 1.6.12

November 25, 2019

Version 1.6.11

November 25, 2019

Version 2.3.1

November 21, 2019

What’s new in USWDS 2.3.1

Now the success icon looks like a checkmark and not a warning. This fixes a bug introduced in 2.2.0 related to SVG normalization. (#3230) Thanks @nickscialli-usds

Version 2.3.0

November 20, 2019

What’s new in USWDS 2.3.0

Properly include component theme variables: Now we’re properly including the component theme variables from _uswds-theme-components.scss in theme/styles.scss so anyone who uses that file in their Sass compile process (like users of uswds-gulp) will see component theme settings applied as expected.

These should be the proper theme imports for USWDS projects:

@import 'uswds-theme-general';
@import 'uswds-theme-typography';
@import 'uswds-theme-components'; <-- previously missing
@import 'uswds-theme-spacing';
@import 'uswds-theme-color';
@import 'uswds-theme-utilities';

Issue: https://github.com/uswds/uswds/issues/3117

Hero image theme setting default is now backward compatible: The $theme-hero-image theme variable now has a default equivalent to its effective value pre v2.2.0 so users that had a working version of their hero are more likely to see no issues upgrading to the latest version of USWDS.

Old default:

$theme-hero-image: '..img/hero.png'

Markup changes

⚠️ We made a small change to the footer markup. This change fixes some small footer spacing issues — not adding this new markup will not negatively affect your existing footer, but adding it will make it better. See the diff: https://github.com/uswds/uswds/pull/3214/files

Smaller issues


Removes the following dependencies:

Updates the following dependencies:

Adds the following dependencies:

Other improvements

npm audit results

15 low, 2 moderate, 6 high, 2 critical

All but one Low vulnerability are related to Fractal.

Version 2.2.1

September 23, 2019

What’s new in USWDS 2.2.1

Sass compiles properly: Now importing uswds using @import uswds will compile properly. The packages/uswds-components package newly referenced by uswds.scss was using incorrect paths and now they point to the proper locations.

Why did this happen? A quirk of how Sass evaluates paths prevented us from seeing this error before we published the release. Sass will, apparently, accept paths relative both to the the file containing the import and also to the entry point (ie, the primary file the compiler points to). The incorrect /base paths evaluated properly for us internally since uswds.scss is the entry point from which we compile our Sass (that is, we do not @import uswds from a separate file). By chance, /base is valid relative to this internal entry point.

How are we preventing this in the future? We’ve made the build process more strict in uswds-site (https://github.com/uswds/uswds-site/pull/816/commits/103dd3ff0569f3a6c61cfd254df031dfdb5c5045#diff-d0940386a71c685fc307161a767958b4R54) so it’ll be far less likely that such a bug will make it through our testing. We may also change our internal build process to surface errors such as this one.

Version 2.2.0

September 19, 2019

What’s new in USWDS 2.2.0

Extended megamenu now works: This fixes a CSS specificity error introduced in 2.1.0 affecting the extended header’s megamenu. (https://github.com/uswds/uswds/pull/3100)

Primary nav indicators are properly aligned: This fixes a spacing issue affecting the header nav indicator bars present since 2.0 that seems to have been a result of rounding errors in line-height calculation. (https://github.com/uswds/uswds/pull/3100)

All component font functions now use role-based tokens: Now code will generate properly, even if a user decides not to use a certain font type in their project (like serif). (https://github.com/uswds/uswds/pull/3103)

Example: a project uses only a sans-serif font on their site, all other font types are set to false.

Improved ARIA markup: We no longer add manual ARIA roles to semantic elements with implicit roles (like header, nav and footer), as this is redundant in modern HTML 5. However, we now add unique and sensical identification to both our primary and secondary navigation with aria-label. (https://github.com/uswds/uswds/pull/3104)

Reference: https://www.w3.org/WAI/tutorials/page-structure/regions/#navigation

Consistent sizing for SVG assets: Now our SVG image assets are sized and built consistently, so CSS styling affects each image as expected. Previously, inconsistent sizing and viewBox settings could cause unexpected effects or necessitate compensatory styling. (https://github.com/uswds/uswds/pull/3105)

Now, each SVG asset is set in a 64px max bounding box flush to the edge of the image — that is, the image is exactly 64px in the maximum dimension, with no space around the perimeter. This allows us to more accurately control the output with CSS. The image is minimally opinionated.

This PR affects:

⚠️ This change has the potential to affect any custom components built with existing SVG assets.

Header and banner width now controlled in settings: Now there are explicit settings for controlling the max-width of the gov banner and the header. (https://github.com/uswds/uswds/pull/3106)

:warning: This change affects the markup of the megamenu. :warning: This change affects settings. Replace instances of the deprecated setting with the new one.

old variable 2.2.0+
$theme-navigation-width $theme-header-min-width
$theme-megamenu-logo-text-width $theme-header-logo-text-width

Your settings file will require the new settings below:

file setting variable controls default
components $theme-banner-max-width maximum width of the banner desktop
components $theme-header-max-width maximum width of the header desktop
components $theme-header-min-width breakpoint at which full header shows desktop
components $theme-header-logo-text-width width of the logo/title region of the header (replaces $theme-megamenu-logo-text-width 33%
components $theme-megamenu-columns number of columns in the megamenu 3

Settings can control hero image: Now you can change the hero image in settings! (https://github.com/uswds/uswds/pull/3107)

:warning: This change affects settings. Your settings file will require the new settings below:

file setting variable controls default
components $theme-hero image path to the hero image, relative to the compiled stylesheet '../img/hero.png'

Improve package documentation and usage: This improves the package documentation in the theme styles.scss by including all available packages in the comments. It also modifies the package contents of uswds-components to require the required and global packages — to be consistent with other packages. (https://github.com/uswds/uswds/pull/3108)

:warning: If you use the uswds-components package, you will no need to include the required and global packages before including uswds-components.

Version 2.1.0

August 14, 2019

Made it simpler to subset the design system and include only the components your project needs with USWDS packages.

package .css .min .zip
default USWDS 359 271 40 KB
form-controls 18 15 3
form-templates 60 47 6
typography 17 15 3
validation 32 28 5
usa-accordion 13 12 2
usa-alert 13 12 2
usa-banner 50 38 5
usa-button 19 16 3
usa-checklist 11 9 2
usa-footer 59 46 6
usa-header 113 63 9
usa-hero 48 37 5
usa-media-block 10 9 2
usa-search 29 25 4
usa-sidenav 12 10 2
usa-skipnav 10 9 2
usa-table 11 9 2
usa-tag 10 9 2
usa-header + usa-footer 162 72 10
usa-banner + usa-footer 99 55 7

Reorganized the source code (in the stylesheets directory) to better reflect its relationship to the build process:

Version 2.0.3

June 07, 2019

Version 2.0.2

May 08, 2019



Version 2.0.1

April 05, 2019


Version 2.0.0

April 04, 2019

USWDS 2.0 is a new foundation for the future of our design system. This new version was designed to make it easier for any project to integrate USWDS and use it to support both your mission and the needs of your audience. It introduces a powerful toolkit of new features to help make creating useful, consistent digital services faster, simpler, and more fun.

New and notable features:

:rocket: More about USWDS 2.0

Changes from Beta 7 to 2.0

Version 1.6.10

March 25, 2019

Version 2.0.0 Beta 7 (Release candidate)

March 25, 2019

Bug fixes


old new
.usa-button-unstyled .usa-button.usa-button--unstyled
.usa-unstyled-list .usa-list.usa-list--unstyled
.usa-linput-list removed
ul and li for checkbox just div.usa-checkbox
.usa-checkbox-input .usa-checkbox__input
.usa-checkbox-label .usa-checkbox__label
ul and li for radio buttons just div.usa-radio
.usa-radio-input .usa-radio__input
.usa-radio-label .usa-radio__label
.media_link .usa-media-link
.usa-font-lead .usa-intro
.usa-form-hint .usa-hint
.usa-label-helper .usa-hint
.usa-input-error-message .usa-error-message
.usa-mobile-nav-active .usa-js-mobile-nav--active
token old value new value migration old → new
1 40ch 44ex 11
2 60ch 60ex 24
3 66ch 64ex 35
4 72ch 68ex 45
5 77ch 72ex 56
6 88ex

Public Sans

Internal / CI

Version 2.0.0 Beta 6

March 11, 2019

This release features some significant breaking changes, but it should be the last release of major code changes before the final release of USWDS 2.0.

Bug Fixes



We’re now adding the USWDS version number to our settings files to better communicate which version of settings files your project uses. (Thanks @jeremyzilar!)

The layout grid now has its own switch for using !important (general > $theme-layout-grid-uses-important) instead of being connected to the $theme-utilities-use-important variable.

We’re now flipping the caret in dropdown menus when the menu is open to consistently indicate that it is closable (#2616)


We’ve added two new font-types to typography settings: lang and icon for icon fonts and language-specific fonts (#2683)

There’s now support for adding custom font stacks and custom font source files in the typography settings file. (#2858)

Adding custom typefaces is now a bit simpler and actually works. (#2858)

We’ve improved the font rendering speed by adding font-display: fallback to our @font-face declarations (#2744)

Global styling options and prose scope are simpler and more streamlined. (#2814)

There’s better, more clear documentation in the typography settings

previous setting Beta 6 equivalent
$theme-content-styles: 'scoped' no explicit setting necessary
$theme-content-styles: 'global' $theme-global-content-styles: true
$theme-content-styles: 'none' $theme-global-paragraph-styles: false
  $theme-global-link-styles: false
  $theme-global-content-styles: false
$theme-global-styles-basic: true $theme-global-paragraph-styles: true
  $theme-global-link-styles: true

Breaking typography changes

old settings new settings
$theme-font-path in settings-general $theme-font-path in settings-typography
$theme-font-definitions $theme-typeface-tokens
$theme-font-definitions.[token].name $theme-typeface-tokens.[token].display-name
removed generate, system-font, and variable-font keys from typeface token maps
moved custom font source and directory data to $theme-font-[type]-custom-src
moved custom font stack data to $theme-font-[type]-custom-stack
$theme-font-[type] $theme-font-type-[type]
$theme-font-[role] $theme-font-role-[role]
$theme-font-[role] accepts $theme-font-[type] variables $theme-font-[role] accepts font-type tokens like 'mono', 'sans', and 'serif'
$theme-output-all-weights $theme-generate-all-weights
no longer import core/font-definitions — this file is deprecated
$theme-global-styles-basic $theme-global-paragraph-styles, $theme-global-link-styles, and $theme-global-content-styles
basic styles set to true by default basic styles (paragraph and link styles) set to false by default

Class names

We’ve decided to use BEM naming for our class naming for disambiguation and consistency with industry norms. This is a major change that affects a majority of USWDS classes.


Beta 5 Beta 6
usa-background-dark usa-dark-background
usa-content usa-content
usa-content-list usa-content-list
usa-display usa-display
usa-external_link usa-link--external
usa-external_link-alt usa-link--external.usa-link--alt
usa-font-lead usa-font-lead
usa-heading-alt usa-heading-alt
usa-link usa-link
usa-paragraph usa-paragraph
usa-prose usa-prose


Beta 5 Beta 6
usa-button usa-button
usa-button-accent-cool usa-button--accent-cool
usa-button-active usa-button--active
usa-button-base usa-button--base
usa-button-big usa-button--big
usa-button-disabled usa-button--disabled
usa-button-hover usa-button--hover
usa-button-outline usa-button--outline
usa-button-outline usa-button--outline
usa-button-outline-inverse usa-button--outline.usa-button--inverse
usa-button-secondary usa-button--secondary
usa-button-unstyled usa-button-unstyled
usa-focus usa-focus


Beta 5 Beta 6
usa-embed-container usa-embed-container


Beta 5 Beta 6
usa-media_link usa-media-link


Beta 5 Beta 6
usa-checkbox-input usa-checkbox__input
usa-checkbox-label usa-checkbox__label
usa-fieldset usa-fieldset
usa-form-group usa-form-group
usa-form-group-day usa-form-group--day
usa-form-group-error usa-form-group--error
usa-form-group-month usa-form-group--month
usa-form-group-year usa-form-group--year
usa-form-hint usa-form__hint
usa-input usa-input
usa-input-inline usa-input--inline
usa-input-medium usa-input--medium
usa-input-small usa-input--small
usa-input-success usa-input--success
usa-input-error usa-input--error
usa-input-error-message usa-input-error-message
usa-input-label-helper usa-input__label-helper
usa-input-label-required usa-input__label-required
usa-input-list usa-input-list
usa-label usa-label
usa-label-error usa-label--error
usa-legend usa-legend
usa-memorable-date usa-memorable-date
usa-radio-input usa-radio__input
usa-radio-label usa-radio__label
usa-range usa-range
usa-select usa-select
usa-textarea usa-textarea


Beta 5 Beta 6
usa-list usa-list
usa-unstyled-list usa-unstyled-list


Beta 5 Beta 6
usa-table usa-table
usa-table-borderless usa-table--borderless


Beta 5 Beta 6
usa-tag usa-tag
usa-tag-big usa-tag--big


Beta 5 Beta 6
usa-accordion usa-accordion
usa-accordion-bordered usa-accordion--bordered
usa-accordion-button usa-accordion__button
usa-accordion-content usa-accordion__content
usa-accordion-heading usa-accordion__heading


Beta 5 Beta 6
usa-alert usa-alert
usa-alert-error usa-alert--error
usa-alert-no-icon usa-alert--no-icon
usa-alert-slim usa-alert--slim
usa-alert-success usa-alert--success
usa-alert-warning usa-alert--warning
usa-alert-body usa-alert__body
usa-alert-heading usa-alert__heading
usa-alert-icon usa-alert__icon
usa-alert-info usa-alert__info
usa-alert-paragraph usa-alert__paragraph
usa-alert-text usa-alert__text


Beta 5 Beta 6
banner-header-expanded usa-banner__header--expanded
usa-banner usa-banner
usa-banner-button usa-banner__button
usa-banner-button-text usa-banner__button-text
usa-banner-content usa-banner__content
usa-banner-guidance usa-banner__guidance
usa-banner-header usa-banner__header
usa-banner-header-action usa-banner__header-action
usa-banner-header-close-text usa-banner__header-close-text
usa-banner-header-expanded usa-banner__header-expanded
usa-banner-header-flag usa-banner__header-flag
usa-banner-header-text usa-banner__header-text
usa-banner-icon usa-banner__icon
usa-banner-inner usa-banner__inner


Beta 5 Beta 6
is-checked is-checked
usa-checklist usa-checklist
usa-checklist-checked usa-checklist__checked
usa-checklist-item usa-checklist__item
Beta 5 Beta 6
usa-footer usa-footer
usa-footer-big usa-footer--big
usa-footer-slim usa-footer--slim
usa-footer-address usa-footer__address
usa-footer-collapsible usa-footer__primary-content--collapsible
usa-footer-contact-heading usa-footer__contact-heading
usa-footer-contact-links usa-footer__contact-links
usa-footer-contact-info usa-footer__contact-info
usa-footer-logo usa-footer__logo
usa-footer-logo-heading usa-footer__logo-heading
usa-footer-logo-img usa-footer__logo-img
usa-footer-nav usa-footer__nav
usa-footer-primary-content usa-footer__primary-content
usa-footer-primary-link usa-footer__primary-link
usa-footer-primary-section usa-footer__primary-section
usa-footer-return-to-top usa-footer__return-to-top
usa-footer-secondary-link usa-footer__secondary-link
usa-footer-secondary-section usa-footer__secondary-section
usa-footer-social-links usa-footer__social-links
usa-social-link usa-social-link
usa-social-link-facebook usa-social-link--facebook
usa-social-link-rss usa-social-link--rss
usa-social-link-twitter usa-social-link--twitter
usa-social-link-youtube usa-social-link--youtube
usa-sign_up-block usa-sign-up
usa-sign_up-header usa-sign-up__heading


Beta 5 Beta 6
usa-form usa-form
usa-form-large usa-form--large
usa-input-medium usa-input--medium
usa-input-small usa-input--small
usa-form-note usa-form__note

graphic list

Beta 5 Beta 6
usa-graphic-list usa-graphic-list
usa-graphic-list-heading usa-graphic-list__heading
usa-graphic-list-row usa-graphic-list__row


Beta 5 Beta 6
usa-current usa-current
usa-header usa-header
usa-header-basic usa-header--basic
usa-header-megamenu usa-header--megamenu
usa-header-extended usa-header--extended
usa-header-extended-megamenu usa-header-extended-megamenu
usa-logo usa-logo
usa-logo-text usa-logo__text
usa-megamenu usa-megamenu
usa-menu-btn usa-menu-btn
usa-nav usa-nav
usa-nav-container usa-nav__container
usa-nav-inner usa-nav__inner
usa-nav-link usa-nav__link
usa-nav-primary usa-nav__primary
usa-nav-submenu usa-nav__submenu
usa-navbar usa-navbar
usa-overlay usa-overlay
usa-search usa-search


Beta 5 Beta 6
usa-hero usa-hero
usa-hero-callout usa-hero__callout
usa-hero-callout-alt usa-hero__callout-alt
usa-hero-heading usa-hero__heading


Beta 5 Beta 6
usa-layout-docs-main usa-layout__docs-main
usa-layout-docs-sidenav usa-layout__docs-sidenav

media block

Beta 5 Beta 6
usa-media_block-body usa-media-block__body
usa-media_block-img usa-media-block__img


Beta 5 Beta 6
usa-accordion-button usa-accordion__button
usa-megamenu usa-megamenu
usa-mobile-nav-active usa-mobile-nav--active
usa-nav usa-nav
usa-nav-close usa-nav__close
usa-nav-container usa-nav__container
usa-nav-primary usa-nav__primary
usa-nav-primary-item usa-nav__primary-item
usa-nav-secondary usa-nav__secondary
usa-nav-secondary-item usa-nav__secondary-item
usa-nav-secondary-links usa-nav__secondary-links
usa-nav-submenu usa-nav__submenu
usa-nav-submenu-item usa-nav__submenu-item
usa-nav-submenu-list usa-nav__submenu-list
usa-nav-submenu-list-item usa-nav__submenu-list-item
usa-navbar usa-navbar
usa-search usa-search
Beta 5 Beta 6
usa-search usa-search
usa-search-big usa-search--big
usa-search-small usa-search--small
usa-search-input usa-search__input
usa-search-submit usa-search__submit
usa-search-submit-text usa-search__submit-text


Beta 5 Beta 6
usa-section usa-section
usa-section-dark usa-section--dark
usa-section-light usa-section--light


Beta 5 Beta 6
usa-sidenav usa-sidenav
usa-sidenav-sublist usa-sidenav__sublist


Beta 5 Beta 6
usa-skipnav usa-skipnav

Version 2.0.0 Beta 5

February 20, 2019

Bug fixes


More up-to-date node dependency (https://github.com/uswds/uswds/pull/2900) We updated the required node version to the current LTS version of node (10.15.1) and updated our dependencies to build properly in this environment.

Now we’re exposing some internal component variables to user-accessible settings (https://github.com/uswds/uswds/pull/2901) Here’s what we added:

// Accordion
$theme-accordion-border-width:        0.5;
$theme-accordion-border-color:        'base-lightest';

// Alert
$theme-alert-bar-width:               1;
$theme-alert-icon-size:               4;
$theme-alert-padding-x:               2.5;

// Banner
$theme-button-stroke-width:           2px;

// Footer
$theme-input-select-border-width:     2px;
$theme-input-select-size:             2.5;
$theme-input-state-border-width:      0.5;

We expanded and improved our system color families and theme defaults These new colors are a bit more harmonious, and have a better 1.x-to-2.0 conversion.

Here’s what changed:

base changes

$theme-color-base-family:           'gray-cool';
$theme-color-base-lightest:         'gray-5';
$theme-color-base-lighter:          'gray-cool-10';
$theme-color-base-light:            'gray-cool-30';
$theme-color-base:                  'gray-cool-50';
$theme-color-base-dark:             'gray-cool-60';
$theme-color-base-darker:           'gray-cool-70';
$theme-color-base-darkest:          'gray-90';
$theme-color-base-ink:              'gray-90';

primary changes

$theme-color-primary-lighter:       '#{$theme-color-primary-family}-10';
$theme-color-primary-vivid:         'blue-warm-60v';

accent-warm changes

$theme-color-accent-warm-family:    'orange';
$theme-color-accent-warm-lighter:   '#{$theme-color-accent-warm-family}-10';
$theme-color-accent-warm-light:     '#{$theme-color-accent-warm-family}-20v';
$theme-color-accent-warm:           '#{$theme-color-accent-warm-family}-30v';
$theme-color-accent-warm-darker:    '#{$theme-color-accent-warm-family}-60';

error changes

$theme-color-error-family:     'red-warm';
$theme-color-error-light:      '#{$theme-color-error-family}-30v';
$theme-color-error:            '#{$theme-color-error-family}-50v';
$theme-color-error-dark:       'red-60v';
$theme-color-error-darker:     'red-70';

warning changes

$theme-color-warning-lighter:  'yellow-5';
$theme-color-warning-light:    'yellow-10v';
$theme-color-warning-darker:   '#{$theme-color-warning-family}-50v';

success changes

$theme-color-success-light:    '#{$theme-color-success-family}-20v';
$theme-color-success-darker:   '#{$theme-color-success-family}-60';

info changes

$theme-color-info-darker:      'blue-cool-60';

USWDS 1.x to 20 color conversion

uswds conversion table

Current USWDS theme defaults


Current USWDS state defaults


Version 2.0.0 Beta 4

November 14, 2018

Note: Items with a ⚠️ icon are potentially breaking changes


Bug fixes


This is a big one with lots of potentially breaking changes. See the pull request and the v2 documentation for a more complete record of the changes and the final palette names.

⚠️ If you’ve experimented with using palettes for your utility classes, you will need to update to the new names or you will get Palette not found in the registry errors when you compile.

The .usa-prose component allows developers to style unclassed elements within a scoped container. However, this could result in unpredictable behavior (like style specificity errors) if other components are inside in a usa-prose container. Now, usa-prose only affects direct children (using the > selector). See the pull request for more details and context.

⚠️ Make sure any content you want styled with usa-prose is a direct child of usa-prose — this could mean adding usa-prose to grid-col or section elements previously styled simply by being inside usa-prose.


Version 2.0.0 Beta 3

October 29, 2018

Bug Fixes



Version 1.6.9

October 15, 2018