Accessibility statement

Last reviewed: April 29, 2026

Homeschool OS is built for families. That means it has to work for parents who teach with assistive technology, students with disabilities, grandparents who joined the household to help, and anyone using a keyboard, screen reader, or zoomed-in browser to get through their day.

We treat accessibility as a baseline requirement, not a feature. This page describes the standards we hold ourselves to, what we currently test against, the limitations we know about, and how to reach us when something doesn't work for you.

Our standard

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the standard most commonly referenced by U.S. accessibility law (including Title III of the Americans with Disabilities Act and Section 508 of the Rehabilitation Act).

Where individual flows fall short of AA, we treat it as a defect and prioritize a fix in the same way we prioritize any other product defect.

What we do

Semantic HTML and landmarks. Every page uses appropriate headings, landmarks, and roles so screen readers can navigate the structure.
Keyboard accessibility. Every interactive element — including dialogs, menus, the curriculum importer, and the Student app — can be reached, opened, used, and dismissed with a keyboard alone. Focus rings are visible.
Color and contrast. Text and meaningful UI elements meet or exceed WCAG AA contrast ratios. We do not use color alone to convey state.
Forms. Inputs have associated labels, error messages are associated with their fields, and submit buttons clearly indicate state changes.
Motion. We respect the prefers-reduced-motion media query and avoid auto-playing or large parallax animations.
Alternative text. User-uploaded images, generated charts, and decorative imagery follow consistent rules for alternative text and descriptive labels.
Voice features. Voice-driven features (dictation, hands-free assistant) are optional supplements, never the only way to perform an action.

What we test

Automated audits with axe-core during development.
Manual screen-reader checks with VoiceOver (macOS, iOS) and NVDA (Windows) on the most-used flows: signup, daily Student checklist, evidence capture, schedule view, settings.
Keyboard-only walkthroughs of the same flows on every release.
Browser zoom and reflow at 200% and on small mobile viewports.

Known limitations

We are honest about gaps:

Some long-form analytics charts (pacing forecast, attendance heatmap) rely on color and shape. We are working on accessible text equivalents that summarize the chart in plain language.
A small number of third-party widgets — most notably the Stripe checkout iframe and the Customer Portal — are governed by Stripe's accessibility commitments rather than ours. They generally meet AA but the user experience is partially out of our hands.
Mobile drag-and-drop on the schedule view has a keyboard fallback but we recommend the mobile checklist for keyboard-only or screen-reader users until we ship a fully equivalent reordering UI.

Tell us when something doesn't work

Accessibility issues are bugs, and bug reports help us fix them faster than internal audits can find them. If something on Homeschool OS doesn't work with your assistive technology, or you hit a barrier you weren't expecting, please tell us:

Email: support@homeschoolos.io

When you report an issue, it helps to include:

The URL or screen where the problem occurred.
The browser, operating system, and assistive technology you were using (e.g., "Chrome 124 on Windows 11 with NVDA 2024").
What you expected to happen and what actually happened.

We aim to respond to accessibility reports within two business days and to land fixes for blocking issues in our next release.

Updates

We review and update this statement at least annually, and whenever the product changes in ways that materially affect accessibility. The "Last reviewed" date at the top reflects the most recent review.