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 1.6.3

May 07, 2018

Fixed

• Update README documentation (#2462)
• Add version number to Fractal (#2463)
• Support node-sass npm importers (#2460)

Version 1.6.2

April 23, 2018

Fixed

• Remove unneeded list CSS (#2426)
• Remove submit button block display and unneeded extra styles (#2425)

Version 1.6.1

March 26, 2018

Fixed

• Ensure return to top link in the footer focuses back to the top on #main-content (#2403, #2321)
• Remove duplicate CSS from the grid (#2404, #2361)
• Use curly quote on government banner text (#2394)
• Fix bug that made footer list content disappear when the heading was clicked on desktop sizes (#2386, #2344)
• Allow footer menu items to be toggled close on click for the big footer on mobile (#2389, #1857)

Version 1.6.0

March 12, 2018

Changed

• Simplify Sass asset path variable overrides (#2365)

Fixed

• Change input optional text to HTML text instead of CSS content to improve accessibility (#2368)

Version 1.5.0

February 26, 2018

Added

• Add ability to have a basic alert with no icon (#2358)

Changed

• Use HTML5 <nav> element in the side navigation (#2359)
• Allow text to be used in close button (#2350)

Fixed

• Fix file input type styling by removing text border (#2364)
• Lower specificity of form Sass (#2357)
• Remove browser prefixes on appearance where possible (#2356)
• Trap focus to mobile navigation menu and other accessibility fixes (#2347)
• Change footer logo alt text to null (empty) (#2345)
• Add color to body tag to fix WCAG error (#2342)

Version 1.4.6

February 12, 2018

Removed

• Remove unused CSS from typography (#2312)
• Remove text color and decoration from usa-footer-return-to-top class to allow normal text styling to occur. (#2330)

Fixed

• Fix government banner display bug in IE 9-11 (#1984)

Version 1.4.5

January 23, 2018

Changed

• Optimize images to reduce file size without losing quality (#2308)
• Update links to repo to reflect the new GitHub organization and repo name (#2313)

Version 1.4.4

December 18, 2017

Fixed

• Add vertical space around sidenav at small widths in the documentation template (#1669)
• Update .usa-overlay transition to “overlay” to fix a flicker issue in the the uswds-jekyll template (#2274)
• Fix dropdown arrow display in Internet Explorer 9-11 (#2265)
• Make the focus variables default so they can be overridden (#2266)
• Update jQuery (used in tests) to the latest version and the packages associated with it (#2254)
• Fix unclosed search tag in header (#2236)

Version 1.4.3

November 20, 2017

Changed

• Balanced the vertical spacing between elements in the mobile primary and secondary navigation. (#2222, #2228)

Removed

• Remove unused class (.usa-form-control) from date input (#2225)

Fixed

• Allow for underlining in the footer links, except in custom scope (ie .usa-footer-primary-link, .usa-footer-secondary-link, and address) (#2219)
• Adds .usa-footer-secondary-link class to secondary links in the .usa-footer-big footer (#2219)
• Fixed extended header navigation overlap. This ensures that any element following the close button is cleared so there is no overlap. (#2222, #2228 )

Version 1.4.2

November 02, 2017

Changed

• Use character units (ch) for text max-width for improved performance with different fonts for paragraph text within usa-content (#1866)

Removed

• Remove unused polyfills from LICENSE (#2189)
• Remove unneeded pattern attribute from date input (#2200)

Fixed

• Fix hero component button display
• Fix select input text from overlapping with the icon
• Use pixel-fit icon for the select input dropdown for improved display
• Use correct font family for h6 headings
• Fix select arrow display bug after autofill in Chrome
• Fix duplicate border focus on select input in Firefox
• Fix disappearing focus state on links on hover
• Use caption on table for proper accessibility
• Make telephone number a tel link in the footer for more consistent functionality
• Fix spacing issue in multi-line footer links (#1637)
• Fix style consistency issue on optional and required form labels
• Update table styling with a tighter horizontal space, remove gray background on borderless table heading, and flush left first child on borderless table headings (#2192)
• Reduce CSS specificity in table and search components (#2062)

Version 1.4.1

October 06, 2017

Header Fixes

• The header style updates introduced in version 1.4 brought a series of bugs that affected mega menu variants of the basic and extended headers. This update reverts some of the changes so the mega menus function correctly.

Documentation Updates

• Updates to RELEASE.md to provide more clarity on the release process.

Fixed bug with headless Chrome tests

• Use the system’s hostname when REMOTE_CHROME_URL is also set and use localhost otherwise.

Version 1.4.0

September 29, 2017

Accessibility improvements

• The search button’s submit text is now visible to screen readers on all viewport sizes (#2065).
• A number of accessibility improvements have been made to the fractal site (#2057, #2064).

Visual changes

• Alerts now have a high-contrast left border to help differentiate them from each other and surrounding content (#2095).

  

• Buttons’ corners are more round to help them feel more button-y and to differentiate them from other elements, like labels (#2098). The spacing of the type inside the buttons is now balanced.

  

• The focus state has been updated to address concerns about contrast (#2112). Users told us the blue focus state on the common blue background color was hard to see. Our update does the following:

  1. Chooses a neutral gray that has higher contrast that works well on dark backgrounds and light (big caveat here: while there is no perfect focus state color for every site, one goal we had here is to help designers think critically about what focus state works best for the site they are designing).

  2. We offset the focus state a bit in order for the type to breathe a wee bit and help make it more noticeable, especially on objects that are flush the edge of a browser window.

  

• Dropdown menus have been updated (#2115). We changed the following:

  1. We changed the icon from a down-caret to a selector.

  2. The default state for a dropdown menu should indicate that the menu contains a list of options, rather than the first item on the list (see the example below for an illustration of this).

  

• A new usa-input-optional class has been added in favor of usa-input-required (#2116). The latter is now deprecated and will be removed in a future release of the Standards, due to evidence that labeling optional fields over required ones is a best practice. If you feel strongly about this issue, however, please contact the Standards team, as we may un-deprecate usa-input-required if a compelling argument exists. Update: while usa-input-optional is recommended over usa-input-required because it’s a best practice, we are keeping the usa-input-required in case anyone still needs it. For more details, see issue #2238.

• Checkboxes have been updated (#2117). Specifically:

  1. Spacing adjustments have been made for a cleaner look.
  2. The widget has slightly less rounded corners.
  3. The disabled state looks more disabled (note that accessibility contrast requirements do not apply to disabled elements).

  

• Labels have been updated (#2118). Specifically:

  1. They have less rounded corners to look less button-y.
  2. We’ve changed the labels from primary-blue to gray to differentiate them from buttons.
  3. We’ve adjusted the spacing to feel more comfy.

  

• The footer has been visually revamped (#2130). Specifically:

  1. Primary blue links didn’t have enough contrast on the light gray background.
  2. The agency logo has been scaled down to a medium size for the medium footer.
  3. The contact info has been moved onto one line to consume less vertical space (especially on mobile).
  4. The overall spacing has been adjusted to be more consistent.

  

• The header has been visually revamped (#2131). Specifically:

  1. The underline marker extends beneath the down arrow.
  2. We’ve balanced column spacing to align with the grid and allow for longer page titles.
  3. We’ve made overall spacing improvements for consistency.

  

Other changes

• The footer example provided by documentation included an <h3> inside an <address>, which was not standard HTML. The <h3> has been moved outside the <address> (#2128).

• Disabled button styles such as usa-button-disabled are now deprecated (#2152). The disabled attribute on a button is now all that’s needed to style a button so it looks disabled. For example, use <button class="usa-button" disabled> instead of <button class="usa-button-disabled" disabled>. The old button styles ending in -disabled will be removed in a future release of the Standards.

New features for core development

• A mechanism for testing for visual regressions has been added (#2067, #2129).

• The aXe accessibility tool is now run on all fractal components during testing, to ensure that accessibility regressions don’t occur.

Version 1.3.1

August 22, 2017

Bug Fixes

• Sub-navigation now has the proper height again (#2092).
• Form submission on the Fractal site is now disabled (#2113).

Version 1.3.0

July 21, 2017

New Features

• Grid Offsets - you can now utilize the usa-offset-* classes to indent elements within the grid (#1721).
• SASS Source In ZIP distribution - The SASS source code for the Standards is now included in the USWDS ZIP distribution, in the scss directory (#1739). All dependencies such as Bourbon and Neat are also included. This makes it easier for people who don’t have access to Node–or who are unfamiliar with the command-line–to leverage the SASS.

Bug Fixes

• Example templates now place the “menu” mobile navigation button after the site logo in their HTML, resulting in a more logical tab ordering (#1651). Users of the standards may want to reflect this change onto their own websites for improved accessibility.
• The search button toggle (sometimes present in the header of pages) now works in IE11/Edge (#2034).
• Accordions now work on devices that support both touch and mouse input (#1993).
• A number of radio button and checkbox issues have been fixed (#1929).
• The validator component used for, among other things, password validation, has been fixed (#1992). As part of this work, the js-validate_password class is now deprecated and documentation for this component has been added to the Standards site.
• Users of SASS will no longer see Bourbon deprecation warnings when importing the USWDS stylesheets (#1904).
• When navigation menus contain links to targets on the current page (e.g. #some-section), the menu now collapses after the link is clicked (#1962).
• When accordions are expanded, the top of the accordion is scrolled into view if needed (#2021.).

Kudos

Thanks @colinalford for submitting a pull request to add grid offsets to the Standards!

Thanks @JJFranko for help figuring out the root cause behind #1993!

Version 1.2.1

June 07, 2017

• Changes to the circle.yml config to fix npm publishing issues.

Version 1.2.0

June 06, 2017

This release marks a complete rewrite of our JavaScript to make interactive components more friendly with third-party frameworks such as React and Angular.

:warning: If you’re upgrading from a previous version and you use the Standards JS modules in a custom bundle, please read the migration guide. (If you’re using the static JS or don’t understand what any of this means, then you can safely skip the guide.)

New features

• Lists appearing inside the usa-content class now have the same maximum width as paragraph content.
• All events are now handled via delegation, rather than listeners on individual elements. See other changes for more information on our backwards-compatible API changes.
• Accordions now support multiple open panes with aria-multiselectable="true" on the .usa-accordion or .usa-accordion-bordered element.
• We no longer polyfill the global Array.prototype.forEach and Array.prototype.filter methods, and instead use the array-foreach and array-filter modules, commonly known as “ponyfills”. If you’re targeting IE9 or earlier and need these methods, you can get them from polyfill.io.
• usa-alert-paragraph class added for creating alerts that are paragraph width instead of the default width.

Bug fixes

• The .usa-skipnav component now works as originally designed, setting tabindex="0" on the target element when the link is clicked, then returning it to tabindex="-1" when blurred.

Other changes

• All of our JavaScript and tests have been rewritten to use ES2015 features such as const, arrow functions, and template literals. We’re using Babel to compile to browser-friendly, backward-compatible ES5.
• We have introduced a suite of v1.x compatibility unit tests and a tool called cracks to help us avoid introducing breaking JS API changes in the future. (In v2.0.0, the v1.x unit tests will be removed.)

Version 1.2.0 release candidate 1

May 24, 2017

This release marks a complete rewrite of our JavaScript to make interactive components more friendly with third-party frameworks such as React and Angular.

You can install this pre-release with npm:

npm install --save uswds@1.2.0-rc1

Please let us know if you run into any troubles!

:warning: If you’re upgrading from a previous version and you use the Standards JS modules in a custom bundle, please read the migration guide. (If you’re using the static JS or don’t understand what any of this means, then you can safely skip the guide.)

New features

• Lists appearing inside the usa-content class now have the same maximum width as paragraph content.
• All events are now handled via delegation, rather than listeners on individual elements. See other changes for more information on our backwards-compatible API changes.
• Accordions now support multiple open panes with aria-multiselectable="true" on the .usa-accordion or .usa-accordion-bordered element.
• We no longer polyfill the global Array.prototype.forEach and Array.prototype.filter methods, and instead use the array-foreach and array-filter modules, commonly known as “ponyfills”. If you’re targeting IE9 or earlier and need these methods, you can get them from polyfill.io.
• usa-alert-paragraph class added for creating alerts that are paragraph width instead of the default width.

Bug fixes

• The .usa-skipnav component now works as originally designed, setting tabindex="0" on the target element when the link is clicked, then returning it to tabindex="-1" when blurred.

Other changes

• All of our JavaScript and tests have been rewritten to use ES2015 features such as const, arrow functions, and template literals. We’re using Babel to compile to browser-friendly, backward-compatible ES5.
• We have introduced a suite of v1.x compatibility unit tests and a tool called cracks to help us avoid introducing breaking JS API changes in the future. (In v2.0.0, the v1.x unit tests will be removed.)

Version 1.1.0

April 27, 2017

New features

• The new .usa-embed-container class responsively resizes <iframe> (and other) elements using a standard aspect ratio.
• We are now using Fractal to preview, test, and document the code for all of our components. Check out this release in Fractal!
• We are now publishing static builds on Federalist, which means that our release branches will produce predictable, versioned URLs, such as this release’s CSS and JavaScript.
• You can now npm run watch to rebuild just the CSS and JavaScript whenever the source files change.

Bug fixes

• The visual behavior of the first and last child of .usa-grid-full now matches that of .usa-grid. See #1773 and #1768 for more info.
• We now recommend that footer navigation use the usa-grid class rather than usa-grid-full for better horizontal text alignment. See 18F/web-design-standards-docs#243 for more info.
• Unordered lists within accordions are now styled consistently. See #1719 and the fix in #1825.
• Buttons nested inside accordions without the usa-accordion-button class will not mistakenly trigger the accordion’s show/hide logic, as reported in #1762. We’ve also refactored the accordion JS to simplify and improve coverage. See #1806 for more info.

Other changes

• ⚠️ Heading mixins, h1() through h6(), have moved from elements/_typography.scss to core/_utilities.scss. See #1763 and the fix in #1775.
• Add code coverage badge to the README, and a coverage section in the contributing docs.
• Update our documentation to reference the new default branch, develop (formerly staging).
• Lots of updates to our running list of who is using the Standards.

Kudos

• Thanks to @sawyerh for the typography mixins in #1775.

Version 1.1.0 pre-release

April 17, 2017

This is a v1.1.0 preview release. See #1796 for changes since v1.0.0.

You can install this pre-release with npm:

npm install --save uswds@1.1.0-pre

Please let us know if you run into any troubles!

Version 1.0.0

February 23, 2017

This is our first official major release. Read about our new release process and how we are updating the workflow to formally follow semantic versioning.

Fixed

• Disabled submit buttons without the usa-button class were accidentally styled via [type="submit"]:disabled. We now apply disabled styles only to .usa-button:disabled. See #1523.
• Checkbox inputs that are checked and disabled are now styled properly. See #1628.

Changes

We’ve made a couple of changes to our npm configuration:

• We’ve upgraded lodash.debounce to a “production” dependency, which should solve the problem of missing dependencies for some user installations.
• Our package.json now references the static “tarball” version of our release rather than the git endpoint, which means that you can npm install uswds without access to git.

The following are changes to our build tools and process that have no direct impact on the code itself:

• The README, LICENSE, and CONTRIBUTING markdown documents are now included in our static and npm distributions.
• Use stylelint to ensure that our SCSS files meet our own guidelines.
• Measure JavaScript code coverage with istanbul and analyze coverage with code climate.
• Commits (merges) to master are now automatically published to npm via our CI service.

Kudos

We’d like to thank all the contributors who worked on our current release! We appreciate your service and all the time you spent making the Standards even better. Big kudos to the following folks:

• @awolfe76

If you have questions about these upcoming changes, please feel free to email our team at uswebdesignstandards@gsa.gov.

Version 0.14.0

December 16, 2016

Fixed

• Fix styling of alert components that do not have a header #1430
• Fix government banner font glitch on smaller screen widths #1571
• Move *Required flag on forms to better placement for low vision users #1350

Changed

• Refactor header css to match the JavaScript asset restructuring work #1434
• Add ability to create a custom alert via Sass mixin
• Remove Politespace as a dependency #1385
• Use specific subset of Bourbon Neat, which allows us to remove Python as a language dependency #1554

If you have questions about these upcoming changes, please email our team.

Kudos

We’d like to thank all the contributors who worked on our current release! We appreciate your service and all the time you spent making the Standards even better. Big kudos to the following folks:

• @carlosvalle
• K.C. Jones-Evans

And thank you to everyone for your comments and feedback!

Full Changelog

Version 0.13.3

December 01, 2016

Fixed

• The fonts were twice as large as they should have been. This was due to !default being added to $em-base, which created a null value for this font sizing. See #1590 for more details on the issue.
• Fix missing search box for extended header on smaller screens. See #1572 for more details on the issue.

Changed

• Added a WHO_IS_USING_USWDS.mdthat lists all of the websites and applications we know of that are currently using the Standards. This replaces the original wiki page. #1573
• Removed copy in the README.md around the repo split. #1589

If you have questions about these upcoming changes, please email our team.

Full Changelog

Version 0.13.2

December 01, 2016

⚠️ This release has a few known bugs:

• Fix missing search box for extended header on smaller screens. #1572
• Issue around font sizing. #1590

We recommend upgrading to v0.13.3 of the Standards. If you are unable to do so, please use the attached uswds-0.13.2patch.css (un-minified) or uswds-0.13.2patch.min.css (minified) and uswds-0.13.2patch.map files on this release.

Changed

1. The header component has been broken up into more modular pieces, each with their own JavaScript tests (see code changes here). Here is the breakdown of what has been changed:
   • header/mobile is now navigation
   • header/search is now search
   • To support testing, the navigation and search JS modules both export an off() function for removing listeners added by the top-level export.
2. The utility functions for element classes (addClass(), removeClass(), and toggleClass()) have been replaced with a polyfill for the Element.classList property (see code changes here).
3. Some of the SCSS files have been reorganized (see code changes here and here). See the deprecation notes (“Upcoming backwards incompatible changes”) below for more info.
4. Our README now includes more helpful instructions for users on various platforms and fixes some formatting (see code changes here).

Upcoming backwards incompatible changes

We are planning to make the following changes to the Draft U.S. Web Design Standards in future releases. In keeping will semantic versioning conventions, we will never intentionally introduce breaking changes without updating the minor and major versions accordingly. Here are the upcoming changes:

1. The Standards will no longer require jQuery or include it as part of the package you download. If you are using jQuery for other parts of your site, you will have to download it separately. It won’t come included in the Standards any more. We decided to make this change because we heard from our users that requiring jQuery for the WDS conflicted with other versions of jQuery they were already using.
2. We have reorganized some of our SCSS “partials”, and will be removing the deprecated paths in a future release. If you import the USWDS into your own Sass or SCSS files, here is what you need to know:
   • We have replaced the SCSS all “entry point” with uswds, and set up an alias for all (_all.scss) to ease the transition for users of previous versions. Upgrade instructions:
     • replace @import 'all'; with @import 'uswds';, or
     • replace @import 'uswds/all'; to @import 'uswds/uswds';
   • We have deprecated the SCSS uswds/defaults partial in favor of uswds/variables, and added !default to all of our variables so that they can be selectively overridden by a previous import. Upgrade instructions:
     • remove @import 'core/defaults'; or @import 'uswds/core/defaults';
     • add @import 'core/variables'; if you don’t import it already
     • move your variable customizations before @import 'core/variables'; for consistency
     • remove any unmodified variable declarations from your customizations to avoid accidentally overriding future changes
   • uswds/core/grid-settings is no longer necessary, as the grid settings are all declared in uswds/variables. Upgrade instructions:
     • remove @import 'core/grid-settings'; or @import 'uswds/core/grid-settings';

If you have questions about these upcoming changes, please email our team.

Full Changelog

Version 0.13.1

October 06, 2016

NEW Page templates and government banners

This release includes the addition of two different page templates and government verification banners.

Upcoming backwards incompatible change

In the near future, the Draft U.S. Web Design Standards will no longer include jQuery as part of its package. Users will be required to include jQuery(v2.2.0+) when using the Standards. If you have questions about this upcoming change, please email our team at uswebdesignstandards@gsa.gov.

Fixed

• Reduce specificity on inputs #891
• Fix search bar #1481
• Add missing 5/12 and 7/12 grid items #1383
• Fixing mobile.js from having duplicative events from firing #1496

Changed

• Add background color for thead > tr > td
• Add font smoothing mixin #1427 #1440
• De-nest grids #971

Full Changelog

Version 0.12.1

September 09, 2016

This is a patch level release that adds missing images for the mobile version of the new headers component into the src directory. In version 0.12.0 they were added as part of the website/docs assets and not part of the package itself. Please use v0.12.1 in place of v0.12.0!

Full Changelog

Version 0.12.0

September 01, 2016

Updated to 0.12.1: Release 0.12.0 was missing some images for the new Headers component. You may run into issues using 0.12.0 on your project.

Please use version 0.12.1 in place of 0.12.0!

NEW Headers component

This release includes the addition of a headers component, which helps users identify where they are and provides them a quick, organized way to reach the main sections of a website. Check out our documentation to learn more about our most recently added component.

Upcoming backwards incompatible change

In the near future, the Draft U.S. Web Design Standards will no longer include jQuery as part of its package. Users will be required to include jQuery(v2.2.0+) when using the Standards. If you have questions about this upcoming change, please email our team at uswebdesignstandards@gsa.gov.

Fixed

• Fix search bar doc links to accessibility guidelines
• Design downloads on WDS site are not current #37

Changed

• Use Sass variable for font path
• Refactor JavaScript to remove jQuery dependency #1351
• IE bug on secondary links search form #1404
• New UI component: Headers and navigation #1312
• Make CSS background image path links a Sass variable #1007

Kudos

We’d like to thank all the contributors who worked on our current release! We appreciate your service and all the time you spent making the Standards even better. Big kudos to the following folks:

• hursey013
• jessieay
• carlosvalle

And thank you to everyone for your comments and feedback!

Full Changelog

Version 0.11.1

August 18, 2016

Fixed

• Remove hash for javascript:void(0); in code examples.

Changed

• Simplify lists to use browser defaults #1091.
• Using sr-only mixin for .usa-sr-only class.
• Generate component example code using gulp tasks.
• Removing JavaScript from website #1353.

Kudos

We’d like to thank all the contributors who worked on our current release! We appreciate your service and all the time you spent making the Standards even better. Big kudos to the following folks:

• @carlosvalle

And thank you to everyone for your comments and feedback!

Full Changelog

Version 0.11.0

August 04, 2016

Accordion backwards-compatible changes

In this release, we’ve refactored the accordion code so that it is easier to use, less specific, and more concise. The accordion functionality from previous releases will still work and there are instructions on how to make the upgrade when it best suits the needs of your project.

Fixed

• Copyediting for 18F style

Changed

• [Search bar]: Reduce font size in ‘Medium’ and ‘Small’ bars #594

Kudos

We’d like to thank all the contributors who worked on our current release! We appreciate your service and all the time you spent making the Standards even better. Big kudos to the following folks:

• @PilgrimMemoirs
• @nicoleslaw

And thank you to everyone for your comments and feedback!

Full Changelog

Version 0.10.0

July 21, 2016

We have been made aware that we didn’t explicitly outline a backwards-incompatible change for the accordion component in v0.9.4, and we’d like to apologize for any inconvenience this may have caused you or your team. In the release notes for 0.9.4, we’ve added directions on how to update your accordions with these changes when you make this upgrade.

Backwards-incompatible changes version

In this release, we’ve made a specific backwards-incompatible change to the the structure of the scss files. Prior to this release, users could update their project specific scss variables by changing the values in _variables.scss. This release removes that file and from the core import and will require users to manually add their application-specific Sass files.

Fixed

• Remove dead link from form controls and form templates accessibility section #1313
• Small screen + landscape mode = impossible to scroll because of header height (Moto E, Android 4.4, Chrome 44) #345
• Unordered lists nested inside ordered lists appear ordered #1328

Changed

• Remove variables.scss file #1168

Kudos

We’d like to thank all the contributors who worked on our current release! We appreciate your service and all the time you spent making the Standards even better. Big kudos to the following folks:

• @cfarm
• @toolness

And thank you to everyone for your comments and feedback!

Full Changelog

Version 0.9.6

July 14, 2016

Fixed

• Fixed an incorrect reference on the typography page. #1274
• Fixed some code sample styles. #1274
• Styled the site footer by class to prevent further problems with the footer component. #1274
• Remapped routes on deployments. #1308
• Fixed linter errors. #1274

Changed

• Removed the splash page to provide quicker access to the UI components. #1274
• Added a sticky horizontal navigation bar to expand the site content. #1274
• Added our product roadmap and component maturity scale. #1274
• Eliminated the Visual Design section of the site to prevent confusion, and moved Typography and Colors into the side navigation. #1274
• Expanded the Getting Started instructions for developers and designers #1274
• Separated the design file downloads by file type. #1274
• On mobile, moved the Menu button to the right side and added collapsible sections in the mobile navigation. #1274 and #1314
• Updated the styling of the disclaimer bar to make it less obtrusive. #1274
• For each of the components, we changed the maturity levels to reflect our updated Component Maturity Scale. #1274
• We added an unstyled button mixin. #1274
• We also added a media link mixin that can be used on images inside of links to get proper focus states. #1274
• We updated the grids’ outer margins from 30px to 15px on mobile to increase viewable screen space. #1274
• We fixed the alignment of checkboxes and radio buttons (for IE11 and below) so that they’re vertically aligned. #1300
• We adjusted the max width of lead text to 75 characters. #1274
• Updated our sidenav navigation items to make the line spacing more comfortable when the menu drops to more than one line #1274
• Changed the sidenav in the page navigation so it’s displayed via Jekyll instead of CSS (this prevents CodeSniffer false positives!). #1274

We love outside contributions!

The continued success of the Standards relies on contributions from folks like you. To make a contribution, file an issue in our repo (and do let us know if you have any questions).

View the full changelog here.