Accessibility

1. Our commitment

Trackside Athletics LLC, doing business as EVAD, wants every athlete to be able to train with EVAD — including athletes who use a screen reader, need larger text, rely on strong contrast, or navigate without precise touch. We build against WCAG 2.2 Level AA as our standard for both this website and the EVAD iOS app. We are a small independent team, which is not an excuse for an inaccessible product but does shape how we work: we automate the checks we can, we tell you plainly what is still broken, and we help you directly while a fix is pending.

2. Conformance status

EVAD is partially conformant with WCAG 2.2 Level AA. "Partially conformant" means most of the product meets the standard but some parts do not yet; the parts we know about are named in section 4. This statement covers:

• The website at evadtraining.com.
• The EVAD iOS app.

3. What conforms today

• Color contrast meets AA throughout the app, in both light and dark mode. This is not a one-time audit result. An automated check verifies every text-and-background pair in the palette on every change, and a change that drops any pair below the AA threshold fails the build and cannot ship. An equivalent check runs against this website's stylesheet.
• Text scales with your device's text-size setting. If you use Larger Text on iOS, EVAD's screens scale with it — with the exceptions noted in section 4.
• Reduce Motion is respected. With Reduce Motion on in iOS Settings, EVAD drops non-essential animation — screen transitions, reveals, and celebratory motion — across the app, not just in one or two places.
• Controls are named and typed for VoiceOver. The large majority of buttons, tabs, and interactive rows expose a spoken name and a role, so VoiceOver announces what a control is and what it does instead of reading "button".
• Important changes are announced. Confirmations, calendar selections, workout state, and program-build progress are announced to the screen reader rather than only appearing on screen.
• Touch targets meet WCAG 2.5.8 (24 × 24). A few controls are smaller than Apple's 44-point guideline but carry an expanded touch area, so they stay comfortably hittable.
• On this website: every page opens with a skip-to-content link and wraps its content in a main landmark, so keyboard and screen-reader users can bypass the header. Pages declare their language, images carry text alternatives, the layout reflows to a phone without horizontal scrolling, and the browser's own keyboard focus indicator is left intact — we never suppress focus outlines.

4. Known limitations

We would rather name these than have you discover them. Every one is on our list to fix.

• Most pop-up sheets do not isolate VoiceOver. When a sheet or dialog opens, VoiceOver can still reach the content behind it, so swiping can wander out of the sheet. Two surfaces handle this correctly today; the rest do not.
• Many text fields are labelled only by their placeholder. The placeholder disappears once you start typing, which can leave a field with no spoken name. Fields carrying an explicit accessibility label are currently the minority.
• Some icon-only buttons have no spoken name. A screen reader may announce these as an unlabelled button, including in a few places where the action is destructive.
• The shared session card ignores your text-size setting. A small number of text elements on that card are fixed-size so it renders correctly as an image for sharing. Everything else on that screen scales.
• Text that sits in a fixed slot grows only up to a limit. Where a piece of text has to fit a space that cannot grow with it — the bottom tab labels, the notification count, the athlete line and date in the app header, the number fields in onboarding — it follows your text-size setting up to a ceiling and then stops, because past that point it would be cut off instead of merely small. At the largest settings two of the five tabs previously became unreadable and indistinguishable from one another, which is what prompted this. For the tab labels the ceiling is calculated from your screen width, so a larger phone allows more growth. The EVAD wordmark in the app header does not grow at all; it is treated as a logo rather than as text. The body of each screen — the parts carrying your actual training information — is not capped.
• Screen-reader hints are sparse. Controls generally announce what they are, but few add the extra hint describing what happens if you activate them.
• We have not completed assistive-technology testing on a physical device. Our review so far is code-level and automated. A full pass with VoiceOver, Voice Control, and Switch Control on a real iPhone is planned, and until it is done there may be barriers we have not found.
• Third-party and system components — Sign in with Apple, Google Sign-In, the App Store, and the iOS share sheet — are controlled by their providers, and their accessibility is not ours to change.

5. How we assess accessibility

This statement is based on a self-evaluation of our own code and design, supported by automated checks. It has not been reviewed by an independent third-party auditor, and this page will say so until it has been.

• What the automated checks cover: color contrast against WCAG 2.2 AA thresholds, for both the app palette and this website's stylesheet. They are enforcing, not advisory — a failing change does not ship. Separately, every public page of this website currently returns zero findings from a full automated accessibility audit.
• What they do not cover: everything a person notices and a script cannot — whether a screen reads in a sensible order, whether a label makes sense out loud, whether a flow can be finished without sight or without precise touch.

6. Tell us about a barrier

If any part of EVAD is hard or impossible for you to use, we want to hear about it, and you do not need to know the standard or the terminology to report it — describe what happened in whatever words fit. Email evad.training.support@gmail.com with "Accessibility" in the subject. It helps if you can include:

• Where you ran into it — a screen in the app, or a page on this site.
• What you were trying to do, and what happened instead.
• Your device and iOS version, plus any assistive technology you use (VoiceOver, Voice Control, Switch Control, Larger Text, Reduce Motion).

We aim to respond within 5 business days. Where a fix will take longer than that, we will tell you what we are doing and offer the information or the functionality another way in the meantime — including doing the thing for you on your account, if that is what gets you back to training. There is no charge for that, and an accessibility request is never lower priority than any other support request. If our answer does not resolve it, reply and say so: it gets looked at again rather than closed.

7. Technical information

This website is built with HTML, CSS, and JavaScript and relies on your browser's built-in accessibility features. The EVAD app is a native iOS app built with React Native and relies on the accessibility features iOS provides: VoiceOver, Dynamic Type, Reduce Motion, Voice Control, and Switch Control. Accessibility therefore depends on those technologies being supported by your device and its operating system.

8. About this statement

This statement was prepared on August 18, 2026 by Trackside Athletics LLC and describes EVAD as of that date. We review it whenever we ship a release that changes accessibility behavior, and at least once a year. Corrections and additions are welcome at the address above.