Creating accessible surveys is essential for reaching all audiences, including those with diverse functional needs. Our goal is to deliver an inclusive survey experience by design—so you can ask everyone, everywhere.
Accessibility features
We are committed to continuous improvement and are actively working toward compliance with the Web Content Accessibility Guidelines (WCAG) 2.1, Levels A and AA, as well as relevant sections of U.S. Section 508 of the Rehabilitation Act.
Currently, our survey platform supports:
Compatibility with major screen readers (e.g., VoiceOver, NVDA, TalkBack)
Smooth zoom functionality up to 400%
Full keyboard navigation without requiring a mouse
Best Practices for Building Accessible Surveys
To ensure your survey is accessible, we recommend the following design practices:
Add alternative text (alt text) to all images to support screen reader users.
Use only accessible question types—those that work well with assistive technologies.
Avoid blinking or rapidly changing GIFs. If used, ensure they meet WCAG criteria for readability and timing.
Avoid horizontal layouts for Net Promoter Score (NPS) questions on mobile, as they may be difficult to navigate.
Avoid adding labels such as "Not likely" and "Very likely" for NPS, as they are not visible for screen readers
Use Survey theme colors that meet the 4.5:1 contrast ratio requirement
Limitations and Known Accessibility Issues
The following elements currently have limited accessibility support, particularly in mobile or specific environments:
Date questions (in mobile versions of web surveys)
Thank You screens
Introductions
Disclaimers
We are actively exploring improvements in these areas. Below you will find the full overview of the WCAG criteria.
Survey Navigation
Shortcut | Action |
Tab | Navigating through the survey using keyboard focus (moves between questions and answer options) |
Enter | Selecting or submitting an answer |
Arrow Keys | Navigating between options in dropdowns and ranking questions |
WCAG 2.1 Compliance Review – Survey Platform
WCAG Criterion | Level | Status | Notes |
1.1.1 Non-text Content | A | ✅ Fully supported | Alt text for images is required and encouraged. |
1.2.1 Audio-only and Video-only (Prerecorded) | A | 🚫 Not applicable | Surveys do not typically contain audio/video content. |
1.2.2 Captions (Prerecorded) | A | 🚫 Not applicable | No video in standard surveys. |
1.3.1 Info and Relationships | A | ✅ Fully supported | Screen reader compatibility and semantic elements included. |
1.3.2 Meaningful Sequence | A | ✅ Fully supported | Linear navigation through keyboard is available. |
1.3.3 Sensory Characteristics | A | ✅ Fully supported | Instructions do not rely solely on visual/sound cues. |
1.4.1 Use of Color | A | ✅ Fully supported | Color is not the only means of conveying information. |
1.4.3 Contrast (Minimum) | AA | 🔲 Partially supported | Requires validation of survey themes and fonts. |
1.4.4 Resize Text | AA | ✅ Fully supported | Zoom supported up to 400% without loss of content. |
1.4.5 Images of Text | AA | ✅ Fully supported | Avoids use of images of text in surveys. |
1.4.10 Reflow | AA | ✅ Fully supported | Content adapts to different screen sizes. |
1.4.11 Non-text Contrast | AA | 🔲 Partially supported | Needs confirmation on UI elements contrast. |
2.1.1 Keyboard | A | ✅ Fully supported | All functionality operable via keyboard. |
2.1.2 No Keyboard Trap | A | ✅ Fully supported | Users can navigate freely using keyboard only. |
2.2.2 Pause, Stop, Hide | A | ✅ Fully supported | Blinking content discouraged, GIFs reviewed. |
2.3.1 Three Flashes or Below Threshold | A | ✅ Fully supported | Animated content follows WCAG guidance. |
2.4.3 Focus Order | A | ✅ Fully supported | Logical navigation sequence preserved. |
2.4.6 Headings and Labels | AA | 🔲 Partially supported | Thank you/introduction screens need improvement. |
2.4.7 Focus Visible | AA | ✅ Fully supported | Keyboard focus is visually apparent. |
3.1.1 Language of Page | A | ✅ Fully supported | Default language declared in HTML structure. |
3.2.1 On Focus | A | ✅ Fully supported | Focus does not trigger unexpected changes. |
3.3.1 Error Identification | A | 🔲 Partially supported | Some question errors are not fully screen reader accessible. |
3.3.2 Labels or Instructions | A | ✅ Fully supported | Labels used for form elements. |
4.1.2 Name, Role, Value | A | ✅ Fully supported | Form elements exposed to assistive tech correctly. |
📞 If you have any questions or need further assistance, feel free to reach out to our team via chat or email: support@survicate.com