for everyone, properly

Accessibility

Last updated 15 September 2026

Kwokka is meant to be usable by everyone, whatever device, assistive technology, or way of reading you bring. The aim is WCAG 2.1 level AA, and where the site falls short we would rather hear about it than guess.

What is in place

• The whole site works by keyboard: every quiz answer, menu, and the results-page contents can be reached and operated without a mouse, with visible focus outlines.
• A Skip to content link is the first thing you reach with the Tab key on every page, and it moves focus into the main landmark.
• Reduced-motion preferences are honoured: with reduce motion set in your system, decorative animation and movement effects switch off or calm down, including the page fade-in and the About page’s sparkles.
• Headings, landmarks and lists are semantic, so screen readers get a real structure to navigate rather than a soup of styled text.
• Images that carry meaning have text alternatives; purely decorative ones are hidden from assistive technology.
• Text and interface colours are chosen for contrast against the parchment background, and text resizes with your browser settings without breaking the layout.
• Text boxes grow rather than clip when the site is machine-translated into a language whose words run longer than the English.
• The animated logo is decorative and silent, and is hidden from assistive technology entirely.
• Sound effects are off until you turn them on, and the preference is remembered.

Known limitations, honestly

• The results pages are long and content-rich; the side Contents menu exists precisely to make them navigable, and we keep working on the reading order.
• Some decorative flourishes (the landing statue scene among them) are visual only; nothing you need is carried by them alone.
• Open-data sections on results pages pull from outside sources whose own accessibility we cannot control; we prune the ones that behave badly.

Tell us what is broken

If anything on Kwokka is hard or impossible for you to use, that is a bug, and we mean it: email adamkesterson@kwokka.net with the page and what happened, and it goes on the fix list. Plain descriptions are plenty; no technical vocabulary required.

How this statement is kept

This page is reviewed whenever the site changes materially, and the date above moves when it does.