Accessibility
Accessibility at APEX
APEX is designed with accessibility as a core product and engineering requirement, using WCAG 2.1 Levels A and AA as our target standard. This statement describes what we have done, what we know is still open, and how to reach us if you encounter a barrier.
- Target standard
- WCAG 2.1 Levels A and AA
- Effective
- August 12, 2026
- Scope
- Coach, Athlete, and Live applications
Status
Our current conformance status
We state our position precisely so institutions can evaluate it accurately.
We have completed substantial platform-wide internal evaluation and remediation, including automated accessibility testing and manual keyboard, assistive-technology, browser, and device testing of representative critical workflows.
We have not completed a comprehensive independent WCAG conformance assessment across all supported browser and assistive-technology combinations, and we have not issued a VPAT or Accessibility Conformance Report. Accordingly, we do not represent APEX as formally conforming to WCAG 2.1 Level AA. Formal independent conformance assessment is pending.
Standard
The standard we target
We use the Web Content Accessibility Guidelines (WCAG) 2.1, Levels A and AA, as the target standard for our web applications.
Accessibility is treated as a core product and engineering requirement rather than a remediation project. Our engineering standards require new and changed user-facing features to be built and tested against code-remediable WCAG 2.1 A/AA requirements, and those requirements are enforced by automated checks in our build pipeline.
Work completed
What we have done
A platform-wide remediation program covering the applications coaches, athletes, and administrators use.
Platform-wide internal evaluation and remediation
We completed an internal accessibility evaluation and substantial remediation across the Coach, Athlete, and Live applications and the shared component library all three are built from. The work covered semantic structure, keyboard operability, accessible names, tables and data grids, charts and their text equivalents, forms and error messaging, focus management, color contrast, zoom, and responsive reflow.
Automated testing and regression guardrails on every build
Automated accessibility checks and custom lint rules run as a gate on every build. A new accessibility violation fails that gate and must be reviewed and resolved before the change ships, so remediated surfaces do not silently regress.
Keyboard-only and assistive-technology testing
Representative critical workflows across the three applications were manually exercised using keyboard-only navigation and using VoiceOver with Safari.
Device testing
Live workflows — the surfaces coaches use on the floor during a session — were tested on a physical iPad in both portrait and landscape orientation.
Open work
Known limitations
Areas where we know accessibility work is incomplete. We publish these rather than leave them for a reviewer to discover.
Generated PDFs are not tagged
PDF reports produced by the platform are not tagged for assistive technology under our current renderer. Where a report is generated, a semantic HTML companion presents the same underlying data in a structure assistive technology can navigate. A formal PDF accessibility review is still outstanding.
AI-generated tabular content
A screen reader may not announce a useful name or row context for tables our AI features generate. Giving that content a reliable structure is open engineering work.
Windows screen readers not yet formally exercised
Our assistive-technology testing to date has been VoiceOver-based. We have not yet formally exercised NVDA on Windows or JAWS.
No independent assessment or VPAT
No independent third-party WCAG conformance assessment has been performed, and we have not issued a VPAT or Accessibility Conformance Report. Engaging an independent evaluator is on our roadmap.
Feedback
Report an accessibility barrier
Accessibility feedback is treated as a product issue, not a support formality.
If you encounter an accessibility barrier in APEX, email us at accessibility@apexcoachai.com. Where you can, tell us the page or feature involved, what you were trying to do, and the assistive technology, browser, and operating system you were using.
- We respond to reported accessibility barriers.
- Where a barrier blocks a core function of the platform, we will provide an accessible alternative or remediate the barrier.
- Reports that identify a defect are tracked through the same engineering process as any other product issue.
Scope
Scope and effective date
This statement is effective August 12, 2026. We review it at least annually and after material platform changes.
| Product | Surface |
|---|---|
| Coach application | coach.apexcoachai.com |
| Athlete application | athlete.apexcoachai.com |
| Live application | live.apexcoachai.com |
| Shared component library | Used across all three applications |
For institutional privacy and security review materials, see Trust & Security.
Accessibility Contact
Encountered a barrier in APEX?
For users, institutional reviewers, and procurement teams.