ApexAgentPrototype

Accessibility

A plain-language account of what ApexAgent actually does today — not a certification.

What's built in

ApexAgent is built with standard, real HTML elements throughout — actual buttons, form labels, checkboxes, and headings, not custom-drawn look-alikes. That means screen readers (VoiceOver, Voice Control) and keyboard-only navigation work using the browser and OS's own built-in support, rather than a bolt-on accessibility layer.

Specifically:

  • Every input has a visible, associated label — not just a placeholder.
  • Interactive elements are real <button>/<a>/<select> elements, reachable and operable by keyboard alone.
  • Text sizes use relative units, so your device's text-size/Dynamic Type setting scales the app instead of being locked to a fixed size.
  • The app follows your system's light/dark mode setting automatically.

What we haven't formally verified yet

This app has not been through a formal accessibility audit or VPAT. Color contrast, focus-order, and screen-reader behavior on every page have not been individually tested against WCAG success criteria. If you use assistive technology and hit something that doesn't work — an unlabeled control, a contrast issue, a focus trap — that's a real bug, not an accepted limitation, and we'd like to know about it.

The one uploaded-video feature (Highlight Reel) does not currently support captions or audio descriptions, since clips are raw self-uploaded game film rather than produced video content.

Report an issue

See the Support page to report an accessibility problem — tell us the page, what assistive technology/device you were using, and what happened. We treat these as real bugs to fix.