Research

News and Events on Research

225 posts

Mobile Product Testing Guidelines and Resources

You have started developing your mobile product, but you may be wondering what and how to test. As with any form of software development, mobile testing should be done intermittently throughout all development stages. This article was developed as part of the Mobile Application Development Program to provide agencies with some general testing strategies, types,
Aug 22, 2013

Mobile Product Security and Privacy Testing Resources

Security testing is used to ensure that a mobile product does not pose a threat to agency IT systems and databases. In addition, privacy testing ensures that an app does not put the user’s personally identifiable information into a compromisable position. This article was developed as part of the Mobile Application Development Program. See our
Aug 05, 2013

Mobile Product Performance Testing

Performance testing is used to verify that an app or web page will display quickly to the user and will continue to function as the number of users increases to peak loads. Performance is an important consideration for mobile applications because the connection speed of users is often slower and more variable for mobile users than desktop users. Surveys
Aug 05, 2013

Mobile Product Accessibility Testing Resources

Accessibility testing is a subset of usability testing and is the inclusive practice of making websites and mobile applications usable by people of all abilities and disabilities. You do this by testing mobile websites and/or applications on all leading browsers, mobile devices and screen readers. This article was developed as part of the Mobile Application
Jul 31, 2013

Business.USA.gov – Usability Case Study

When redesigning a site, it’s easy to place menu items, text and other content wherever you can make them fit. It’s harder to take a step back and ask the strategic question: Is this the best place for this? A good rule of thumb is to never make any changes randomly—base your decisions on user
Jul 02, 2013

Fueleconomy.gov – Usability Case Study

Many technical websites have a hard time explaining information to the general public. This happens because users don’t understand the industry-specific or scientific terms. Fortunately, solutions to these problems are fairly easy—changing menu and navigation item text, or adding a line of explanatory text on key pages or complex graphics. The DigitalGov User Experience Program
Jul 02, 2013

Army.mil – Usability Case Study

If you want to make a website more efficient and user friendly, then it’s not enough just to have your most valuable information on the site. People are busy—they want to find what they’re looking for, and they want it fast. You don’t always need to redesign an entire site to make things easier to
Jun 19, 2013

Functionality and Usability Testing Resources

Functionality testing verifies that the functions of a product or service is working as intended. Each function is tested by providing appropriate input, verifying the output and comparing the actual results with the expected results. Usability testing measures the ease of use and intuitiveness of a product or service by asking users to perform a
May 25, 2013

ATF.gov – Usability Case Study

The Bureau of Alcohol, Tobacco, Firearms, and Explosives has some really valuable information for the public that a lot of people search for on ATF.gov. It’s important that the information is easily and quickly accessible. Government agencies reach a wide audience with their information, so making sure everyone can understand your content is important. The DigitalGov User
Apr 29, 2013

Usability Testing + Gov APIs = Best

Good APIs can transform intimidating data sets into something that people can use. Good government APIs can create a better connection between government and citizens. The Digital Government Strategy has spurred Federal adoption of APIs, and the Digital Services Innovation Center and DATA.GOV teams are supporting these efforts by releasing a swath of guidance and
Apr 29, 2013

Regulations.gov – Usability Case Study

More and more people use search as their primary means of finding what they are looking for. When users get confused by the search results, or can’t immediately find what they are looking for, they’re going to get frustrated. They may even leave the site for good. The DigitalGov User Experience Program helped test Regulations.gov on October 5, 2012, to
Mar 22, 2013

SaferBus Mobile App – Usability Case Study

When designing a site, remember that your terms and icons are like signposts that show people where your links and pages lead. Make sure that you use words and pictures that are easily understood or people will have trouble using your site. Small changes like underlining links or adding arrows to indicate expandable information can
Mar 21, 2013

Contractor Vehicle Navigator – Usability Case Study

When users interact with a website to find information, it is important that we help them find their way by using plain language, clear terminology and visible help text. On December 7, 2012, the DigitalGov User Experience Program helped test the U.S. General Services Administration’s Contract Vehicle Navigator website. This Navigator site helps contracting officers find
Feb 19, 2013

SAM.gov – Usability Case Study

One of the most vital parts of any website is its starting point. When a visitor arrives on the main page of your site, they should be able to quickly tell what the main tasks are and how to perform them. Visual cues and plain language are the best ways to accomplish this. The SAM.gov
Dec 17, 2012

IRS – Usability Case Study

Acronyms and jargon are fine when you want to communicate quickly to an internal audiences or to like-minded readers. Once the scope of your audience widens, however, these elements can make your pages harder to understand. The IRS recognized that its pages about tax planning for retirement were reaching an audience beyond tax professionals, and
Dec 14, 2012

Weather.gov – Usability Case Study

After conducting a usability test and listening to customer feedback, the Weather.gov team and the DigitalGov User Experience Program identified these three issues as both important and quickly solvable. Problem 1: Terminology and Labels Confusing The terminology and labels used were either too technical or too abstract for users to understand—a far cry from the plain
Dec 06, 2012