Accessibility Statement

1. Our Commitment

Kwokka is a small, single-author website. Despite that — and partly because of it — we believe accessibility is fundamental, not optional. The quiz and the eighteen thinker-type pages are intended for the broadest possible audience, including front-line professionals, students, and anyone simply curious about their own moral and political instincts. People come to a philosophy quiz with all sorts of bodies, devices, and contexts. We want all of them to be able to participate.

This statement explains what we have done so far, what we know is not yet right, and how to tell us about anything we have missed.

2. The Standard We Aim For

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.1 at conformance level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is the standard adopted by the UK Government Digital Service for public-sector websites and is widely treated as the baseline for private-sector good practice in the United Kingdom and the European Union.

Where WCAG 2.2 introduces additional success criteria, we attempt to meet those too on a best-effort basis, but our formal conformance target is 2.1 AA.

3. Compliance Status

This website is partially compliant with WCAG 2.1 AA.

“Partially compliant” means we have implemented the majority of the success criteria, but we are aware of areas where we do not yet fully conform. Those are listed under Known Issues below. We have not yet commissioned an external accessibility audit; assessment to date is based on internal testing and automated tooling.

4. What We’ve Done

Across the site, we have:

• Used semantic HTML — landmarks, headings, lists, and form elements are marked up with their proper roles so that screen readers and assistive technology can navigate the page structure;
• Provided text alternatives — all meaningful images, icons, and illustrations have descriptive alt attributes, and decorative images use empty alt="" so they are correctly skipped;
• Made the site keyboard-navigable — all interactive elements (the navbar, mobile drawer, dropdowns, language menu, quiz controls, share buttons) can be reached and operated using only a keyboard;
• Used focus indicators — visible outlines appear on focused elements so keyboard users can see where they are on the page;
• Respected user motion preferences — non-essential animations on the landing page and quiz transitions are reduced when the visitor’s operating system requests prefers-reduced-motion;
• Avoided colour as the only indicator — quiz answers, footer links, and selection states use text labels and shape changes alongside colour;
• Allowed text resizing — the layout reflows cleanly when text is resized up to 200%, and the page does not require horizontal scrolling at standard zoom levels;
• Set the document language — lang is declared on the root element so screen readers select the correct pronunciation engine;
• Provided a skip link or landmark structure so that keyboard users can move past the navigation directly to the main content;
• Used sufficient colour contrast in the primary brand palette — parchment background with dark warm-grey body text, gold accents reserved for headings and small UI flourishes rather than body copy.

5. Known Issues

The following items are known not to fully meet WCAG 2.1 AA. We will be addressing them in priority order.

• Quiz Likert sliders. The five-point agreement scale is operable by mouse, touch, and keyboard, but the screen-reader announcement of value changes may not be fully descriptive on every assistive-technology and browser combination. We are working on richer ARIA labelling for each option.
• Decorative animations. The gentle floating animation on the landing-page statue and certain hover effects on the navbar may exceed the strict prefers-reduced-motion threshold in edge cases. Reducing them further is on the to-do list.
• Colour contrast on subtle UI flourishes. A small number of decorative flourishes (for example, faint background sparkles, the muted “scroll down to begin” hint colour) sit close to but not always above the 4.5:1 ratio required for normal text under WCAG 2.1 AA. They are non-essential and convey no information that is not also conveyed elsewhere, but we are tightening them.
• External components. Some third-party components (the Complianz cookie banner, the Weglot language switcher, the Hotjar opt-out widget where it appears) are styled by their respective vendors. Their accessibility may differ from ours; see Third-Party Content below.
• Mobile reading order. On the quiz results page, the share buttons and “Take quiz again” link sit above the type description in source order on mobile. For a screen-reader user this presents the call-to-action before the explanation. We intend to reorder this.
• Error messages. Newsletter sign-up and quiz-submission error messages are visible but do not always announce themselves to screen readers via aria-live. Users relying on assistive technology may need to refocus the form to discover the error.

If you encounter an issue not on this list, please report it to us — we will add it.

6. Third-Party Content

Parts of the site are rendered by third-party services. We do not control their markup or behaviour, and their conformance with WCAG 2.1 AA is determined by them, not by us. The third-party components currently in use are:

• Complianz — cookie consent banner;
• Weglot — site translation;
• Google reCAPTCHA — anti-spam on the newsletter form;
• Hotjar — behavioural analytics, including its own opt-out controls when shown;
• Embedded social-media share buttons — rendered with the providers’ own markup.

If a third-party component is causing an accessibility problem, please tell us anyway. We will either work around it ourselves or escalate to the vendor.

7. How to Report a Problem

If you find anything on the site that is hard or impossible to use because of an accessibility issue, please email us at adamkesterson@kwokka.net. Please include, where you can:

• The page or feature that didn’t work (a URL or short description);
• What you were trying to do;
• What happened (or didn’t happen);
• The browser, device, and assistive technology you were using.

We aim to respond to accessibility reports within five working days, and to fix issues that have a clear remedy within thirty days. For complex issues we may need longer; we will tell you if so.

8. Enforcement Procedure

If you are not satisfied with our response, the body responsible for enforcing accessibility legislation in the United Kingdom for private-sector services is the Equality and Human Rights Commission (EHRC). Under the Equality Act 2010, service providers in the UK have a duty to make reasonable adjustments for disabled users. You may contact the EHRC’s Equality Advisory and Support Service for advice.

If you are based in the European Union, your national equivalent regulator may be appropriate.

9. How We Tested

This site has been assessed using a combination of:

• Automated tools — including Lighthouse (Google Chrome’s built-in audit), axe DevTools, and WAVE, run against the landing page, quiz pages, results pages, and the legal pages;
• Manual keyboard-only testing — navigating the entire site using only the Tab, Shift+Tab, Enter, Space, Escape, and arrow keys;
• Manual screen-reader spot-checks — using VoiceOver on macOS and NVDA on Windows for representative pages;
• Browser zoom testing — verifying that the layout still reads at 200% and 400% zoom in modern browsers;
• Reduced-motion testing — toggling the operating-system preference and confirming that non-essential animations are suppressed.

The site has not yet been audited by an independent third party against the formal WCAG 2.1 AA test methodology. When we commission such an audit, we will update this statement to record the result.

10. What We’re Doing to Improve Accessibility

Accessibility work is ongoing. Concrete commitments:

• Address the items in Known Issues in priority order, starting with the Likert-slider screen-reader experience;
• Treat any new feature as not-shipped until it has been keyboard- and screen-reader-tested;
• Re-run the Lighthouse and axe automated tests after every significant deployment;
• Review this statement at least every twelve months, or sooner if the site or the standards change.

11. Contact

Questions about this statement, or about the accessibility of the Site generally, can be sent to:

Adam Kesterson
Kwokka
Email: adamkesterson@kwokka.net
Location: Staffordshire, United Kingdom

This statement was prepared on 28 April 2026.