Accessibility

Last updated: September 2026

SparkleQuiz (published by Quentin Bastos) wants as many people as possible to play, create quizzes and take part in the community, whatever their abilities. This page says what we aim for, what is in place, what is not yet, and how to tell us.

What we aim for

We aim for the WCAG 2.1 level AA recommendations, on the web as well as in the Android and iOS apps. This is a goal, not an achieved state: the site has not been through an independent conformance audit, so we do not present it as conformant. Every new feature is checked with an automated analysis tool (axe) and by keyboard before release, and a full internal audit was carried out in September 2026.

What is in place

Resizable text that follows the system font-size settings.
Light and dark modes; body text, links and buttons aim for at least 4.5:1 contrast.
Keyboard navigation with a visible focus indicator on interactive elements, and a "Skip to content" link.
Semantic structure: a single main landmark per page, ordered headings, labels tied to form fields, explicit button names.
Decorative illustrations (including the mascot) are hidden from screen readers; meaningful images carry alternative text.
Touch targets of at least 44 px on primary actions, and visual feedback on every action.
Animations are reduced or removed when the system asks for less motion ("Reduce motion").
Modal dialogs keep focus inside, close on Escape and return focus to where it came from.

Known non-conformities

We would rather name them than hide them. As of this page:

Real-time matches: the countdown and the automatic move to the next question cannot be paused; live ranking changes are not all announced to screen readers.
Quiz editor: questions are reordered with arrow buttons, without an accessible drag-and-drop; some fields of the advanced editor do not yet have an error description linked to the field.
Community-created content: images added by quiz authors do not always carry alternative text, and we cannot guarantee it on their behalf.
Maps and long lists: the chapter map and some lists are virtualised; tab navigation skips items that are off-screen.
Remaining contrast issues: a few secondary texts (small print, disabled states) are still below 4.5:1; they are listed and fixed release by release.
Mobile screen readers: VoiceOver and TalkBack compatibility is verified on the main journeys (sign-in, solo map, settings), not yet across the whole app.

Assistive technologies

We work with screen readers (VoiceOver on iOS, TalkBack on Android, NVDA and VoiceOver on desktop), keyboard-only navigation and the system magnification tools. If a specific combination causes you trouble, tell us: that is what decides the order of the fixes.

Tell us

If you run into an accessibility barrier, write to [email protected] with "Accessibility" as the subject, the page concerned, your device and the assistive technology you use. We answer every report, normally within a week, and we say whether and when the issue will be fixed.