[caption id=”attachment_21094” align=”alignnone” width=”2433”] Source: gao.gov[/caption]
The U.S. Government Accountability Office released a report on the fiscal and administrative state of 18F and the U.S. Digital Service, both established to make federal government digital services work better for users, and it appears the agency could use some help from the two on its own website, gao.gov.
Here are four ways GAO’s digital operations must be rebooted to meet the needs of today’s web user, and how 18F and USDS helped us better understand all of this.
HTTPS
The GAO website is not secure for users visiting gao.gov.
As 18F has emphasized, HTTPS protects visitor privacy with a secure, encrypted connection and is an important practice for .gov domains to adhere to.
The move to HTTS for all .gov websites began more than a year ago, yet gao.gov still remains unencrypted.
Fortunately for GAO, 18F and USDS created a number of HTTPS resources for governments and agencies having difficulty understanding its importance and quickly adopting it.
Mobile-friendly
The GAO website is not mobile-friendly.
Whether it’s a phone, tablet or laptop, gao.gov doesn’t adapt to the device you’re using. As billions of people around the world are now using mobile devices to access information, it’s requisite that all government websites are mobile-friendly so their services are accessible to everyone.
Fortunately for GAO, 18F and USDS created the U.S. Web Design Standards that makes it easy for anyone creating government websites to build mobile-friendly sites (including accessible color schemes, which GAO does a mediocre job on).
Update:
Alex Howard notes that GAO has a separate mobile version (launched in 2010) of its website and an app (launched in 2012). While these were great technological enhancements at the time, they no longer meet today’s standards around responsive design and streamlined development practices.
Rather than building one site that adapts to all devices, GAO has created two development environments and duplicated development costs.
While an app is certainly mobile, it doesn’t qualify in this case, as it’s a secondary outlet to the website. </em>
Open data
GAO does not have a comprehensive open data strategy.
While the site provides a great list of RSS feeds, not all reports are in data-friendly formats (all are, however, in PDFs). There also appears to be no public application programming interface (however Sunlight Foundation has created one via its Sunlight Congress API).
Unsurprisingly, GAO’s report on 18F and USDS isn’t available through an open, accessible, digital format.
Fortunately for GAO, while not directly created by 18F or USDS, but done by many who now serve in each, there is Project Open Data to help it get started on executing an effective open data strategy.
Analytics
GAO doesn’t participate in the federal government’s Digital Analytics Program.
As the agency that provides oversight on federal government activities, it would be great to have more transparency into its website analytics.
Given that gao.gov is already using Google Analytics, and familiar with its tools, this is easily resolved with a simple snippet of code provided by DAP.
Thoughts
I get nervous when policymakers take a myopic approach to assessing technology, especially in a politically charged environment like Washington, D.C., where there are behind-the-scenes personal and business relationships that impact motivations around critiquing new initiatives like 18F and USDS.
I especially get nervous when an agency charged with overseeing federal government technology practices fails the digital test.
If GAO is serious about modernizing its own digital strategy, 18F and USDS can surely help.