Accessible surveys guide: a WCAG-aligned checklist
An accessible survey can be completed by people using screen readers, keyboard-only navigation, screen magnification, or with low vision, motor, or cognitive differences. The practical essentials, aligned with WCAG: sufficient color contrast, a visible label tied to every input, full keyboard operability, a logical reading and focus order, clear error messages, and plain language. Accessibility isn't only ethical and often legally expected — it also widens your sample, because excluded respondents are missing data.
This guide is practical, not legal advice. If your survey must meet a specific legal standard (such as ADA, Section 508, or the EU's accessibility requirements), confirm the details with a qualified accessibility or legal professional. What follows is a working checklist aligned to the Web Content Accessibility Guidelines (WCAG).
Why accessible surveys matter
When a survey can't be completed with a screen reader or a keyboard, the people affected don't just have a worse experience — they drop out, and their perspectives vanish from your results. That's both an exclusion problem and a data-quality problem: you're systematically missing a segment of your audience. Designing accessibly widens who can respond and makes your findings more representative.
Color and contrast
- Meet WCAG contrast ratios: at least 4.5:1 for normal text and 3:1 for large text against its background
- Don't rely on color alone to convey meaning — pair required-field red with an asterisk and the word 'required', and pair error states with text
- Make sure focus indicators and selected states are visible to people with low vision
- Test your palette with a contrast checker, including any custom theme colors
Labels and inputs
- Give every input a visible, persistent label — placeholder text alone is not a label and disappears on focus
- Programmatically associate each label with its field so screen readers announce it
- Group related options (like a set of radio buttons) so assistive tech announces them as one question
- Provide clear instructions before the field, not buried after it
Keyboard and focus order
- Make every control reachable and operable with the keyboard alone — no mouse-only interactions
- Ensure a logical focus order that follows the visual reading order of the page
- Keep a clearly visible focus indicator so keyboard users always know where they are
- Avoid keyboard traps where focus enters a control and can't leave
Screen readers
- Use real form semantics so screen readers announce field type, label, and required state
- Provide text alternatives for any images that carry meaning (and mark decorative ones as decorative)
- Announce progress and step changes so screen-reader users know where they are in a multi-step survey
- Make error messages perceivable to assistive tech, not just a color change
Errors and validation
- Write specific error text ('Enter a valid email address'), not just 'Invalid'
- Identify which field has the error in text, not only by color or position
- Move focus to the first error so keyboard and screen-reader users find it immediately
- Don't clear a respondent's other answers when one field fails validation
Plain language and cognitive load
- Use short, common words and one idea per question
- Avoid double-barreled questions, double negatives, and jargon
- Keep the survey short and show progress to reduce cognitive load
- Don't impose tight time limits unless they're essential, and warn people if you do
Run a five-minute keyboard test on any survey before launch: put the mouse aside and complete the whole thing using only Tab, Shift+Tab, arrow keys, Space, and Enter. If you can't reach a field, can't tell where focus is, or get stuck in a control, neither can a keyboard or screen-reader user. It catches the majority of real accessibility blockers fast.
How to actually test accessibility
- 1Do the keyboard-only run-through described above
- 2Check every color combination, including custom themes, against WCAG contrast ratios
- 3Turn on a screen reader and complete the survey listening, not looking
- 4Zoom the browser to 200% and confirm nothing is cut off or overlapping
- 5Read each question aloud and cut anything that needs re-reading to understand
Your tooling matters too: if the platform outputs proper labels, keyboard-operable controls, and responsive layouts, you start most of the way there. Formkii surveys are mobile-responsive and use standard form controls, and you control theme colors — which means you're responsible for choosing accessible contrast and writing plain-language questions. Whatever tool you use, run the keyboard and contrast checks on your own live survey before sharing it.
Frequently asked questions
What makes a survey accessible?
An accessible survey can be completed with a screen reader, keyboard, or magnification by people with a range of vision, motor, and cognitive differences. In practice that means sufficient color contrast, a visible label tied to every input, full keyboard operability, a logical focus order, clear text error messages, and plain-language questions.
What contrast ratio do surveys need?
WCAG recommends a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text against its background. Check any custom theme colors with a contrast checker, and never rely on color alone to signal meaning such as required fields or errors — pair it with text.
How do I test if my survey is accessible?
Start with a keyboard-only run-through: complete the survey using only Tab, arrow keys, Space, and Enter. Then check color contrast against WCAG ratios, complete the survey with a screen reader turned on, and zoom to 200% to confirm nothing breaks. These four checks catch most common blockers.
Are accessible surveys legally required?
It depends on your jurisdiction and context — standards like the ADA, Section 508, and the EU accessibility rules may apply. This guide is practical, not legal advice; confirm your specific obligations with a qualified accessibility or legal professional. Regardless of the law, accessible surveys widen your sample and improve data quality.