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:

• Namespacing: It’s more compatible with other Sass frameworks. SaMS offers optional custom namespace for any USWDS variables, mixins, and functions, assuring that there are never any collisions between similarly named functionality across libraries (like two functions called color()).
• Subsetting: It loads only what you need. SaMS makes it simpler to subset the design system to include only the components you need, with no redundant imports and minimal unused rules.

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.

Requirements

This currently requires a compile path that uses Dart Sass.

• Example: Use Gulp with gulp-sass and sass, and sass.compiler = require('sass'); set in the gulpfile.
• Example: Use uswds-gulp

⚠️ 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.

Implementation

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:

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

• Add the beta package to your project with the simple implementation and see if it compiles as expected
• Try some of the intermediate implementations: subsetting or namespacing
• File any questions of bugs in the uswds repo
  • Use the beta label
  • Be as descriptive as possible about how to reproduce a bug
  • Attach any setup information (beta version, compiler, framework, os, etc)
• Ask questions in the #uswds-public Slack

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:

• Identifier: The identifier communicates a site’s parent agency and displays agency links required by federal laws and policies.
• Step indicator: A step indicator updates users on their progress through a multi-step process.
• Time picker: A time picker helps users select a specific time.

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)

• flex-align-self-start: align element at the start of the parent’s cross axis
• flex-align-self-middle: align element in the middle of the parent’s cross axis
• flex-align-self-end: align element at the end of the parent’s cross axis
• flex-align-self-stretch: stretch across the full extent of the parent’s cross axis

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

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:

• Breadcrumb: Breadcrumbs provide secondary navigation to help users understand where they are in a website.
• Date picker: A date picker helps users select a single date.
• Date range picker: A date range picker helps users select a range between two dates.
• File input: File input allows users to attach one or multiple files.
• Tooltip: A tooltip is a short descriptive message that appears when a user hovers or focuses on an element.

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:

• Emphasize that trustworthiness is a combination of an official TLD and a secure HTTPS connection
• Stay up to date with the different ways to determine HTTPS usage in your browser
• Provide official language support for other languages, starting with Spanish (with the help of the USAGov en Español team)
• Focus the message by using TLD-specific copy for .mil sites

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

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

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( 
  background-color, 
  preferred-text-color, 
  fallback-text-color, 
  WCAG-level
)

@include set-text-and-bg( 
  background-color, 
  preferred-text-color, 
  fallback-text-color, 
  WCAG-level
)

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

WCAG-levels:
  "AA"
  "AA-large"
  "AAA"

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

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

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:

• Button group: Use button groups to collect similar or related actions.
• Card: Cards contain content and actions about a single subject.
• Character count: Character count helps users know how much text they can enter when there is a limit on the number of characters.
• Combo box: A combo box helps users select an item from a large list of options.

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

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

  Note: The devDependencies number is high because we’re still having issues with npm audit fix.

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

Vivid color wheel 2.6.0

Dependencies and security

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

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

  Note: The devDependencies number seems high. We’ve had some issues with npm audit recently

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:

• banner: is now a <section> instead of a <div> with the ARIA label Official government website
• footer: nav includes the ARIA label of Footer navigation
• graphic-list: uses h2 as a heading default instead of h3
• hero: includes the ARIA label of Introduction
• search: the search form is given the ARIA role of search
• documentation template: includes only the main content in the <main> element. The nav is no longer treated as an <aside>

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:

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:

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)

Bugfixes

• Added a border-collapse: collapse rule to our tables to to fix a bug introduced when we upgraded our version of Normalize. Thanks for the heads up @maya! (https://github.com/uswds/uswds/pull/3250)
• Removed a duplicate layout grid import (https://github.com/uswds/uswds/pull/3252)
• Fixed the focus outline’s offset, which was being overridden by a specificity bug (https://github.com/uswds/uswds/pull/3259)

Audit

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

• Removed Fractal, since we are no longer making changes to component code
• Removed unused regression tests
• Added precompiled component previews and renders to a committed directory for testing
• Using v1-master and v1-develop as v1 production branches

Result

npm audit: 4 moderate severity vulnerabilities

All current moderate vulnerabilities related to jsdom > hoek

Version 1.6.12

November 25, 2019

• Fix Snyk tests on Circle
• Fix cache bug on Circle

Version 1.6.11

November 25, 2019

• Changed Circle cache settings

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.

• Although the new default includes a variable reference to $theme-image-path, users can change this to any path needed. It need not refer to $theme-image-path.
• This new default requires that the component theme variables (uswds-theme-components) be imported after uswds-theme-general. We suggest that uswds-theme-components be the last of the theme variables imported.

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

• Megamenu sections now appear at the proper width in the mobile menu: Fixes a megamenu column-width bug that made some subsection menu items appear at less than the full column width.
• Contact Info underline scope applies to each item individually: This fixes an issue where the :hover selector was too broad. This attaches it to the a link instead of the parent div.
• Contact info spaced properly in slim footer: Fixes a grid-gap error to assure that contact info items have space in-between.
• Contact info displays properly regardless of whether utilities use important: Fixes an issue where the contact info wouldn’t display properly unless project utilities were set to use important.
• Open/close carets in the mobile big footer are now the proper size.
• Improved footer link spacing @desktop width.
• Updated and clarified all the font licenses.
• Added Public Sans v1.007
• Use Prettier formatting for files.
• Completely install USWDS when building on Federalist.
• Update our security test with Snyk.

Dependencies

Removes the following dependencies:

• @frctl/mandelbrot
• array-filter
• acorn
• canvas-prebuilt
• chalk
• cracks
• jquery

Updates the following dependencies:

• @types/node → 12.12.9
• del → 5.1.0
• @babel/preset-env → 7.7.1
• @frctl/fractal → 1.2.1.beta-1 (to fix a 404-related bug)
• ansi-colors → 4.1.1
• autoprefixer → 9.7.1
• gulp-filter → 6.0.0
• gulp-stylelint → 10.0.0
• handlebars → 4.5.3
• node-notifier → 6.0.0
• node-sass → 4.13.0
• normalize.css → 8.0.1
• resemble.js → 3.2.3
• sinon → 7.5.0
• stylelint → 11.1.1
• stylelint-scss → 3.12.1

Adds the following dependencies:

• eslint-config-prettier
• prettier
• stylelint-config-prettier
• stylelint-config-recommended-scss
• stylelint-prettier

Other improvements

• Update node version to latest LTS (12.13.0) and document
• Update sinon usage to use most current API

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:

• all SVG assets
• some components that use SVG assets
  • alerts
  • search
  • checkboxes
  • checklist

⚠️ 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.

Your settings file will require the new settings below:

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:

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.

• Thanks @turnerhayes for getting the ball rolling here, even if the final product might not be what you envisioned!
• Created custom packages in stylesheets/packages used to import only code related to the component package (ie @import uswds-banner)
• Analyzed each USWDS component’s stylesheet dependencies
• Left existing default build process alone (ie @import uswds)
• Allows users to dramatically reduce the USWDS code footprint

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

• Split subcomponents into separate files
• Move global stylesheets into their own folder
• Move all code-emitting source out of required dependencies

Version 2.0.3

June 07, 2019

• Fixed a bug that prevented in-page anchor links from linking properly from the main nav (https://github.com/uswds/uswds/pull/3059)
• Updated to Public Sans 1.005

Version 2.0.2

May 08, 2019

Fixed

• Fixed a bug where footer sections were closing on iOS when a user scrolled up and down. Thanks @joncasey! (https://github.com/uswds/uswds/pull/3047)
• Fixed a bug where uswds.css was outputting minified (https://github.com/uswds/uswds/pull/3050)

Updated

• Now using primary-dark for our default link hover instead of primary-darker (https://github.com/uswds/uswds/pull/3023)
• Improved the reliability of our Snyk integration (https://github.com/uswds/uswds/pull/3028)
• Changed the title typography mixin to display to make it more clear that it’s meant for the largest type on the page, not necessarily for the title or h1 (https://github.com/uswds/uswds/pull/3034)
• Changed the max date to 2019 for the date input (https://github.com/uswds/uswds/pull/3039)
• Linted all development Javascript against Airbnb eslint
• Updated to Public Sans v1.003

Version 2.0.1

April 05, 2019

Fixed

• Remove png from external link mixin and checkmark input print style

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:

• Easier incremental adoption
• Practical design tokens, functions, and mixins
• Accessible color system
• Expressive theming
• Powerful utility classes
• Simplified 12-column layout grid
• Introducing the Public Sans typeface
• A stable foundation that’s built to grow

:rocket: More about USWDS 2.0

• USWDS 2.0 website and documentation
• USWDS 2.0 for developers
• USWDS 2.0 for designers
• Migration guide

Changes from Beta 7 to 2.0

• Removed unneeded PNG fallbacks for images since we no longer support the bowsers that require them. (https://github.com/uswds/uswds/pull/3007)
• Updated our icon colors to USWDS 2.0 tokens (https://github.com/uswds/uswds/pull/3007)
• Now you can use token values of .5 and -.5 — without leading zeros — in functions and mixins. Thanks @dmethvin-gov! (https://github.com/uswds/uswds/pull/3009)
• The u-outline() mixin now properly accepts all the tokens it’s meant to accept. Thanks @jeremyzilar! (https://github.com/uswds/uswds/pull/3012)
• Added u-overflow-x() and u-overflow-y() mixins to match utilities. Thanks @jeremyzilar! (https://github.com/uswds/uswds/pull/3012)
• The offset-none utilities now support responsive prefixes as intended. Thanks @robertromore! (https://github.com/uswds/uswds/pull/3014)

Version 1.6.10

March 25, 2019

• Radio buttons are now printable (https://github.com/uswds/uswds/pull/2857)
• We documented our supported Node and NPM versions in the README (https://github.com/uswds/uswds/pull/2969)
• Non-focusable elements no longer get a focus indicator in Windows 11. Thanks @ncksllvn! (https://github.com/uswds/uswds/pull/2983)

Version 2.0.0 Beta 7 (Release candidate)

March 25, 2019

Bug fixes

• Radio buttons are now printable (https://github.com/uswds/uswds/pull/2950)
• Slim alert has the correct (smaller) icon size alert (https://github.com/uswds/uswds/pull/2946)
• usa-alert--no-icon has proper padding (https://github.com/uswds/uswds/pull/2959)
• Font stacks now output properly. Thanks @stphnwlkr! (https://github.com/uswds/uswds/pull/2947)
• Non-focusable elements no longer get a focus indicator in Windows 11. Thanks @ncksllvn! (https://github.com/uswds/uswds/pull/2988)
• All type tokens (even lang, cond, and icon) output proper theme font size utilities. (https://github.com/uswds/uswds/pull/2980)

Improvements

• ⚠️ breaking change: gov banner markup now points to the flag in the img folder and not the favicon (https://github.com/uswds/uswds/pull/2985)
• ⚠️ breaking change: hero component now uses an h1 for its tagline for better accessibility (https://github.com/uswds/uswds/pull/2973)
• ⚠️ breaking change: Removed the alert paragraph component as its functionality is now better controlled with utilities. (https://github.com/uswds/uswds/pull/2990)
• ⚠️ breaking change: BEM implementation is clearer and more consistent:

• ⚠️ breaking change: Updated footer-big component to use new BEM (https://github.com/uswds/uswds/pull/2974)
• ⚠️ breaking change: Updated measure tokens to conform to guidance and be more reliable (https://github.com/uswds/uswds/issues/2960 and https://github.com/uswds/uswds/pull/2981)

• Tightened letterspacing of letterspacing 1 to conform to guidance for small text (https://github.com/uswds/uswds/pull/2965)
• Documented supported Node and NPM versions in the README (https://github.com/uswds/uswds/pull/2968)
• Update to most current versions of Source Sans Pro and Merriweather. Thanks @miguelsousa! (https://github.com/uswds/uswds/pull/2934)
• Updated the favicon to match our logo (https://github.com/uswds/uswds/pull/2985)
• Removed EOT and SVG font versions since we do not support IE8 or Safari older than 4.1. Thanks @miguelsousa! (https://github.com/uswds/uswds/pull/2989)

Public Sans

• Fixed a display error resulting in poor font rendering on Windows. Thanks @fat32 and @stphnwlkr! (https://github.com/uswds/public-sans/pull/27)
• Lightened the regular weight (https://github.com/uswds/public-sans/pull/27)
• Updated the license to restore the original author’s copyright and remove the reserved font name to conform to SIL OFL best practices. Thanks @davelab6! (https://github.com/uswds/public-sans/pull/27)
• Coming soon: a new url for specimen site (https://public-sans.digital.gov)

Internal / CI

• Updated to Gulp 4 (https://github.com/uswds/uswds/pull/2957)
• Addressed all outstanding Snyk vulnerabilities

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

• Added the missing u-order() utility mixin

Improvements

General

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)

Typography

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)

• Removed $theme-content-styles and its options (global, scoped, none)
• Now usa-prose always applies content styles to its direct children
• Replaced the $theme-global-styles-basic variable with three explicit global styling vars — each set to false by default.
  • $theme-global-paragraph-styles applies styling to p elements
  • $theme-global-link-styles applies styling to a elements
  • $theme-global-content-styles applies styling to p, a, h[1-6], ol, ul, and table elements
• Now USWDS will only apply global styling when the user enables it.

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

Breaking typography changes

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.

• Use BEM for class naming: .usa-block-name__element-name--modifier (#2915)
• Use single hyphens for all blocks and elements (.usa-media-block)

typography

button

embed

figure

inputs

list

table

tag

accordions

alerts

banner

checklist

footer

forms

graphic list

header

hero

layout

media block

navigation

search

section

sidenav

skipnav

Version 2.0.0 Beta 5

February 20, 2019

Bug fixes

• The borderless table variant now displays properly in prose scope (https://github.com/uswds/uswds/pull/2881)
• Grid columns now display properly when your project doesn’t explicitly include component styles (https://github.com/uswds/uswds/pull/2900)
• Extra large content no longer breaks fill and auto columns. (https://github.com/uswds/uswds/pull/2900)
• List items now have a maximum width, similar to their <p> counterparts. Additionally, when a list is the last child of a container, it now does have any bottom margin. Thanks @adunkman! (https://github.com/uswds/uswds/pull/2906)
• Media query styling now applies to print jobs, fixing a number of current issues with print output. (https://github.com/uswds/uswds/pull/2910)

Improvements

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.

• Added a blue-cool color family (https://github.com/uswds/uswds/pull/2902)
• Added a red-cool family (https://github.com/uswds/uswds/pull/2911)
• Saturated gold-20v (https://github.com/uswds/uswds/pull/2911)
• Desaturated blue-cool standard colors and added vivid variants (https://github.com/uswds/uswds/pull/2911)

• Made small hue consistency modifications to the following families (https://github.com/uswds/uswds/pull/2911):

  • blue-warm
  • blue
  • gold
  • gray-cool
  • green-cool
  • mint
  • orange
  • red-cool
  • red
  • yellow
• Updated the following theme palettes for better consistency with 1.x defaults (https://github.com/uswds/uswds/pull/2911)
  • base
  • primary
  • accent-cool
  • error
  • warning
  • success
  • info

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

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

Internal

• Welcome @greensteph to the USWDS Core team 🎉

Bug fixes

• Checkboxes now print correctly (link)
• The $theme-font-definitions variable for adding custom font definitions is no longer overridden by the system default. Thanks for the heads up @yomatters! (link)
• Added the missing u-text-indent() mixin. Thanks for the heads up @jeremyzilar! (link)
• Fixed errors when compiling with Dart Sass or Jekyll. Thanks to Matt Langan in the #uswds-public channel for surfacing this! (link)

Improvements

New mixins and improved mixin functionality (link)

• u-pin() mixin now uses the format u-pin-[side] instead of u-pin([side]) for simplicity

  Example: u-pin-y instead of u-pin('y') — though the latter will still work

• Removed u-list-reset() since there’s already add-list-reset() but also included list-reset() as a clone of add-list-reset() for backward compatibility

  ⚠️ Replace any instance of u-list-reset with add-list-reset

• Added u-radius-[modifier]() mixins.

  Example: u-pin-radius-left('pill')

Clearer more consistent palette names (link)

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.

• Palette naming is additive: each subset has the palette name of its parent, plus a subset suffix
• Default palettes use palette-[property]-default not palette-system-[property]
• Palettes with no suffix include all tokens in the category
• Palettes attempt to mimic the token categories/functions/properties: like units, color, and font
• Palettes attempt to mimic the token categories/functions/properties: like units, color, and font
• Palettes have a relative subset suffix (like -small, -smaller)
• Palettes that include all values in a set, have no special suffix (-all goes away)
• Any palette that had a -negative grouping now also has a corresponding -positive
• The -negative and -positive groups now appear before the sizing groups
• The font-weights category is now font-weight
• Numeric font-weights use the -system suffix, not -numeric

More predictable prose scope component (link)

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.

Improvements to Public Sans (link)

• Better, more readable numbers
• Narrower italic
• Thickened light and normal weights
• Better spacing of tabular figures

Documentation

• Now data tables are responsive, even at very narrow widths! Thanks for the technique @line47! (link)
• Lots of updated docs around utilities and palettes (link)
• Removed the utility output section since it was largely redundant with the utility examples and the style tokens sections (link)
• Added a banner to the main site that directs folks to the v2 Beta site. (link)
• Removed unsupported webp images
• Fixed a bunch of typos 🎉
• Fixed code block wrapping
• Fixed the navigation on the Developers page (link)
• Fixed some problems with svg rendering (link)

Version 2.0.0 Beta 3

October 29, 2018

Bug Fixes

• Repair u-border() mixin to accept valid units string tokens like '05' and '105' (https://github.com/uswds/uswds/pull/2860)
  • Thanks to the USWDS public Slack channel for surfacing this issue!

Improvements

• Added a few new token function clones to make them simpler to type. Note: All the previous functions continue to work as-is, this just adds some new functions that duplicate the functionality with a shorter name (https://github.com/uswds/uswds/pull/2861)
  • font-size() → size()
  • font-size() → fs()
  • font-family() → family()
  • font-family() → ff()
• Update to newest Public Sans (https://github.com/uswds/uswds/pull/2862)
  • A small update to Public Sans that tweaks the b and d characters, as well as the dot on the i character

Documentation

• Expanded the Style section and renamed it Style tokens to be explicit about its content
• Added the following section to Style Tokens
  • Overview
  • Color
    • Using color
    • Theme color tokens
    • State color tokens
    • System color tokens
  • Typesetting
    • Using type
    • Font family
    • Font size
    • Font weight
    • Letterspacing
    • Line height
    • Measure
  • Flex
  • Opacity
  • Order
  • Shadow
  • Spacing units
  • Z-index
• Updated the fonts and heading styles
• Updated the appearance of the docs sidebar to better display nested pages
• Added a new USWDS logo
• Added updated design principles

Version 1.6.9

October 15, 2018

Updated

• Addressed a potential vulnerability with mem@1.1.0 by updating to yargs@12.0.2 (https://github.com/uswds/uswds/commit/8aad13c9d4e88f549dd761f1b2d4b91c7921ecc4)

Fixed

• Improved the print styling of checkboxes to properly show checked boxes. (https://github.com/uswds/uswds/pull/2811) Thanks @David-Way