
Accessibility statement
Contents
This statement covers the website at peekwell.org: the home page, How it works, Pricing, the FAQ, the wiki, the blog, the contact form and the legal pages.
It doesn’t cover the PeekWell app at app.peekwell.org, where reports are read, or the other websites we link to.
PeekWell checks websites against the laws of each jurisdiction it covers, and accessibility is one of them: the European Accessibility Act in EU-10, the Equality Act 2010 in UK-12 and the ADA in US-06. So here’s where our own site stands, in the same plain terms.
We build and test peekwell.org against the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. The European accessibility standard, EN 301 549, uses the same level for web pages.
Every page comes in two looks: light, and reading-lamp mode, the darker one you switch on with the lamp in the header. If your device is set to a dark theme, the site opens in reading-lamp mode. Both looks are held to the same level, so text contrast has to hold up in each.
WCAG 2.2 added six success criteria at levels A and AA, and we checked the site against them on 3 November 2026. Target size is now part of our automated tests. For focus not obscured, we tabbed through every page at phone width and checked that the sticky header never covered what had focus. It never did, though the walk turned up one other focus problem, listed in section 4. The other four are about dragging, help in a consistent place, typing the same thing twice and signing in. The comic turns with a swipe but also with a tap or its buttons, so nothing needs dragging. The website has no sign-in, its help is the same contact link in every footer, and its one form asks for each thing once. We’ll call 2.2 our standard once all six are in the tests we run on every change.
Where the site stands. Our automated tests for WCAG 2.1 AA pass on every page they cover. That isn’t the same as saying the site meets every criterion, because automated tools catch only some problems. What we know falls short is in section 4.
We run these tests when we change the site:
- Automated rules in a real browser. axe-core checks every page in our test list against its rules for WCAG 2.0, 2.1 and 2.2 at levels A and AA, once in light mode and once in reading-lamp mode. The list has every kind of page on the site, with a sample of the blog posts and wiki articles.
- Lighthouse on a phone. Lighthouse loads the main pages on a simulated phone over a slowed connection, three times each. The run fails if a page’s accessibility score drops below 98 out of 100.
- Keyboard. Tests work the tabs, the comic, the personnel files on the About page and the lists in the wiki with the keyboard alone, using the arrow keys, Home, End and Enter where each one expects them.
- No JavaScript. Every page in the list loads with JavaScript switched off and must still show its heading, its navigation and its content.
- A narrow screen. Every page loads 320 pixels wide and must not scroll sideways.
- Reduced motion. With reduced motion switched on, nothing on any page may be moving.
- Blocked storage. With the browser’s storage blocked, the lamp switch must still work and the page must throw no errors.
On 3 November 2026 we also ran the automated rules over every page on the site, at phone and desktop widths, in both looks.
- Documents on other websites. Wiki articles and blog posts link to decisions, laws and guidance on authorities’ own websites, many of them PDF files. We don’t control those, and some aren’t accessible. If you need one in another format, ask us and we’ll help you find a version you can use.
- Peeky’s handwriting. Peeky’s notes, like the one with this section, use a handwriting typeface. Some people find it harder to read. The notes only repeat what the section says, so you don’t miss anything if you skip them.
- The comic on the home page. Its words are drawn into the pictures. They’re also in the page as text, shown under each picture on a phone, and every picture has a description, so a screen reader gets both.
- Focus on How it works. On a phone, tabbing to the Join now button at the end of the How it works page can leave it just above the top of the screen, because the sections above it are drawn as they come into view and the page changes height. Scrolling up a little shows it. It’s on our list to fix.
- Pages outside the test list. The browser tests run on every kind of page but only a sample of blog posts and wiki articles. A new post can go live before the full set has run over it.
- Testing by people. So far the testing is ours: automated rules and keyboard checks. Nobody who relies on a screen reader, voice control or switch access has tested the site for us yet.
The lamp switch in the header turns on reading-lamp mode, a darker look held to the same contrast. Your choice stays in your browser and goes nowhere else.
Text grows with your browser’s zoom and text size, and pages fall into a single column on screens as narrow as 320 pixels. The first thing the Tab key reaches on every page is a link that skips past the menu.
Every page’s content and links, and the contact form, work without JavaScript. Nothing moves on a loop, and with reduced motion switched on, nothing moves at all. There’s no cookie banner to dismiss, nothing pops up on its own, and nothing runs against a clock.
If something on peekwell.org is hard to use, or you need what’s on a page in another format, tell us:
- through the contact form, or
- by email to hello@peekwell.org.
It helps to know the page, what you were trying to do and what you browse with, such as a screen reader, zoom or voice control. Leave out anything you’d rather not say. A person reads every message, and we’ll tell you what we’re going to do about it.
We prepared this statement on 3 November 2026 and last reviewed it on 3 November 2026. It’s based on our own testing, described in section 3, run on that date.
We’ll review it again when the site changes in a way that affects what it says, and update the version and date at the top when we do.
