Compatibility testing

Illustration: five users

Test across different devices and browsers. Five testers will complete a task while identifying accessibility issues.

What is a Compatibility Test and when to use one?

A Compatibility Test allows you to test compatibility and accessibility on important user journeys within your digital properties across assistive technologies, devices and browsers. It’s like engaging a diverse team of QA analysts, each of whom is uniquely qualified to support your accessibility efforts. 

You should create a Compatibility Test if you are looking to: 

  • Test specific tasks and flows on a website, mobile or software application

  • Gather detailed feedback from multiple assistive technology users

  • Identify compatibility issues with specific browsers, devices and assistive technologies

  • Get an overall sense of the user experience and if it’s working well for end users

  • Validate remediation efforts to a previously tested Compatibility Test

 How to create a Compatibility Test?

Like any request, start by selecting ‘Create’ from the Fable platform. Select an existing Project, or create a new one – every request must be assigned to a Project. Select ‘Compatibility Test’ and you’ll be on your way!

To request a Compatibility Test you’ll need information on the the following:

  • Testing audience: Who do you want feedback from? Choose from a preset audience, or create your own custom audience if you have a specific testing matrix that you use.
    • Mixed users includes three screen reader, one alternative navigation, and one screen magnification user.
    • Custom audience allows you to specify all five of your tester configurations, including AT type, device, browser and OS. 
  • Testing subject: When and why would you like to meet? This includes date, time and a description of your goals/objectives.
  • Credentials and access: How will your participant access your product? This includes any special instructions or existing environments.
  • User journey: What will your participant be interacting with? This includes proving any URLs you’ll want the participant to review.

D