We believe that sport belongs to everyone. We are working to make the SAL platform usable by the widest possible range of people, including those who use assistive technologies such as screen readers, keyboard-only navigation, voice control, or high-contrast display modes.
Our accessibility efforts are guided by the Web Content Accessibility Guidelines (WCAG) 2.1 published by the World Wide Web Consortium (W3C). We are actively working toward conformance with Level AA of these guidelines.
SAL is currently in partial conformance with WCAG 2.1 Level AA. This means some parts of the content do not fully conform to the accessibility standard. We have identified these areas and included them in our remediation roadmap.
The platform launched in mid-2026 and is under active development. Accessibility improvements are incorporated into each development cycle.
We are currently aware of the following limitations and are actively working to address them:
prefers-reduced-motion media querylang="en")SAL is designed to be compatible with: NVDA and VoiceOver (screen readers); Dragon NaturallySpeaking and Voice Control (voice control); keyboard-only navigation; browser zoom up to 200%; high-contrast and dark mode display settings.
The platform is tested primarily on Chrome and Firefox. We test with VoiceOver on macOS as our primary screen reader.
We welcome feedback on the accessibility of SAL. If you experience any barrier, please contact us:
We aim to respond within 5 business days and to provide a solution or workaround within 30 days where technically feasible.
If you are not satisfied with our response, you may contact the U.S. Department of Justice ADA Information Line at 1-800-514-0301.
Product: Sport Athlete Level (SAL) Web Application
Version: 1.0 · Report Date: July 2026
Evaluation Methods: Self-evaluation; manual testing with VoiceOver and keyboard; automated testing with axe DevTools
Standard: WCAG 2.1 Level A and Level AA ·
Contact: support@sportathletelevel.com
| Criterion | Status | Remarks |
|---|---|---|
| 1.1.1 Non-text Content | Partial | Most images and icons have alt text or are marked aria-hidden. Map event pins lack descriptive alt text. |
| 1.2.1–1.2.3 Audio/Video | N/A | No audio-only or video content on the platform. |
| 1.3.1 Info and Relationships | Partial | Semantic HTML used throughout. Some custom tab interfaces and modals are missing full ARIA role markup. |
| 1.3.2 Meaningful Sequence | Supports | Reading order follows visual order in the DOM. |
| 1.3.3 Sensory Characteristics | Supports | Instructions do not rely solely on shape, color, size, or location. |
| 1.4.1 Use of Color | Supports | Color is not the sole means of conveying information. Text and icons accompany color-coded elements. |
| 1.4.2 Audio Control | N/A | No auto-playing audio. |
| 2.1.1 Keyboard | Partial | All core functionality is keyboard operable. Map interface has limited keyboard access to individual event markers. |
| 2.1.2 No Keyboard Trap | Supports | Focus is managed in modals; Escape key closes all overlays. |
| 2.2.1 Timing Adjustable | Supports | No time limits on core functionality. Marketing slideshow has play/pause controls. |
| 2.2.2 Pause, Stop, Hide | Partial | Landing page slideshow has visible play/pause. Control is not yet keyboard-focused without mouse interaction. |
| 2.3.1 Three Flashes | Supports | No content flashes more than three times per second. |
| 2.4.1 Bypass Blocks | Partial | Skip navigation links not yet implemented. Planned for next release. |
| 2.4.2 Page Titled | Supports | All pages have descriptive title elements. |
| 2.4.3 Focus Order | Supports | Focus order is logical and follows reading order. |
| 2.4.4 Link Purpose | Supports | Link text is descriptive. Icon-only buttons include aria-label attributes. |
| 3.1.1 Language of Page | Supports | All pages declare lang="en". |
| 3.2.1 On Focus | Supports | No context changes occur on focus. |
| 3.2.2 On Input | Supports | No unexpected context changes on input. |
| 3.3.1 Error Identification | Supports | Form errors are identified in text and displayed near the relevant field. |
| 3.3.2 Labels or Instructions | Supports | All form inputs have visible labels. Required fields are indicated. |
| 4.1.1 Parsing | Supports | HTML is valid and well-formed. |
| 4.1.2 Name, Role, Value | Partial | Native HTML elements used wherever possible. Custom components (tab panels, score sliders) are missing some ARIA state markup. Remediation in progress. |
| Criterion | Status | Remarks |
|---|---|---|
| 1.2.4–1.2.5 Captions / Audio Description | N/A | No live or prerecorded video content. |
| 1.3.4 Orientation | Supports | Content is not restricted to a single display orientation. |
| 1.3.5 Identify Input Purpose | Partial | Standard fields use autocomplete attributes. Some custom fields do not yet declare input purpose. |
| 1.4.3 Contrast (Minimum) | Partial | Primary text (#f5f2eb on #0d0d0d) exceeds 4.5:1. Some muted/secondary text falls below 4.5:1. Active audit underway. |
| 1.4.4 Resize Text | Supports | Text resizes to 200% without loss of content or functionality. |
| 1.4.5 Images of Text | Supports | Text is rendered as actual text. The SAL logo is SVG-based text. |
| 1.4.10 Reflow | Partial | Most pages reflow at 320px. Event map and multi-column score forms require horizontal scrolling at very narrow widths. |
| 1.4.11 Non-text Contrast | Partial | Most UI components meet 3:1. Some input borders and inactive toggle states are below threshold. |
| 1.4.12 Text Spacing | Supports | No loss of content when text spacing is overridden via user stylesheet. |
| 1.4.13 Content on Hover or Focus | Partial | Some hover-revealed tooltips cannot be hovered themselves and disappear on mouse-out. |
| 2.4.5 Multiple Ways | Supports | Content is accessible via navigation links, search, and direct URL. |
| 2.4.6 Headings and Labels | Supports | Headings are descriptive and follow a logical hierarchy. |
| 2.4.7 Focus Visible | Supports | Keyboard focus indicators are visible on all interactive elements. |
| 3.1.2 Language of Parts | N/A | No content in languages other than English. |
| 3.2.3 Consistent Navigation | Supports | Navigation is consistent across all pages. |
| 3.2.4 Consistent Identification | Supports | Components with the same function are identified consistently. |
| 3.3.3 Error Suggestion | Supports | Error messages suggest corrections where applicable. |
| 3.3.4 Error Prevention (Legal, Financial) | Supports | Payment and competition flows include review and confirmation steps before submission. |
| 4.1.3 Status Messages | Partial | Toast notifications and score updates are not yet announced via ARIA live regions. Remediation planned. |
SAL relies on HTML5, CSS3, JavaScript (ES2020+), SVG, Leaflet.js (mapping), Stripe.js (payments), and Supabase (authentication and data).
This statement is based on a self-evaluation by the development team against WCAG 2.1 success criteria, manual keyboard and screen reader testing with VoiceOver on macOS 14, automated scanning with axe DevTools, and color contrast evaluation with the WebAIM Contrast Checker. An independent third-party audit is planned for 2027.