Accessibility statement

1. What we aim for

We work towards WCAG 2.1 Level AA. We have not been formally audited against it, so we are not claiming compliance. We are telling you the target and what we have actually done, which is more useful than a badge.

2. What is in place

• Keyboard navigation. Every link, button, field and menu can be reached and operated with a keyboard. A skip link at the top of each page jumps straight past the navigation.
• Semantic structure. Real headings in order, real lists, real buttons and real form labels, so screen readers can build an outline instead of reading a wall of text.
• Reduced motion. If your system asks for reduced motion, the scrolling ticker stops, section reveals stop animating, and the custom cursor stops easing.
• Pointer independence. The custom cursor is decorative and is switched off entirely on touch and non-hover devices. Nothing depends on hovering to be discoverable.
• Text contrast. Body and heading text is checked against its background on the dark, blue and white sections.
• Resizable text. Type is set in relative units and reflows to 200 percent zoom without content being cut off or requiring horizontal scrolling.
• Images. Photography carries alternative text; decorative graphics, including the court diagrams and the net pattern, are hidden from screen readers rather than announced as noise.
• No time pressure. There is no countdown on a booking form. The one timed behaviour is a security token expiring, and that returns a page explaining what happened rather than failing silently.

3. Known gaps

Being straight about what is not done:

• No independent accessibility audit has been carried out.
• The booking slot grid has not been tested end to end with a screen reader. It is the most complex interaction in the product and the most likely place to find problems.
• Colour contrast on venue-chosen branding is not enforced. A venue can pick a primary colour that fails contrast on its own booking page, and we do not currently stop them.
• Charts on the admin dashboards convey some information by colour alone.
• PDF and CSV exports from the sales reports are not tagged for accessibility.

These are on the list. If one of them is blocking you specifically, say so and it moves up.

4. A note for venues

Your booking page inherits this work, but you can undo some of it. Two things to watch:

• Pick brand colours with enough contrast against white and against each other. A pale accent on a white page will be unreadable for a lot of people.
• If you upload a logo image with your venue name in it, the name still needs to exist as text somewhere. We use your venue name for that automatically, so avoid replacing it with something that only appears inside the image.

5. Report a problem

If something here stops you doing what you came to do, email support.readycourt@gmail.com. Tell us the page, what you were trying to do, and what you use to browse, for example a screen reader, keyboard only, or high zoom.

We aim to reply within two working days. If a fix will take longer, we will tell you how you can get the same thing done in the meantime, including doing it for you.

Last updated: 11 August 2026