Accessibility statement

Last updated: October 28, 2026

We want everyone to be able to register, upload a ride, read results and run an event with GPXTiming, whether they use a mouse, a keyboard, a screen reader, a phone or magnification.

The standard we aim for

We build to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. In practice that means pages have one clear heading structure and landmarks, every control and field has a label, error messages say what to fix and keep what you typed, nothing depends on colour alone, text has enough contrast, targets are large enough to tap, nothing refreshes or times out on its own, and no part of a task requires dragging.

How we check

Every page and state is checked automatically for structure (language, titles, headings, landmarks, labels, tables, duplicate ids) each time we change the service. Manual testing with a screen reader and keyboard, at 320 pixels wide, at 400% zoom and on real phones is done separately, and we publish what it finds here.

Known limitations

• The director's course map is a drawn map and is not usable with a screen reader. Everything it shows is also available as text and fields: the course summary, the start and finish points, neutral zones and segments, and typed times that replace dragging a marker.
• The results PDF is generated automatically and is not a tagged, fully accessible document. The same results are on the web results page, which is accessible, and in a plain-text file.
• Manual testing with assistive technology is still in progress. If you find a problem we have not listed, please tell us.

Tell us about a problem

If something on GPXTiming is hard or impossible for you to use, write to [email protected] with the page address and what happened. We will reply within five working days and, if you need it, give you the information or help another way, for example by entering your ride for you.