Accessibility

Building accessible quizzes with FluoTest

Quizzes built with FluoTest are designed to work with keyboards, screen readers, and other assistive technology, on the free plan and every paid plan alike.

FluoTest does not hold an official WCAG or ADA certification yet. We design and build with accessibility best practices in mind and keep improving, but we can't guarantee full compliance for every use case. If accessibility is critical for your organization, test your specific quiz with your target assistive technology before publishing.

How we approach accessibility

When we build or change a question type, we follow WCAG's form guidelines as our reference: someone using only a keyboard or a screen reader should be able to complete the quiz without hitting a wall. Most of FluoTest's public quiz is built on standard, semantic HTML, which gives us a solid accessible foundation to start from. When we find gaps — from user reports, audits, or our own testing — we fix them.

What works today

Keyboard navigation

  • Tab through every question, option, and button in a quiz — start, answer, go back, and submit — without touching a mouse
  • Every choice, star rating, and yes/no button is a real focusable, activatable control
  • Moving to the next or previous question sends keyboard focus to the new question automatically
  • Date pickers are fully keyboard-reachable

Screen readers

  • Every answer field is programmatically linked to its question text, so screen readers announce what's being asked
  • Multiple-choice, multi-select, yes/no, and star-rating questions are announced as a group with the current selection, not as unlabeled buttons
  • The progress bar has an accessible label announcing the current section and percentage complete
  • Validation errors and the "calculating your results" state are announced automatically as they appear
  • Decorative question images are marked as such, so they aren't read twice alongside the question text

Improvements shipped in 2026

  • Labelled form controls — every input, textarea, range slider, date picker, and file upload is tied to its question via aria-labelledby
  • Radiogroup and checkbox roles with live selection state on all choice-style questions
  • Automatic focus movement between question steps for keyboard and screen-reader users
  • An accessible, announced progress indicator
  • Live-region announcements for results, errors, and async loading states
  • Corrected heading structure (quiz title, section title, question title) so screen-reader users can navigate by heading
  • A visible, translated hint explaining why the Next button is disabled when required questions are unanswered

Known limitations

  • Choice-style questions (multiple choice, yes/no, star rating) don't yet support left/right arrow-key navigation between options — each option is still reachable one at a time with Tab
  • We haven't yet run a full color-contrast audit across every score-tier color
  • This page covers the public, respondent-facing quiz. The quiz editor/dashboard used by quiz creators hasn't had a dedicated accessibility pass yet

We're a small team and accessibility is an ongoing effort, not a checkbox. If you hit something that doesn't work for you, let us know at [email protected].

Tips for creating accessible quizzes

  • Write clear question text — don't rely on placeholder text alone as a label for open-ended questions
  • Don't rely on color alone — score tiers use color, so make sure the tier label and message carry the meaning too
  • Keep quizzes focused — fewer questions mean less friction, especially for respondents with cognitive or motor disabilities
  • Give sections a clear, descriptive title so respondents always know what part of the quiz they're in
  • Test your quiz with a keyboard before sharing it widely

Was this helpful?