Accessibility

Accessibility statement

This statement applies to Riddle interactive content embeds: the quizzes, polls, forms and minigames your audience sees on your website or app. It does not cover the Riddle Creator. Riddle embeds are designed to meet level A and AA criteria of the Web Content Accessibility Guidelines (WCAG) 2.2, the international standard for accessibility of websites and applications.
Compliance Riddle embeds are partially conformant with WCAG 2.2 level AA. Partially conformant means that most of the content meets the criteria, but some parts do not yet. In October 2026 we fixed every issue confirmed in Axess Lab's latest re-test (see below). Some barriers remain, and we list them openly on this page.
Help and feedback

Have you encountered something that doesn't work? We'd be grateful for your feedback on how we can improve. Contact us via our support chat, by sending an email to hello@riddle.com, or by completing the form below and we'll make sure you get the help you need as soon as possible. We'll reply in the way you prefer.

Our support is open on weekdays from 09:00 to 17:00 CET, and we usually reply to accessibility requests within 2 business days.

Note that you have the option to file a complaint with the market surveillance agency of your country in case your issue is not resolved.
How we work with accessibility We fix all known accessibility issues as soon as possible. In the future, tooling and expert guidance will prevent the introduction of new accessibility barriers into the product. We commit to a third-party consultancy reviewing our products and new features before launch to ensure that new functionality is accessible and also works with the existing functionality. We provide ongoing accessibility training for our designers, developers, and project managers. In addition, we also consult people with disabilities in design processes. All of this is part of our ISO 27001 audited development process.
Our accessibility partner Since April 2025, we've partnered with Axess Lab, a leading accessibility consultancy. They reviewed our application in 2025, re-tested it against WCAG 2.2 AA in 2026 and continue to support us with our accessibility needs.

What we fixed in October 2026

Axess Lab re-tested sample polls, personality quizzes, forms, minigames, leaderboards and score predictors against WCAG 2.2 AA. We checked every finding against live Riddles and fixed all confirmed issues. The fixes apply to every Riddle that uses these blocks, so you don't need to change anything in your existing content.

Clear names for buttons and fields

  • The leaderboard reload and search buttons have names, and the search field has a label instead of just a placeholder.
  • Every Minesweeper cell and the reset button have names.
  • The Swiper buttons say what they do instead of reading out "00 %".
  • Upvote buttons name the choice they vote for and announce whether they are pressed.
  • Star ratings name the item being rated.
  • In the Score Predictor, each score field names its team, and the +/- steppers are real buttons.
  • In forms, Yes/No answers, the terms checkbox and the privacy checkbox read their own label instead of the question. The date field (DD/MM/YYYY) is grouped under its question.

Answer choices that read as one clear control

  • Image credits are no longer read out as part of the answer and no longer sit inside the answer button. This applies to all blocks with images, including This or That.
  • The "Other" text field in single choice questions is no longer nested inside the answer and no longer grabs focus on its own.
  • Headings and other elements inside answer choices (for example in personality quizzes and multiple choice questions) no longer break how screen readers read the choice.

Announcements for screen reader users

  • The time selector announces the new value when you press increase or decrease.
  • Wheel of Fortune announces the result after the spin.
  • Crossword announces letters that were revealed.
  • Quiz result stats read vote counts with their unit ("1 vote" instead of "1").
  • Guess It uses the correct singular ("1 guess remaining").
  • The selection counter no longer announces negative numbers.
  • Announcements from a previous page no longer stay behind when you move on.

Errors and forms

  • Submitting a form with empty required fields shows a visible error message and announces it.
  • Multiple choice instructions state the actual selection limit instead of "Select all that apply", and the error message stays visible instead of disappearing after two seconds.
  • Required fields are marked consistently, including rating and text questions.
  • Name, email, phone and URL fields (also in the quiz leaderboard form) tell the browser what they expect, so autofill works.
  • Error dialogs are real dialogs: focus moves into the dialog and the page behind it is blocked.
  • The time picker is fully translated.

Small screens, zoom and contrast

  • Wheel of Fortune fits screens down to 320px wide. On narrow screens a text legend lists all segments, and on wider screens the legend is available to screen readers.
  • The Crossword toolbar fits narrow screens, so the Check button stays reachable.
  • The Crossword grid uses a correct row and cell structure, and blocked cells are announced as unavailable.
  • The Minesweeper Streak mode badge meets the 4.5:1 contrast ratio.

Remaining barriers and how to avoid them

Most of Riddle's blocks are built to meet WCAG 2.2 AA. The few block types that rely on vision are named below, and with a custom creator role (part of our Enterprise Plan) you can make sure your team can't use them. Whether a Riddle is fully accessible also depends on how it is set up. These are the barriers that remain and what you can do about them.

Images and colors

  • Blind users and users with low vision can encounter images without a descriptive text alternative when the creator didn't add one.
  • Unless one of our default palettes is selected and not altered, contrasts of some UI elements and texts are insufficient, affecting users with low vision or color vision deficiencies. To ensure readability, select the "Atkinson Hyperlegible" font type (developed by the Braille Institute).

Block types that rely on vision

The following block types cannot be made accessible. Keyboard and screen reader users are unable to fully interact with them, and some of their information is only available to users who can see the screen. Please refrain from using them if your Riddle needs to fully conform with WCAG 2.2 AA.

  1. Spot the difference
  2. Tap & Find
  3. Interactive Graphic

Features to avoid

The following features cannot be made accessible. Please refrain from using them if your Riddle needs to fully conform with WCAG 2.2 AA:

  • Order-it: reshuffling choices after each submission. Keep the order buttons switched on.
  • Quiz ⇒ Display visuals briefly
  • Timers
  • Auto-Advance. Automatically moving to the next question can be disorienting for users with cognitive disabilities. The option is off by default and has to be enabled.

How we assessed accessibility

This statement is based on a third-party evaluation by Axess Lab: a full audit in 2025 and a re-test against WCAG 2.2 AA, with the report released on 2026-04-26. Axess Lab tested sample quizzes, personality quizzes, polls, forms, minigames, leaderboards and score predictors with different screen readers, other assistive technologies and automated testing tools. We verified every finding against live sample Riddles on 2026-09-01 and fixed all confirmed issues in October 2026.

Accessibility is one part of how we build trust. Riddle is also ISO 27001 certified and meets strict data privacy standards.

Last updated: 2026-10-19