Accessibility Statement

1. What we're aiming for

A product whose entire job is to reach you is useless if it can't reach everyone. We build this site and the Coachyn service to target WCAG 2.2 Level AA.

We haven't had an independent audit yet. This statement describes what we've done and what we know is imperfect, rather than claiming conformance we haven't verified.

2. What's in place

Structure and navigation

• Semantic HTML with a single h1 per page and headings in order.
• A "skip to content" link as the first focusable element on every page.
• Landmarks — header, main, footer — so screen readers can jump between regions.
• The current page is marked with aria-current in the main navigation, not by colour alone.

Keyboard

• Everything interactive is reachable and operable by keyboard, in a sensible order.
• Visible focus rings on links, buttons, and form fields — we haven't removed any outlines without replacing them.
• The mobile menu is a real button with aria-expanded, not a CSS-only toggle.
• FAQ sections use native <details>, so they work without JavaScript.

Content and forms

• Every form control has a real label; errors are text next to the field, not colour alone.
• Decorative images and background flourishes are hidden from assistive technology.
• Body copy is set in Inter at comfortable sizes and reflows to 320px without horizontal scrolling.
• Data tables have proper header cells and captions, and scroll within their own container rather than pushing the page sideways.

Motion and colour

• prefers-reduced-motion disables every animation, transition-based reveal, and smooth scroll.
• Scroll-triggered reveals have a no-JavaScript fallback, so nothing is permanently invisible if a script fails.
• Text is checked against AA contrast ratios. Brand amber is used as a background behind dark text, not as light text on white.

3. Known gaps

Being honest about these is more useful than a clean-looking claim:

• No independent accessibility audit has been carried out yet.
• Form validation is server-side, so an error is announced on page load rather than live as you type. It's reliable, but it isn't the smoothest experience with a screen reader.
• Some decorative colour treatments — the amber category labels on blog cards, for instance — sit close to the AA threshold at small sizes and are on the list to re-check.
• The Coachyn app itself is early. This statement covers the website with confidence; the product is being built to the same target but has had less scrutiny.

4. Compatibility

The site is built to work with current versions of major browsers and screen readers, and does not depend on JavaScript to deliver its content. If JavaScript is off you lose the mobile menu animation, the pricing period toggle, and the password reveal button — never any information.

5. Tell us about a barrier

If something on this site or in the product got in your way, we want the specific detail — the page, what you were using, and what happened.

• Use the contact form, or
• email [email protected] with "Accessibility" in the subject.

We aim to reply within five working days and to tell you either when it's fixed or why it's going to take longer. If you'd rather have the information on this site in another format, ask and we'll provide it.

6. Keeping this current

This statement is reviewed whenever the site changes materially, and the date at the top reflects the last review. When an independent audit happens, its findings will replace section 3 rather than being summarised away.