What works,and what does not yet.

We aim to meet WCAG 2.2 Level AA (opens in a new tab) across this website, including the Ai4RD research preview.

Current status: partially conformant. That means most of the site meets the standard and some parts do not yet. The parts that do not are listed in §IV by name, rather than described in general terms, because a general description is not something you can act on.

Colour and contrast

Every pairing of text colour and background colour in the site’s design was measured in both the light and dark themes, using the WCAG relative luminance formula rather than an eyeball. Body text measures 6.89:1 to 16.76:1 in the light theme and 8.85:1 to 15.84:1 in the dark. The lowest text pairing is 4.77:1, small captions on the light theme’s recessed band, against a 4.5:1 requirement; in the dark theme the lowest is 5.18:1. Accent marks and form-field borders that carry no text meet the 3:1 non-text threshold: the lowest is 3.33:1 in the light theme and 3.08:1 in the dark, over the brightest part of the warm glow it draws at the foot of the screen.

On the home page, where text sits over gradients and glows, it was also measured on the rendered pixels behind it rather than on a declared colour, because a gradient has no single background to read. That is how the problems in the recreated app screens listed in §IV were found.

Two earlier failures were found and fixed. Form field borders were drawn at 12% ink, which measures 1.27:1 on the light ground — effectively invisible to anyone with reduced contrast sensitivity; they now measure between 3.08:1 and 4.35:1 across both themes. And the inactive tab labels in the phone illustration on the home page were a mid tone on a background that fades from transparent to near-black, so they measured 3.72:1 at one end of that fade and 2.53:1 at the other. They were fixed at the time. The phone has since been redrawn, and the text inside it that falls short now is in §IV.

Keyboard and focus

• The skip link now actually moves focus. It previously pointed at a region that could not receive it, so pressing Enter scrolled the page but left focus in the header — which is the failure mode that makes most skip links useless.
• The sticky header no longer covers whatever you have just tabbed to or jumped to by anchor (WCAG 2.4.11).
• The waitlist submit button is no longer disabled by the consent checkbox. A disabled control cannot be focused and explains nothing; it now submits, and tells you what needs fixing.
• Controls are built to a 44px touch target, well above the 24px WCAG 2.2 minimum. Measured on a phone-sized screen, every control clears 24px; a few, the habit buttons and some controls inside the home page’s figures, come in two or three pixels under 44.

Screen readers

• Form errors are tied to the field they belong to, marked with aria-invalid, announced, and carry a text marker as well as a colour — so an error does not depend on seeing red.
• The habit selector on the home page now has a name, and announces what changed when you pick one. It silently rewrote three sections further down the page.
• The Ai4RD starter prompts no longer carry a hidden label different from their visible one — that broke voice control outright.
• The Ai4RD welcome dialog has a name. It referenced one that did not exist.

Motion

When your system asks for reduced motion, every animation on the site is switched off or cut to an instant, including the ones driven by scrolling, and anything that would have animated in is simply there.

• The evening on the home page advances on its own, for longer than five seconds, so it has a Pause control that works by keyboard and by touch, not just on hover. Under reduced motion it waits for you to move it on, except a breathing step, which runs its own length as it does in the app.
• Figures that play themselves play once, when they come into view, and finish in under five seconds. The ones that tell a small story, like the fortnight of nights on the home page, have a Play again button for anyone who looked away. Under reduced motion they show their finished state.
• Smooth scrolling eases the page with a mouse or trackpad only. It is off on touch screens, off under reduced motion, and off in the Ai4RD chat, where the page has scrolling panels of its own.

By hand, by the people who build it, in September 2026: keyboard-only navigation of every page, the accessibility tree inspected for each interactive component, contrast computed arithmetically over the design tokens in both themes, and text over gradients measured on the rendered page.

There has been no independent third-party accessibility audit. We would rather say that than let “tested” imply more than it does. A self-assessment finds the things you thought to look for.

Known and unfixed, at the date at the top of this page.

• Focus after renaming or deleting an Ai4RD session. Committing or cancelling removes the control you were on, and focus falls to the top of the page instead of moving somewhere sensible (WCAG 2.4.3).
• The Ai4RD mode-switch dialog on small screens. Its buttons are read in the opposite order to the one they appear in (WCAG 2.4.3).
• Ai4RD answers are generated text. We control how they are marked up, but not their heading structure or their reading order, because a language model writes them. Citations open in a new tab without warning.
• The app-screen figures show things the text does not say. The phone on the home page shows a night’s sleep and a thirty-night grid, each habit page plays that habit’s steps inside a phone, and the progress page redraws the app’s graphs. None of that is repeated in the prose beside them. On a wide screen the home page’s phone is announced by one sentence and nothing inside it is read out. A full text equivalent is owed and has not been written (WCAG 1.1.1).
• Some text inside the recreated app screens is below 4.5:1. The screens use the app’s own colours. Measured on the rendered home page, the step captions on the evening’s player drop close to 2:1 while its background shifts; on a phone, the small type on the Home screen’s wind-down card falls lower still once the card turns ember; and several smaller labels on the Home and Progress screens sit between 3.5:1 and 4.5:1 (WCAG 1.4.3).
• Printing a page from the dark theme carries the dark colours onto white paper. There is no print stylesheet yet.
• No independent audit, and no testing with real users of assistive technology. Both are things we intend to do, and neither has happened.

If something here does not work for you, please write to privacy@wellpal.io. Tell us the page, what you were trying to do, and what happened — and, if you are willing, what you use to browse. That last part is the most useful thing you can give us and we will never share it.

We answer within five working days. If a fix is quick we will make it and tell you; if it is not, we will tell you honestly when it is likely to happen and add it to §IV in the meantime, so it is on the public record rather than in an inbox.

If you need something on this site in another format in order to use it, ask. We will find a way to get it to you.

This statement was first prepared on 6 September 2026. It was revised on 25 September 2026, after the site was redesigned, and the figures in §II and §IV were measured again on that date. We review it whenever the site changes materially, and at least once a year. A statement that quietly goes stale is a statement that has stopped being true.