Roughly 1 in 4 people have some form of sight loss, so you may be curious how your user journey fares when experienced with a visual impairment. Velocity’s WCAG screen reviews help designers build to a baseline of accessibility, but there is still a chasm in designing for how interfaces are alternatively perceived.
Consider the screen below. A loading indicator and written reinforcement set a clear expectation for users to wait some time before proceeding. So why, then, when testing with a limited-vision persona, are they so intent on clicking the area below the loading? The activity starts to make sense when we can see the effect of a visual impairment; the distinctive purple area on white is likely being clicked because it could be a button to proceed.
Blurred vision results appear alongside standard agentic simulations.
Check out an example report 🔗
More accessibility soon…
Thanks to our friends at Hassell inclusion, for highlighting how many enterprises are adopting accessibility conformance reports (ACR) and, within them, VPATs and templates that translate a world of standards (e.g., Section 508 and other legal frameworks) into actionable testing criteria for products and services. Within the VPATs, we are particularly interested in simulating:
- Limited vision
- Without perception of colour
- Limited cognition, language or learning
Blurred vision is currently in beta.
Try it out for yourself and let us know your impressions.
contact@appvelocity.io
