Accessibility Statement

We want this site to work for people who use a keyboard, a screen reader, screen magnification, or a browser set to reduce motion.

What we aim at

We build against WCAG 2.2 Level AA. That is the target we work to, not a claim we have met it. This site has not been audited against WCAG by an independent third party, and nobody has yet driven it end to end with a screen reader, so we do not claim conformance at any level.

What we have actually done

These are specific and checkable rather than general assurances.

An automated accessibility check runs against part of the site. A check we run drives the front page and the how-we-work page with the keyboard alone. It fails if the drafting board or the FAQ cannot be operated without a pointer, if focus becomes trapped, or if one of the decorative elements it watches is left announcing itself to a screen reader. We run it by hand. It is not wired into the deploy, and it does not cover the other pages.

Interactive elements show a visible focus state. Most take the site's standard focus outline: two pixels in the accent colour, offset from the element so it is not lost against a border. Some fields in the Clarity area do not. The sign-in field and the newsletter field there change their border colour instead, which is a weaker signal than an outline. We know about those and they are on the list.

We honour reduced motion. If your browser or operating system is set to reduce motion, every animated element on the site renders in its finished state instead of moving. Nothing fades in, nothing draws itself, and no content waits on an animation before it can be read.

Colour contrast is calculated, not judged by eye. We compute the WCAG contrast ratio from the colours as they actually render, including text drawn inside diagrams. Where a colour falls short of the AA threshold we record the number rather than round it away, and some of those decisions are still open.

Pages can be read with JavaScript turned off. They are rendered on the server and the full content, including every FAQ answer, is in the HTML. A check loads the main pages with JavaScript disabled and fails if the copy is missing. The forms, the booking calendar and the Clarity sign-in do need JavaScript. If that is a barrier, email us and we will do it for you.

What we know is not covered

The booking calendar on /booking. Until 17 August 2026 this said the page loaded a scheduling tool from another company inside a frame, whose markup and keyboard behaviour we did not control. That frame is gone and the calendar is ours: the available times are worked out on our server and are in the page when it arrives, and every day and every time on it is an ordinary button with a label, which a keyboard reaches in the ordinary way. What we have not done is test it with a screen reader, so we are not going to claim it works with one. If it blocks you, tell us and we will book the time with you by email instead.

If you hit a barrier

Email hi@moretime.ai. Tell us the page, what you were trying to do, and what you use to browse if you are willing to say.

We will acknowledge your message within ten business days and tell you what we are going to do about it. If a fix will take time, we will say so and offer another way to get what you came for, including doing the thing for you directly.