Accessibility research Frequently Asked Questions
There’s a misconception that accessibility research is complex and requires new skills and a large shift in how research is conducted. In fact, many UX research methods also apply to accessibility research. But, having questions about kickstarting a new process is natural – so we’ve got expert answers!
Why is accessibility my responsibility?
Prioritizing accessibility is everyone’s responsibility. By involving every team in your organization you can accelerate meaningful progress. Establishing an accessibility champions program can help build a shared sense of responsibility and bring like-minded people together. You can also offer specialized training to ensure teams have the skills to support organizational goals and drive KPIs.
What’s the difference between accessibility testing and usability testing?
Accessibility testing is the process of verifying that people with disabilities can navigate your digital product using assistive technologies. It is often tied to legal and regulatory requirements and works to identify barriers that prevent people with disabilities from using your product.
Usability testing evaluates how easily all users can accomplish their goals when using your product, including people with disabilities. It ensures people with disabilities can achieve the same outcomes as those who don’t require accessible accommodation. Fable’s Accessibility Usability Scale (AUS) is a free tool you can use to measure the usability of a digital product for an assistive technology user.
These testing types are complementary and essential for creating an inclusive, user-friendly product. Accessibility testing ensures no one is excluded, while usability testing optimizes the experience for all.
Why should we test for accessibility when we don’t know how many people with disabilities use our product?
People with disabilities represent a massive group of potential future customers. 1.3 billion people in the world have a disability, which represents 16% of our global population. In the US, 1 in 6 people have a disability. Even if there aren’t many people with disabilities using your product now, they could become loyal customers if the experience was accessible.
It’s also important to remember that tracking how many people with disabilities are using a product assumes that accessibility will only benefit those users. In fact, accessibility benefits all users by creating interfaces that are universally attractive, easy to understand, and easy to use. When your products check all these boxes you create greater potential to grow your customer base.
We aren’t getting complaints about accessibility from our users, so we don’t need testing, right?
Silence isn’t the same as acceptance. If you aren’t getting complaints, it might be because people with disabilities aren’t using your products due to accessibility challenges. And if your products aren’t accessible then there’s a good chance your customer complaint channels aren’t either.
According to our Fable community research panel report, 9 in 10 respondents will try to find a better option when they come across an inaccessible brand. If they find a solution that meets their needs, they tend to stick with it. People with disabilities aren’t necessarily going to complain about your digital products. Instead, they’ll quietly move on to another brand that delivers what they need.
We already use automated testing tools, so why do we also need Fable?
Automated testing tools identify technical compliance issues, like missing alt text or color contrast violations. Testing with people with disabilities reveals how actual assistive technology users interact with your product. People with disabilities contribute lived experiences and nuanced perspectives that reveal usability and accessibility issues other testing tools can miss.
“You can do all the accessibility checks you want, but it’s not going to replace talking to people who experience it every day. I’m never going to be able to catch every accessibility issue. Having that collaborative co-design relationship with Fable testers has been instrumental for us.”
– Annabel Weiner, User Experience Accessibility Specialist at Ally Bank
People with disabilities can also go beyond telling you whether it’s possible to complete a task and weigh in on whether the experience is enjoyable. This is a metric you can keep measuring long term using a free tool like Fable’s Accessible Usability Scale (AUS).
We already have a VPAT. Isn’t that enough?
A VPAT (Voluntary Product Accessibility Template) is a document prepared by a product developer or vendor that describes how well a product conforms to the accessibility standards of Section 508 of the Rehabilitation Act.
While a VPAT is a helpful starting point for documenting accessibility compliance, it only summarizes compliance at a single point in time. It isn’t a comprehensive test reflecting ongoing changes or product updates. Since VPAT is self-reported by a product vendor it can also introduce biases or inaccuracies.
Complementing VPAT with more rigorous testing and real-world validation helps to ensure products are both accessible and usable.
Resourcing my team for accessibility research
In this section:
Do I have to learn an entirely new skill set to do accessibility research and testing?
Accessibility research is more about expanding your expertise than starting from scratch. UX researchers already possess the foundational skills and knowledge that are highly relevant to accessibility research, including creating research plans, conducting interviews, analyzing user feedback, and synthesizing findings.
Any knowledge gaps can be quickly filled with targeted training. For example, Fable Upskill offers robust online training specifically designed to help UX researchers learn how to do things like engage with a variety of assistive technology users, plan and scope accessibility research, and take meaningful next steps with research findings.
How much of my time is this going to take?
The ideal state is to have accessibility research flows baked into your existing processes, but you can start small and grow. For example, you can aim to do 20% of user testing with people with disabilities, then keep refining your processes to ensure you always hit that target.
Recruiting and screening people with disabilities to participate in your research projects also doesn’t have to be a massive time-suck. For example, Fable offers on-demand access to a pre-qualified community of people with disabilities. Researchers can choose from a range of options to connect one-to-one or one-to-many with assistive technology users and results come back to you within two days.
Do I need to have an accessibility expert on my team to use Fable effectively?
No. The Fable team is here to act as an extension of your team through planning, delivery, and knowledge sharing. You can do the accessibility testing independently, we can do it together, or our experts can do it for you. Our community of testers is pre-recruited, trained to support enterprise organizations, and available on demand.
You also have the option to subscribe to Fable Upskill, giving your internal teams on-demand access to the knowledge and skills required to build truly inclusive products. Upskill includes video-based courses designed by our experts for your team and custom courses that incorporate your tools and systems to enable accessibility at scale.
What to consider when recruiting for accessibility research
In this section:
- Do I need to test with several hundred people with disabilities?
- Why should I avoid using screeners?
- Do I need to make sure I’m testing with every possible disability?
- When is it appropriate for people without disabilities to test using assistive technology?
- Why can’t I just have our employees with disabilities do testing or participate in research?
- Can I ask users with disabilities to volunteer to perform accessibility testing services?
Do I need to test with several hundred people with disabilities?
No, you don’t need to test with a large number of participants to uncover valuable insights in accessibility research. Like traditional UX research, small sample sizes can yield meaningful results when participants are carefully selected.
Testing with 5-10 participants with disabilities—particularly those who represent a range of abilities and use different assistive technologies—can help capture a variety of perspectives and identify critical barriers and areas for improvement.
Why should I avoid using screeners?
Screeners require people to answer a list of questions before being considered as research participants. The questions asked in a screener can inadvertently disqualify people with disabilities due to factors outside of their control (like job status). They also often assume a person with a disability can currently use the digital experience in question.
Because of the above, it’s possible that screeners don’t truly help you reach the participants who would lead you to the most valuable insights. Screeners often exclude people with disabilities even if that’s not their intention.
Do I need to make sure I’m testing with every possible disability?
It’s neither realistic nor necessary to test with every possible disability and type of assistive technology. Since accessibility testing is iterative, you can start off more focused and then broaden your research to include additional testers.
At the start, try to include a mix of disabilities (e.g., visual, auditory, mobility, cognitive) and assistive technologies.
You can begin by identifying the most common or critical use cases for your product and prioritize testing different assistive technologies based on how different the experience is likely to be with each. This allows you to avoid potential biases around where your team thinks the barriers are and ensures you don’t unintentionally leave out some assistive technologies entirely due to faulty assumptions.
When is it appropriate for people without disabilities to test using assistive technology?
There are a few use cases where it may be appropriate for people without disabilities to test your products using assistive technology.
- People without disabilities can perform QA testing and use assistive technologies to check for issues in your design. For example, a tester could check to see if a screen reader can read your alt text or whether voice control technology can recognize key actions.
- UX researchers can familiarize themselves with how different types of assistive technology work with products in order to more effectively facilitate inclusive research sessions.
Scenarios like these can help UX teams uncover basic problems and prepare for user research. However, you will drive the most meaningful results by testing with real users who rely on assistive technologies in their daily lives.
Why can’t I just have our employees with disabilities do testing or participate in research?
First and foremost, your employees with disabilities have key job responsibilities with your company. It’s not fair to ask them to do accessibility testing off the side of their desk. With their managers holding them accountable for meeting other goals and priorities, they may also rush through testing.
Your employees with disabilities are also accustomed to your products and workflows which can introduce familiarity bias. This bias can mask usability issues that unfamiliar users would more easily surface. In addition, your employees may edit or soften critical feedback if they worry it might impact their working relationships.
It’s also unlikely that your employees with disabilities represent the full spectrum of disabilities or assistive technology use cases you need to conduct thorough research. In contrast, Fable’s community of assistive technology users employ a wide variety of assistive technologies and 67% have been native users of their assistive technology for more than a decade. Our testers can provide up to 20+ unique configurations consisting of different combinations of browsers, assistive technologies, and operating systems. Fable community members are also pre-vetted, trained to test digital products at the enterprise level, and uniquely qualified to provide high-quality, rapid feedback.
Can I ask users with disabilities to volunteer to perform accessibility testing services?
People with disabilities deserve fair pay for their labor. If you don’t expect your employees to work for free, your testers should be held to the same standard. When people are appropriately compensated for their skill and expertise, they are more likely to take the work seriously and provide feedback that your team can use to make meaningful improvements to the accessibility of your products.
It’s also important for accessibility testers to have an appropriate level of experience with using assistive technologies. It’s also helpful if they are trained with the skills to communicate about their experiences with your products using clear, actionable language.
Fitting accessibility research in the product development cycle
In this section:
When is my product ready for accessibility testing?
You don’t have to have a fully-baked product to conduct accessibility testing. If you wait to test accessibility at the quality assurance stage, minor issues that could have been fixed with a single line of code may have grown into complex bugs.
Even if you don’t have a design file or working prototype, you can still collect valuable insights from people with disabilities. Discovery and generative research can help you define a problem more clearly. Open-ended user interviews with people using a range of assistive technologies can increase understanding of accessibility considerations. Use the insights collected to prevent issues before product build, saving remediation time down the line and practicing accessibility-centered design from the start.
Why does accessibility research and testing need to be an ongoing process?
With every new product version release, there’s a chance of unintentionally breaking the existing experience for assistive technology users. Ongoing testing gives you a tool to continually monitor your product accessibility and health. It also helps you to capture your team’s progress in building accessible products over time.
Companies like CVS Health have partnered with Fable to build ongoing user research with people with disabilities. According to Greg Weinstein, Senior Accessibility Designer and Inclusive Research Lead at CVS Health, this partnership has been “very important as one of the pieces of their inclusive design work.”
Accessibility means I have to remove features and create simpler interfaces, right?
Accessible does not equal scaled back or ugly. It’s not about creating overly simplistic experiences. In fact, in the past, this mindset led to sub-par experiences, like text-only interfaces and screen-reader detection.
The correct mindset to adopt is that accessible interfaces can (and should) be human, beautiful, and user-friendly. When digital products are built through this lens, it’s a win for all users – those with and without disabilities.
You can explore more myths around accessibility and design by checking out a conversation between Laila Coulton, Head of Design, Research, and Accessibility at Xero and Samuel Proulx, Accessibility Evangelist at Fable.
Doesn’t focusing on accessibility slow down innovation and development?
No. In fact, ignoring accessibility can be a drag on innovation because it forces teams to waste time building fixes after the fact.
“For every hour that a UX designer invests into accessibility pre-launch, we save up to four hours in engineering post-launch, not bug-fixing accessibility issues.”
– Dirk Ginader, Accessibility UX Engineering Lead at Google
There are plenty of examples of accessibility driving innovation and value for all users. For example, the keyboard evolved from the typewriter, which was designed to help a blind Italian countess write letters. And technologies like voice recognition, voice dictation, and computer control of devices were also born out of the needs of people with disabilities. Technologies like Alexa and Siri built on those advances, combining them into single systems that are used by all users today.
Evaluating our efforts
How can we measure the results of our accessibility research and testing?
Although measuring compliance is a first step, aligning your accessibility measurement to the business metrics your leadership cares about will help you demonstrate more meaningful impact. For example, you can show how accessibility research has impacted team efficiency by measuring factors like project velocity, code stability and even usability scores over time.
You can leverage Fable’s KPI framework to report on accessibility progress using data points that are meaningful to your organization. This framework is centered on KPIs that encompass the categories of People, Process, and Product.
- People – Do your teams possess the skills required to build accessible products? (e.g., measure how many weeks it takes team members complete critical accessibility training.)
- Process – How do your systems of working and tooling support accessible product development? (e.g., What portion of design system components have accessibility baked in?)
- Product – What’s the user experience of people with disabilities? (e.g., Can people using assistive technologies complete critical tasks in your product experience?)
