Accessibility

Our position

A site about sleep will be read by people who are tired, in dim rooms, on phones, late at night, and by people using screen readers, keyboard navigation, magnification, or reduced-motion settings. Designing for that is not a separate workstream; it is part of the design.

This page describes what has been built, what has been verified, and what has not yet been checked. The distinction matters — an accessibility statement that lists intentions as if they were results is not much use to anyone relying on it.

Standard we are working to

We are building towards WCAG 2.2 at Level AA. We are not claiming conformance. A formal conformance claim requires an audit that has not been carried out, and we will not make the claim before it has.

What has been built in

• Semantic HTML throughout, with one <h1> per page and headings in order.
• A skip link to the main content as the first focusable element.
• A single <main> landmark, with labelled navigation regions.
• Visible focus indicators on every interactive element, switched to a lighter colour on dark backgrounds so they stay visible.
• The one interactive menu is a real button with aria-expanded, keyboard operable, dismissible with Escape, and every destination inside it is also reachable from the footer without JavaScript.
• Colour contrast considered as part of the palette rather than checked afterwards, with a darkened variant of the lightest accent reserved for small text.
• Full support for prefers-reduced-motion, which disables transitions and animation.
• Layouts built with relative units and fluid type, so text can be resized and the page reflows without horizontal scrolling.
• No content that flashes, auto-plays, or moves without user action.

What has not been verified

• No audit by a third party has taken place.
• No formal testing with screen readers has been completed. The markup is written to be screen-reader friendly, which is not the same as having been confirmed to work well with one.
• Automated contrast checking has not been run across every combination in the palette.
• The tools are not built yet. Interactive forms are where accessibility is most often lost, and none of ours have been tested because none of them exist.

Known gaps

Fonts are currently loaded from a third-party service. Self-hosting them is a planned change and will improve reliability on slow or restricted connections.

Images are placeholders. When real photography lands, each one will need alternative text written for it, and that work has not been done.

Telling us about a problem

If something on this site is difficult or impossible for you to use, please tell us. Describe the page, what you were trying to do, and what happened, along with the browser and any assistive technology you were using if you are able to.

Accessibility reports are treated the same way as factual corrections: they are read, they are answered, and where we cannot fix something quickly we will say so rather than going quiet.

Reports can be sent through the contact page.