Sign-in Changes | VA Identity Flows | Terms of use accessibility | Observer meta-research | Experience research
VA.gov Identity | Unified terms of use, screen reader prototype
Objective: Create a single, unified, terms of use page across all VA digital sites and apps. This increases the user experience since veterans only need to approve, what they see as an annoyance, one time. I included screen reader participants in research to make sure my design worked for those with assistive technology.
My Role: I led research as the lead UX researcher on the multidiscipline VA.gov identity team. Another research on my team assisted. I also worked with engineers who built the code to make this work. I designed this page using the VA Design System and accessibility guidelines from WCAG and 508.
Screenshot of a usability session in Zoom
Time for an update
This project started when the VA Office of General Council wanted to update the terms of use. VA has several digital properties including websites and apps that each had their own terms of use. Many veterans use several experiences, which means agreeing to the same terms of use multiple times. My team, as the owner of the sign-in experience, was eager to make this experience better. Armed with research data, we successfully convinced all stakeholders for a unified terms of use.
Accessibility research first
Terms of use is a potentially blocking point - each veteran must get past it after signing in. It made accessibility even more important. Well before our front end would have a coded page, we researched with an early iteration prototype.
Figma had started offering some screen reader functionality. I was eager to try this new feature. As the first one at VA to try it, I also agreed to present what I learned to other researchers.
Screen reader text of the Figma design
Screen reader text of the Figma design
Figma + screen readers
I found several trade-offs using Figma with screen readers. For example, one way to have a screen reader read off text as a header is to include “heading level [#]” as text content before the text of the header. However, this makes “heading level [#]” visible in the prototype, and not everyone who uses a screen reader is fully or even partially blind.
Another way to have screen readers read off text as a header in Figma is to use an image file with the title of heading. This makes it look fairly seamless at the standard zoom level, but the trade-off is that the screen reader will first announce it as a heading and then as an image, as seen in the screen shot of the screen reader transcript.
Practice makes perfect?
I practiced going through our team’s design with a screen reader to make sure everything worked as the best as possible. Then I asked someone from the VA accessibility team to be a practice screen reader participant. Practicing both the conversation guide and the prototype beforehand, allowed me to iterate further on both before working with real participants.
Even with the tradeoffs of the Figma feature not working perfectly, we found some valuable insights to iterate the design. Research confirmed the usability of the VA Design System accordions in this usage. We confirmed that most folks want to get to the accept button and move on as quickly as possible. I closely watched metrics after launch. This proved that folks found the accept button - a successful launch!
Final terms of use design, live page