Accessibility Statement

Using SailCoach

This statement covers https://sailcoach.app and the SailCoach app that runs on it, including the signed-in dashboard. It is published by Innovology Ltd, trading as SailCoach.

We want as many people as possible to be able to use SailCoach. That means you should be able to:

• change colours and contrast using your browser or operating system;
• zoom in to 200% without text running off the screen;
• use the service on a phone, which is where most people use it — usually outdoors;
• switch between a light and a dark theme, which we built for reading a screen in bright sun and on the water at dusk;
• navigate most forms and menus with a keyboard.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this service is

Parts of SailCoach are not fully accessible. We know about a number of specific problems, and they are listed below with what we are doing about each.

The short version: the written parts of the product — notes, sessions, feedback, messages, forms — are in reasonable shape. The parts that make SailCoach useful to a racing sailor are not. Race tracks, course maps, annotated video and progress charts are visual by their nature, and we have not yet built text equivalents for them.

What we have deliberately done

• A dark theme, which follows your operating system setting by default. It exists for glare on the water and for reading in the dark, and it helps people who find bright screens painful.
• A mobile-first layout. Pages are designed for a phone held in one hand and scaled up, not a desktop design squeezed down.
• A shared component library rather than hand-rolled controls. Dialogs, tabs and dropdowns are built on tested open-source primitives that ship keyboard handling and screen-reader roles as standard. An automated check in our build stops new screens using raw browser form controls instead of our own, so that keyboard and screen-reader behaviour comes from one reviewed set of components. That check only looks at the files a change touches, there is an existing backlog behind it, and it does not stop anyone hand-building a replacement for a component we do not have — which is what happened with the account menu listed below.
• Automated accessibility checks run on every code change. Around thirty of the main signed-in screens are rendered in our test suite and checked with the axe accessibility engine, and the build fails if a check fails. Automated tools find roughly a third of accessibility problems, so this is a floor, not a pass mark.

Known problems

We believe the following do not meet WCAG 2.2 level AA, except the last row, which is a level AAA matter we have listed anyway because it affects real people. This list comes from our own review, not from an audit, so it is unlikely to be complete.

Content that is not within our control

Some things on SailCoach come from somewhere else, and we cannot fix their accessibility:

• Embedded video in coaching content, where the player, its captions and its controls belong to the video host.
• Map tiles supplied by OpenStreetMap, which draw the base map underneath our own layers.
• Race-tracking and results websites that we read data from and sometimes link to.
• Content other people write and upload — a coach's notes, a photograph, an uploaded video. We are responsible for giving them the tools to describe it, and that is on our improvement list; we are not able to write their descriptions for them.

Please report problems with these anyway. We can often work around them, and we would rather know.

Feedback and reporting an accessibility problem

If you find a problem, or you need something in a different format — a document as plain text, large print, or information read out to you over email — contact [email protected].

Tell us what you were trying to do, what got in the way, and what you are using (browser, phone or computer, and any assistive technology). None of that is required; a sentence is enough.

We will acknowledge your message within 5 working days, and tell you either how to do the thing you were trying to do, or when we expect to fix it. If it is going to take a while, we will say so rather than go quiet. Working days are Monday to Friday, excluding public holidays in England and Wales.

If you would rather make a formal complaint, use the Complaints Policy.

Enforcement procedure

We are not a public body, so the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 do not apply to us. We have written this statement in the form those regulations require because it is the clearest format there is, and because the underlying duty still applies to us.

That duty comes from the Equality Act 2010, which requires a service provider to make reasonable adjustments so that disabled people are not put at a substantial disadvantage.

The Equality Advisory and Support Service (EASS) at equalityadvisoryservice.com gives free, independent advice about your rights, and can help arrange conciliation. You do not need to have complained to us first. EASS advises; it cannot take action against us.

If you want to enforce the duty, the Equality Act gives you a claim in the county court — the sheriff court in Scotland — under section 114. There is a time limit of six months less one day from the act you are complaining about (section 118). That clock is not paused by our complaints procedure, by talking to EASS, or by us promising a fix on a date in the table below. If you are anywhere near it, take advice rather than waiting for us. The Equality and Human Rights Commission enforces the Act more broadly, but it does not ordinarily take up individual complaints.

Our broader position on fairness and inclusion, including how we try to stop the product entrenching existing advantage in the sport, is in our Equality, Diversity and Inclusion Policy.

Technical information about this service's accessibility

Innovology Ltd is committed to making SailCoach accessible, in line with the Equality Act 2010.

Compliance status

SailCoach is partially conformant with the Web Content Accessibility Guidelines version 2.2 level AA. "Partially conformant" means some parts do not fully conform to the standard.

This assessment is our own. No independent accessibility audit has been carried out. We are stating that plainly because a self-assessed claim and an audited one are not the same thing, and it would be misleading to let this page read like the second.

What we are doing to improve accessibility

A non-dragging alternative for drawing video annotations is harder, and we are not going to put a date on it that we cannot keep. If drawing is something you cannot do and it is blocking you, write to [email protected] — a workaround for one person is quicker than a rebuild for everyone, and we will do it.

How we prepared this statement

This statement was prepared on 17 September 2026. It reflects the service as it was on that date.

It is based on an internal review of the running product against WCAG 2.2 level AA, carried out by the team that builds it, together with the automated axe checks that run in our test suite. We reviewed the main signed-in journeys — sessions, notes, feedback, messages, progress and race analysis — and the public pages.

We did not use an external auditor, and we did not carry out formal testing with disabled users or assistive technology users. Both of those are gaps, and the audit commitment above is how we intend to close the first one.

We review this statement at least every 12 months, and whenever a significant new part of the product ships. Next review: 17 September 2027.