Accessibility Statement

Last updated: February 16, 2026

Peer10 is committed to ensuring that our platform is accessible to all users, including those with disabilities. Youth sports should be inclusive, and the technology that supports it should be too. We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level.

Conformance Target

We target WCAG 2.1 Level AA conformance across the Peer10 web application and aim to meet Section 508 of the Rehabilitation Act for any government or public school users.

Current Accessibility Features

  • Keyboard navigation: All interactive elements are accessible via keyboard. Focus order follows a logical reading sequence
  • Screen reader support: Semantic HTML, ARIA labels, and landmarks are used to provide context to assistive technologies
  • Color contrast: Body text and interface controls meet WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text). Text placed over photographs is a known exception — see below
  • Focus indicators: Visible focus indicators on all interactive elements
  • Responsive design: The platform works across screen sizes from mobile phones to desktop monitors
  • Text scaling: Content reflows properly when text is scaled up to 200%
  • Motion reduction: Animations respect the prefers-reduced-motion system setting
  • Form labels: All form inputs have associated labels and error messages are programmatically linked to their fields

Assistive Technology Compatibility

We test with the following assistive technologies:

  • VoiceOver (macOS / iOS) — primary screen reader for our user base
  • NVDA (Windows) — open-source screen reader
  • JAWS (Windows) — commercial screen reader

Known Limitations

We are actively working to improve the following areas:

  • Video content: Game film uploads do not yet include automatic captioning. We are exploring auto-captioning solutions
  • Complex data tables: Some roster and schedule tables may be challenging for screen readers. We are improving table markup and providing alternative views
  • Third-party embeds: Stripe payment forms are embedded from a third party and their accessibility is governed by Stripe's own practices
  • Text over photographs: Labels drawn on top of images — the status badges on film thumbnails in particular — do not currently meet AA against every photograph behind them. An automated audit cannot see this, because the background is a picture rather than a colour, so we measure it against the images actually in the product. Until it is fixed the affected labels are also available as text elsewhere on the same screen
  • Status colours: Success, warning and error are not yet visually distinct in every context. Nothing depends on colour alone to convey status — each carries a word — but the colours themselves are being corrected

Alternative Formats

If you need information from our platform in an alternative format (e.g., large print, audio), please contact us and we will work to accommodate your request within a reasonable timeframe.

Reporting Accessibility Issues

We take accessibility feedback seriously. If you encounter a barrier while using Peer10, please let us know:

When reporting an issue, it is helpful to include: the page or feature where you encountered the barrier, what you were trying to do, the assistive technology you were using (if any), and any error messages you received.

We aim to respond to accessibility reports within 5 business days.

Ongoing Commitment

  • We include accessibility in our design and development process from the start
  • We conduct periodic accessibility audits using both automated tools and manual testing
  • New features are tested for accessibility before release
  • We train our team on accessibility best practices
Accessibility Statement — Peer10 | Peer10