Component prioritization
We recently published an initial version of our product roadmap to provide interested folks a better sense of what tasks we’ll be undertaking (and in what relative order).
Along similar lines, we’d like to provide more insight into how we’re choosing the order in which we research, build, and test new components.
The general public’s needs are by far the most important factor influencing how we add to and refine the Draft U.S. Web Design Standards. Our primary goal is to provide developers and designers with the components they need to create functional, accessible, and easy-to-use government websites. This, in turn, helps members of the public more easily access the resources they need. Every part of the Standards, from colors to code, meets high accessibility standards and is Section 508 compliant, meaning sites built using the Standards have a broader reach.
We also take into account the needs of those who are implementing government websites and using the Standards. The Standards are intended to be used to create consistent, trustworthy, and enjoyable digital experiences. We frequently consult with our agency partners and other interested groups to determine how best to represent their needs via the components we develop.
Finally, we strive to create components that are broadly applicable and can be reused by numerous agencies. In addition to being more cost-effective than single- or limited-use tools, reusable tools also provide value to a greater number of agencies and individuals, which is another of our goals.
Our roadmap provides a more granular view of what we’ll be working on. In general, here are the categories of tools and components we’ll be addressing:
1.) Components for standing up a site quickly
- Front end scaffolding (HTML, JavaScript, and CSS)
- Application shell (header/footer)
- User registration forms
- Accordion
- Menu navigation
- Site navigation
- Additional components, including headers and navigation
2.) Forms
- Simple forms (one page or shorter)
- Long forms (longer than one page)
- Form language
3.) Security
- Logins, passwords, and 2FA
- Establishing site trust and credibility
- Electronic signatures
4.) Notifications and communication
- Breaking news alerts
- Presenting data
- Other components, as necessary
5.) Other components
- Search patterns
- Transaction flows
- Other components, as necessary
Have questions or comments? Email the Draft U.S. Web Design Standards team at uswebdesignstandards@gsa.gov.