Accessibility

What we aim for

This website aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. This page is not a certificate and not a claim that the site conforms. It says what was built and what was tested, so you can judge for yourself.

How it is checked

The site has an automated test that runs in a browser. It checks:

• every page against the axe-core rules for WCAG 2.2 levels A and AA, at a desktop width and at a phone width, and again with the menu open, an answer chosen, a search running and each form showing its errors, its prepared email and its confirmation;
• the keyboard: the first press of Tab reaches a visible “Skip to content” link, a focused link shows an outline, Escape closes the phone menu and returns focus to its button, and Tab reaches the bar at the foot of a phone screen straight after the header;
• at 320 and 360 pixels wide, that no page scrolls sideways and that no button, field or stand-alone link is smaller than 24 pixels (links inside a line of text are not measured);
• that every page has one main heading and skips no heading level, that every link, button and disclosure has a name, and that every disclosure opens and closes;
• with JavaScript off, the home, organisers, pilot, news and questions pages; with reduced motion, the home page, the phone menu, the fit check and a form being sent; in forced colours, the fit check, the topic chips on the questions page, the edge of a card and the phone menu.

The test runs in Chromium; the phone and navigation checks also run in Firefox and WebKit. It last passed in full on 1 October 2026. On the same day every page was also checked at 320, 375, 768 and 1280 pixels wide for its headings, sideways scrolling and the same axe-core rules.

Automated rules find only part of what can go wrong. A pass means those rules found nothing, not that every barrier is gone.

What the site does

• Skip link. The first Tab stop on every page jumps to the content.
• Visible focus. Whatever has keyboard focus shows an outline.
• Reduced motion. If your device asks for less motion, animations stop and content appears at once.
• Without JavaScript. Pages are plain HTML. The menu, the topic filter and every answer still open, and the forms hand your message to your email app. The search on the questions page needs JavaScript, so it is not shown without it. The fit check on the organisers page needs it too: without it there is no verdict, and the request form opens with your answers still to choose.
• Zoom and small screens. Text can be enlarged in the browser, and pages reflow to a screen 320 pixels wide.
• Forced colours. In a Windows contrast theme the site takes your colours, and cards, fields and selected items keep an edge.
• No time limits. Nothing on the site expires while you read or type.

Known limits

• Screenshots of the app are images. Each has a text description, but the words inside the picture cannot be read out, enlarged as text or translated.
• On small screens the row of five screenshots on the home page scrolls sideways. It can be reached and scrolled with the keyboard.
• A few decorative animations loop for as long as the page is open, with no pause button: a slow pulse around the main button, a turning ring of text on the home page and a dot on the pilot page. They are off when your device asks for less motion.
• The checks ran in desktop browsers set to phone sizes. Nobody has yet tested this site with a screen reader, or on a phone in the hand.
• The web preview of the app, linked from Get the app, is a separate prototype. This statement does not cover it.

Tell us about a barrier

If something on this site does not work for you, write to support@wlpchat.example. Say which page, what you were trying to do, and the browser and any assistive technology you use. The study team replies within two working days.