Introducing USWDS 2.0

Reinvent the experience, not the wheel

Today, we’re launching U.S. Web Design System 2.0 (USWDS 2.0), 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 your mission and the needs of your audience.

USWDS is a library of code, tools, and guidance to help government teams design and build fast, accessible, mobile-friendly government websites backed by user research and modern best practices. USWDS 2.0 is an important update to the design system — it introduces a powerful toolkit of new features to help make creating useful, consistent digital services faster, simpler, and more fun.

A colorful collection of screens and interface components

We’re proud that USWDS currently powers nearly 200 federal websites and we’re committed to making the design system work better for any federal website. With USWDS 2.0 we’re introducing a design system that’s built to grow with your needs — to help teams build better, more engaging websites for the American public.

Over the last two years, we’ve listened to the designers and developers using USWDS. We’ve conducted interviews with project teams, listened to public feedback, and paid attention to the issues in our GitHub repos. We’ve conducted our own research on how designers and developers communicate with each other, and the tools they use to prototype. This research and feedback shaped our priorities for USWDS 2.0:

  • Encourage modular, iterative, user-centered design
  • Promote accessibility and mobile friendliness
  • Develop a consistent design language
  • Support designing with flexibility and coherence
  • Lead with dependable guidance
  • Allow teams to prototype and build quickly
  • Establish a reliable foundation for growth

So, what’s new in USWDS 2.0?


Side by side illustrations show before-and-after examples of a web page. One has the original page and the other shows that page with just a few design system components added

Easier Incremental Adoption

Add a component, not a headache

You don’t need to totally redesign your existing site to get started with USWDS. Adding USWDS 2.0 doesn’t mean breaking existing site functionality, so it’s easier to make incremental changes. Our components and code play well with existing styles, and it’s easy to adapt our default styles to a look-and-feel appropriate to your audience.

  • Isolated class-based styling won’t affect your existing styles
  • Isolated class-based styling
  • Customizable base font size
  • Supports custom typefaces
  • Provides resilient, modular components


An illustration of three designers and developers using design tokens to communicate their intention. They move from themes to components to a finished website.

Practical Design Tokens

A common language for designers and developers

Design and development are all about decision making. Making decisions and communicating these details with the team takes time and has a cost, both in money and energy. USWDS 2.0 design tokens are the common building blocks of visual design decisions (like color, typescale, and spacing units) that all USWDS projects share. By using design tokens, designers and developers spend more time solving problems and less time fussing over pixels, eyedroppering hex codes, and redlining.

  • Design tokens are a common language between designers and developers
  • Creates simple standardized palettes
  • Makes for a streamlined handoff
  • Allows a faster response to feedback
  • Integrates with best-practice guidance
  • Provides coherent and expressive palettes
  • Even spacing units (based on 8px) yield reliable spacing and centering
  • Typescale outputs consistently and predictably, regardless of typeface


Two rows of colors from light to dark and their accessible color combinations.

An Accessible Color System

From AA Large to AAA: Section 508 contrast made simple

Making a good color decision means making an accessible color decision. The USWDS 2.0 color system makes it simple and predictable to pick accessible color pairs. Each USWDS system color has a numeric grade (like the 50 in red-50). The difference between any two grades is what we call the magic number. Colors with magic numbers of 40+ achieve AA Large contrast, magic numbers of 50+ achieve AA contrast, and magic numbers of 70+ achieve AAA contrast.

  • Magic number makes contrast decisions a snap
  • Encourages accessible color choices for your mission and brand
  • Supports practical project theme palettes
  • Is the foundation for expressive color families


An illustration shows five images of websites at different screen sizes, ranging from small to large — each with a different look and feel.

Expressive Theming

Powered by your mission and user needs

Every project is different. Different audiences, different missions, and different goals require different solutions. USWDS 2.0 helps teams reinvent the experience without reinventing the wheel with a flexible design system that encourages customization consistent with our best-practice guidance. Because using user-centered design to adapt our defaults and build new things shouldn’t mean abandoning USWDS guidance altogether.

  • Normalized typefaces allow custom typeface support
  • It’s easier to match your brand to USWDS
  • Custom settings power themeable layouts
  • Integrated with tokens and utilities


This illustration shows another before-and-after example of how a website can use utility classes to change the styles of site elements. Five stylized examples of code are given below the two versions of the page.

Powerful Utility Classes

Prototype faster to get your designs in front of real users

Building and testing a prototype is an invaluable step to understanding how real people use our services. Utility classes are a modern way to use USWDS design tokens to rapidly test a new idea, make tweaks to existing components, or design in code. USWDS utilities help teams deliver actionable prototypes quickly and consistently, and make quick modifications to production components without writing high-specificity CSS.

  • Build new components or modify old ones without touching production CSS
  • Uses modular, atomic, and mobile-first design
  • Optimized for legibility and comprehension
  • Sophisticated customization options
  • Easy to transfer into production Sass with integrated functions and mixins
  • 25 KB gzipped, but optional


An illustration shows a yellow 12-column grid system overlaid on a colorful website.

Simplified 12-Column Layout Grid

A simple, powerful, flexible grid

Layout grids give any website visual coherence. The USWDS 2.0 layout grid is a familiar flexbox-powered grid that gives predictable control to designers and developers. The grid’s simple, nestable structure means any component and any layout, large or small, can implement a grid in a snap — and its mobile-first layout options make them customizable to any screen or situation.

  • Similar to Bootstrap 4 and Foundation
  • Uses a familiar row and column–based structure
  • Built with Flexbox
  • Predictable and nestable
  • Designed to be mobile-first and responsive


The word Hello displayed in Public Sans as though being edited in a font editor.

Introducing Public Sans

A free, open source typeface from USWDS

USWDS 2.0 adds built-in support for custom typefaces, and sometimes you need one that’s simple, neutral, and isn’t Helvetica. Public Sans is an open source, free license typeface (SIL Open Font License 1.1) designed and maintained by USWDS, adapted from Libre Franklin. Just as with our components, we intend Public Sans to be an example of how to design an accessible open source typeface with contributions and feedback from the public — to deliver a useful, neutral, sans serif and continuously improve it.

  • A neutral typeface for interfaces, headings, and body text
  • A consistent alternative to system fonts or other neutral sans serifs
  • Developed for outcome-based continuous improvement just like our components
  • Designed for legibility and readability
  • Features tabular numerals for data design
  • Free and open source


An expanding geometric flower formed from the USWDS logo.

Built to Grow, Designed to Adapt

A stable foundation for the future

USWDS 2.0 is built to grow and designed to adapt. It exists to help teams build new things and explore new solutions — to be more useful to any federal website and to adapt to new problems and new insights. Our new release is the foundation for the future of the design system and a way to maintain predictable, reliable coherence in an ever-changing world of new technology and evolving expectations. We can’t wait to see what you build with it.

  • No new components, but all new components
  • Consistent, predictable BEM naming
  • Overhauled documentation
  • Streamlined development process
  • Easier to integrate new components from outside projects
  • Prepared to grow and adapt to user needs and industry best practices

Like any true 2.0, this is a living product. We’ll continue to test our decisions and assumptions with real-world feedback as it develops and evolves. We encourage you to explore USWDS 2.0, contribute your own code and ideas, and leave feedback on GitHub, email, or our Slack channel. And join our new mailing list by sending an email to uswds-subscribe-request@listserv.gsa.gov. We’ll use your input to continuously improve the system with ongoing regular releases. We’re listening.


USWDS is a team effort, built in the open for the public good. A heartfelt thank you to everyone who contributes to the project and whose work supports and inspires our own — your passion, smarts, and support are invaluable. We can’t do it without you.

A sincere thanks to Sara Cope, Stephanie Green, Jeremy Zilar, Jacob Parcell, Toni Bonitto, Andre Francisco, Dahianna Salazar Foreman, Wesley Thompson, Adam Biagianti, John Donmoyer, Brian Hurst, Steve Walker, Jen Thibault, Aviva Oskow, Christine Bath, Austin Hernandez, Nick Ng, Eddie Tejeda, Amir Reavis-Bey, Miguel Sousa, Scott Kellum, Eli Altman, Aaron Borden, Andrew Dunkman, Sawyer Hollenshead, Sha Hwang, Jared Cunha, Matt Langan, Heather Battaglia, T. Carter Baxter, Matt Yoder, David Way, nolawi, Amber Reed, Shawn Allen, Micah Taylor, Scott Weber, Brendan Sudol, Brandon Ruffridge, Atul Varma, Maria Marrero, bet4a, Robert Romore, Dave Methvin, Nick Schonning, cathrowe, fat32, Juliette Cezzar, Pablo Stanley, Eric Ronne, Ryan Thurlwell, Linzi Berry, Sam Soffes, Pablo Impallari, and Dave Crossland.

Tags:

File name

2019-04-08-introducing-uswds-2.md

File path

posts/2019/04/2019-04-08-introducing-uswds-2.md

Link Shortcode

{{< link "posts/2019/04/2019-04-08-introducing-uswds-2.md" >}}

Top