Custom audiences

You can create a custom audience for a Compatibility Test if you are looking to test with specific assistive technologies, device types, operating systems and/or browsers. The two default audiences available to you are:

  1. Mixed users (three screen readers, one screen magnifier and one alternative navigation user)
  2. Screen readers users (five screen reader users)

How to set up custom audiences

You can set up a custom audience either from your account settings or while creating a Compatibility Test.

From settings:

  1. In the main navigation, select your name to open the dropdown menu.
  2. Choose Settings from the menu.
  3. Select Custom audiences and then click Create audience.

From a Compatibility Test:

  1. Select New Request.
  2. Choose the Request type Compatibility Test, assign it to a project, and click Next.
  3. Under Audience, select the Custom audience option.
  4. Select Create custom audience.

How to add a custom audience to a Compatibility Test

Once you’ve created your custom audience then you can add it to your Compatibility Test.

Steps to add a custom audience:

  1. Select New Request.
  2. Choose the Request type Compatibility Test, assign it to a project, and click Next.
  3. Under Audience, select the Custom audience option.
  4. Select your custom audience from the list.
Interface for selecting a custom audience. At the top, a selected radio button labeled 'Custom audience' is shown. Below it, there is a button labeled '+ Create custom audience,' followed by three radio button options: 'Mixed users - iOS,' 'Explore Fable Audience - Screen Readers,' and 'Explore Fable - Compatibility Test Audience for iOS.

Tips for creating a custom audience

Use a descriptive name

Choose a name that clearly reflects the purpose of your audience. For example:

  • “VoiceOver on iOS”
  • “Screen Reader Compatibility: NVDA + Chrome”
  • “Mobile Browser Testing: Safari + Android”

A clear name will make it easier to identify and reuse the audience across projects.

Add audience interface featuring a text input field labeled 'Custom audience name' at the top. Below it are expandable sections for 'Tester 1 config,' 'Tester 2 config,' 'Tester 3 config,' 'Tester 4 config,' and 'Tester 5 config.'

Tester customization

Each tester in your custom audience can be configured with the following attributes:

  • Assistive Tech Type: Specify screen readers, magnification tools, or other assistive devices. This is the only required attribute.
  • Device Type: Choose between mobile devices, laptops and desktops.
  • Operating System: Specify platforms like Windows, macOS, iOS, or Android.
  • Assistive Technology: Add even more customization to the assistive technology by selecting the specific technology type.
    • For example, if you want to test with a user who gives voice commands and a user who uses a switch system to check for barriers for both types of alternative navigation, you can do that here.
  • Browser: Combine browser-specific testing with assistive technology to test compatibility (e.g., NVDA with Firefox or JAWS with Edge).
    • Be careful about which combinations you choose as they might expose assistive technology compatibility issues rather than accessibility barriers. For example, VoiceOver works best with Safari.
Tester 1 configuration settings with dropdown menus for Assistive Tech Type (required), Device type, Operating system, Assistive Technology, and Browser. All dropdowns are set to 'No preference' except for Assistive Tech Type, which is labeled 'Select'.

Support and troubleshooting

If you have any questions about setting up recurring requests or are facing any issues, email support@makeitfable.com.