Built so every reader is included — and every family’s language is reached.

Our promise

The things the law requires are never behind a price

Being accessible, reaching a family in its own language, a way to report a safety concern, and a parent’s right to see their own child’s record are the things the law requires — so they are things we will never sell you back. This is our promise: these lanes will never sit behind a price, a higher tier, an unpaid invoice, or a billing suspension. We are building that into the product so it can’t be undone by accident, with an automated test that fails our build if any required lane is ever placed behind a paid gate. Today it is our commitment and the way we engineer the platform — we would rather tell you exactly where the work stands than dress a promise up as a finished feature.

Set it once, served everywhere

A family sets its home language and any accessibility needs one time, on the student record, and every screen reads that profile and adapts — the chrome, the messages, the forms, and the reading experience. That set-it-once foundation is shipped today; it is the base the rest of the accessibility and language work below plugs into. Each school also sets its main language — English or French today, with a French-first setting for Quebec. Family profile & per-school language shipped

Conformance

Where we stand against WCAG 2.1 AA

Our accessibility target is WCAG 2.1 Level AA — the bar the ADA, Section 508, and the UK, Australian, and Canadian public-sector rules all converge on. Below is an honest self-assessment of how the shipped product measures up, in the shape of a VPAT (Voluntary Product Accessibility Template) summary. We keep it current as the product changes. It is a self-assessment we maintain, not a third-party audit or a regulator’s certification.

Overall: substantially conformant, with the gaps named. The reading, design, and account surfaces support the success criteria in the table; a couple are partially supported while the roadmap items above land. We report every partial plainly rather than overstate where we are.

How we test: an automated axe-core pass runs in our build across the reader, console, and account / sign-in / settings / billing surfaces; the commerce surfaces — the cart and checkout, portrait and installment checkout, the storefront and the merch, team, and portrait stores, gift cards, prepay, order status, the printable receipt and invoice document, and the family meal-account surface; the student and family academic daily-driver surfaces — the dashboards, gradebook, transcript, messages and notifications, the online course shell and its discussion boards, and the intervention tracker; and the family-facing capture, proof, and picture-day portals, the day-of check-in kiosk and gate-ticket scanner, and the support and help-center portals; and the public and family-facing forms and readers — the minor-facing secret-ballot voter page, the family marketing opt-in, the student scholarship-match list, the classroom-project and a-thon fundraising pledge pages and the a-thon units recorder, the college-outreach compose form, the fundraising fee-and-floor disclosure, the native accessible online-edition article reader, and the school file drive browser; and the records office, state and federal compliance reporting, registrar and enrollment, counselor caseload, and scholarship review and funder consoles — the FERPA record and report data tables (scoped column headers in a labelled scroll region), the run and sign-off forms, and the not-yet-enabled status chips that carry a text label, never colour alone; the interactive learning tools — the coding block canvas and its lesson and JSON runners, the music note-grid, drum step-sequencer, and score editor, the live game-show host and read-only player consoles, and the student career-pathway map (each a custom, keyboard-operable widget whose controls carry a name and role); the staff daily-driver and campus-operations consoles — the teacher home and the desktop workspace, the carline and hall-pass desks, the lunch-wave planner and school calendar, and the health-office, attendance-intervention, and wellness check-in consoles; and the school finance ledgers — the general ledger, the trial balance, and the finance command center, whose numeric tables carry scoped headers and text debit and credit columns; and fails the build on a new critical or serious issue, backed by manual keyboard and screen-reader review. Automated tools only reach part of WCAG — roughly a third of the success criteria can be machine-verified — so a “Supports” above means automated checks plus human review, not a promise that every page is flawless. One place still tells you rather than stops you: the accessibility gate at publish time is on the roadmap above (coming), so today the tool checks content as you build it but does not yet block a page from publishing. If you hit a barrier, tell us at contact and we will fix it.