Accessibility
Accessibility statement.
OneTeam is being developed to meet WCAG 2.1 Level AA and Section 508 conformance. This page is our public statement of where we are and where we’re going.
Conformance target
WCAG 2.1 Level AA · Section 508 (revised 2018)
We design and test new features against the WCAG 2.1 AA success criteria and the Section 508 ICT requirements. Section 508 conformance is the standard required by U.S. federal agencies and adopted by most state and district procurement processes.
Current status
Partially conformant — actively improving
OneTeam’s iOS app and marketing site meet most WCAG 2.1 AA criteria. Some areas — listed below — are not yet fully conformant. We are committed to remediation on a documented timeline.
What we’ve built in
- Color contrast — Text and interactive elements meet the 4.5:1 contrast ratio (normal text) and 3:1 (large text and UI components) per WCAG 1.4.3 and 1.4.11. Light and dark modes both verified.
- Keyboard navigation — All interactive elements on the marketing site are reachable and operable via keyboard. The iOS app supports full VoiceOver navigation.
- Screen reader support — VoiceOver labels are provided for all custom controls in the iOS app. The marketing site uses semantic HTML and ARIA labels for non-text content.
- Resizable text — The iOS app respects Dynamic Type. The marketing site supports browser zoom up to 200% without loss of content or functionality.
- No reliance on color alone — Tier indicators, status states, and form errors use shape, text, and iconography in addition to color.
- Multilingual — The iOS app supports English and Spanish, with the framework in place for additional languages.
Known gaps
- VPAT — A Voluntary Product Accessibility Template is in development and will be available on request once the iOS app is in the App Store.
- Third-party assistive technology testing — We have not yet completed an independent audit by a third-party accessibility firm. Planned for the 2026–27 school year.
- Microsoft Teams adaptive cards — Card content is text-based and screen-reader friendly, but the rendering and accessibility of cards inside Teams is governed by Microsoft Teams itself.
How we test
- Manual VoiceOver testing on every iOS app release.
- Keyboard-only testing on every marketing-site change.
- Automated checks (axe-core, Lighthouse) on the marketing site as part of our deployment pipeline.
- Color-contrast verification using WCAG 2.1 ratios at design time.
Reporting an accessibility issue
If you encounter an accessibility barrier in OneTeam, please email support@oneteam.school with the subject line “Accessibility” and include:
- The page or screen where you encountered the issue
- What you were trying to do
- What assistive technology you were using (if any)
- What happened versus what you expected
We acknowledge accessibility reports within 3 business days and provide a remediation plan within 14 days.
Standards and laws we align with
- Web Content Accessibility Guidelines (WCAG) 2.1 Level AA
- Section 508 of the Rehabilitation Act, as revised in 2018
- Americans with Disabilities Act (ADA) Title II and Title III
- Individuals with Disabilities Education Act (IDEA), where applicable to school-issued software
Last updated April 28, 2026.