We’ve added two powerful, new tools to our development workflow.
From time to time we post product updates, guidance, and interviews we’ve conducted with users of the U.S. Web Design Standards.
As mentioned in our recent Q&A with the team at NASA, the U.S. Web Design Standards team is sitting down with various agencies that are using the Draft Standards. In this second post in our series, we met with the team at the U.S. Customs and Border Protection and learned how they used the Standards to train, develop, and design their various websites and applications.
Every quarter the team takes a look at how many users have been exposed to the U.S. Web Design Standards across the federal government. We do this by pulling a subset of information that’s collected as part of the Data Analytics Platform.
The team recently worked on the design assets to ensure that the latest components are present in the provided sticker sheets. These sticker sheets are meant to provide design teams with the assets they need to create wireframes or high-fidelity compositions quickly and effectively. The biggest change is the team’s decision to retire the Omnigraffle sticker sheet.
The U.S. Web Design Standards are currently implemented on hundreds of government sites, with an audience of more than 26 million monthly users, and they’ve been recommended by the Office of Management and Budget for all government agencies. We chatted with Brandon Ruffridge, Senior Software Developer at NASA’s Glenn Research Center, to talk about his team’s use of the U.S. Web Design Standards.
With the recent launch of U.S. Web Design Standards 1.0, it’s time for the team to take a look at the road ahead and determine what areas of the Standards they should focus on. To accomplish this, the team meet for a collaborative research and design workshop where ideas were proposed then mapped based on the ideas importance and feasibility.