Accessible survey author checklist

This checklist focuses only on things that are specifically relevant to survey accessibility.

It is designed for HR teams, CX teams, EX teams, communications teams and researchers who want to create surveys that are easier to complete for people using keyboards, screen readers, mobile devices and other assistive technologies.

If you are using Questback’s new Answer Module, this checklist helps you get the most out of a respondent experience designed to be WCAG 2.2 AA aligned.

For the formal product scope, read our WCAG 2.2 accessibility statement

Accessible survey author checklist

1. Make sure the survey can be completed with a keyboard

A respondent should be able to move through the survey, select answers, activate buttons and submit the survey using only a keyboard.

Check that:

• all interactive elements can be reached by keyboard
• the tab order is logical
• buttons, inputs and controls can be activated without a mouse
• there are no keyboard traps

2. Check that keyboard focus is always visible

Users navigating by keyboard need to be able to see where they are at all times.

Check that:

• the current focus state is clearly visible
• focus is not hidden by sticky headers, banners or overlays
• focus remains easy to track across pages, validation states and dialogs

3. Avoid drag-only interactions

If a question includes ranking, sorting or prioritization, respondents should not be forced to use drag-and-drop only.

Check that:

• ranking questions have a non-drag alternative
• the alternative can be completed by keyboard
• the alternative works clearly on mobile devices as well

4. Make answer controls large enough for mobile use

Small controls can be difficult for many users, especially on touch devices.

Check that:

• radio buttons, checkboxes and scale points are easy to tap
• buttons are not too small or too close together
• interactive elements are usable on real mobile devices, not just in preview

5. Make instructions available where they are needed

Users should be able to understand what to do without searching visually around the page.

Check that:

• instructions are placed close to the relevant question or field
• required format information is shown before input, not only after an error
• respondents do not have to rely on layout or guesswork to understand the task

6. Do not rely on color alone

Important information must still be understandable for users who do not perceive color differences reliably.

Check that:

• required fields are not marked by color alone
• warnings and error states are not communicated only through red text or borders
• status messages remain understandable without color cues

7. Review matrix and grid questions carefully

Large matrices can create accessibility barriers, especially for keyboard users, screen reader users and mobile respondents.

Check that:

• matrix questions are only used when truly necessary
• they can be navigated without using a mouse
• they are still readable on smaller screens
• the row and column context remains clear

8. Check survey flow elements such as progress, dialogs and confirmations

Accessibility problems often appear in the flow around the questions, not only in the questions themselves.

Check that:

• progress indicators are understandable
• modal dialogs or overlays can be used by keyboard
• confirmation messages are clear and easy to notice
• the submission state is obvious when the survey is completed

Final accessibility pre-launch check

Before publishing, confirm the following:

• Can the full survey be completed using only a keyboard?
• Is focus always visible?
• Are question interactions usable without drag-only actions?
• Are controls easy to tap on mobile devices?
• Are instructions available where users need them?
• Are required fields, warnings and errors understandable without color alone?
• Are matrix questions still usable for keyboard and screen reader users?
• Does the full flow work accessibly from first page to submission?

Accessibility is about reducing barriers

Survey accessibility is not just about meeting a requirement. It is about removing barriers that make it harder for people to participate.

The more accessible the respondent experience is, the more people can complete your survey with confidence.

To learn more about Questback’s approach, read our WCAG 2.2 accessibility statement