Accessibility
Potato Class is built so every student can learn — not just most. This page documents the standards we target, accommodations we ship, known limitations, and how to request alternate access or report a barrier.
Where we stand
Our target is WCAG 2.2 Level AA on web and iPad. We do not claim conformance today. Our current self-assessed report (VPAT 2.4, 2026-07-18) covers WCAG 2.1 and records partial support on nine criteria; a WCAG 2.2 AA pre-audit on 2026-10-18 found more gaps, listed below. Accessibility is a priority: we are fixing every WCAG 2.2 AA gap we find, and an updated report covering WCAG 2.2 will follow. This page changes as fixes land.
Standards we target
| Standard | Status | Scope |
|---|---|---|
| WCAG 2.2 Level AA | Target | Our target for the web app and the iPad app. We do not claim conformance today: a pre-audit against WCAG 2.2 AA on 2026-10-18 found gaps, listed below, and we are fixing them. |
| WCAG 2.1 Level A and AA | Partially supports | Our current report (VPAT 2.4, self-assessed, 2026-07-18) covers the student and teacher paths on web and iPad and marks nine criteria Partially Supports. The 2026-10-18 pre-audit found gaps on four criteria that report marks as supported: keyboard, focus visible, pointer gestures (iPad) and language of page. |
| Section 508 (Revised 2017) | Partially supports | Mapped in the same report: Section 508 incorporates WCAG 2.0 A and AA, so the WCAG 2.1 results above carry over with the same partial-support qualifications. |
| Apple accessibility guidelines | Target | iPad app: VoiceOver labels and Reduce Motion are partly in place; Larger Text (Dynamic Type) and Reduce Transparency are not yet supported. |
| EN 301 549 | Not evaluated | The European standard is not covered by our current report. |
Accommodations available today
| Feature | How it works |
|---|---|
| Text-to-speech (TTS) | All question text and reading passages can be read aloud. Available student-side and teacher-assigned. Served as pre-rendered natural-voice audio from our cache, with the device’s built-in system voice (Web Speech / AVSpeech) as a structural fallback so read-aloud is always available. |
| Printed sound tasks (deaf / hard of hearing) | K-1 phonemic-awareness items are audio-first; a teacher-set accommodation renders them in print instead, so students who are deaf or hard of hearing complete the same items visually. |
| Word-to-word dictionary (multilingual learners) | A bilingual word-to-word dictionary translates single words for multilingual learners. In practice it is open to every student; on class tests and the math Grow it is an accommodation the teacher grants per student, never to a whole class — matching the Virginia testing convention that offers a word-to-word dictionary only to students who have it. The reading Grow offers no glossary at all, because a dictionary would change the comprehension construct being measured. |
| Reduced motion | On web, the browser’s reduce-motion preference cuts decorative animation to near-instant. On iPad, the assistant’s idle and answer-shake animations follow the system Reduce Motion setting; the Home-screen potato’s idle and jump animation does not yet. |
| Untimed assessments | Grow assessment is untimed by design. Rapid-guess detection is a behavioral flag for response validity, not a time ceiling. Matches iReady and MAP Growth conventions. |
| Keyboard navigation | On web, the student app’s screens start with a working “Skip to main content” link (it does not yet work on the join, privacy and support pages), Tab and Shift-Tab move through the student path with a visible focus ring, Escape closes overlays and Enter submits answers. Some interactive questions are not yet keyboard-operable (see the gaps below). |
| Screen reader support | On web, overlays are announced as dialogs with a name, and icon-only buttons carry text labels. On iPad, question diagrams carry spoken VoiceOver descriptions. Our screen-reader testing so far is spot checks, not a full walk-through; the gaps we know of are below. |
Tested with
| Keyboard-only walk of the web app | 2026-07-18 review; repeated 2026-10-18 |
| Screen readers (VoiceOver on iPad, a desktop screen reader on web) | Spot checks, 2026-07-18; full walk-through not yet done |
| Automated contrast check (web app, over the animated sky) | Runs before each release |
| axe-core automated rule sweep (web app) | One-off sweep, 2026-10-18; a check before each release is in progress |
| Code review against WCAG and Apple’s accessibility guidelines | WCAG 2.1: 2026-07-18; WCAG 2.2: 2026-10-18 |
Known gaps we are fixing
These are the gaps our 2026-07-18 review and our 2026-10-18 WCAG 2.2 AA pre-audit found and have not yet closed.
| Area | Status | Detail |
|---|---|---|
| Zoom and text size | Fixing | Desktop browser zoom to 200% works. Pinch-zoom is currently switched off on phones and tablets. On iPad, most text does not follow the Larger Text setting; a teacher-controlled font-size accommodation enlarges question, answer and hint text in the meantime. |
| Drag-only and gesture-only questions | Fixing | Most drag questions have a tap-to-place alternative, but a few can only be answered by dragging (moving a shape’s corners, the probability-line dot, the box-plot handles), and two of them cannot be answered from the keyboard. On iPad, the ruler and protractor need two-finger rotate or pinch. |
| Screen readers | Fixing | On web, drawing visuals rely on the question text for context, and on question screens the closed toolbox can still be reached by Tab and is read out by screen readers. On iPad, about a dozen interactive question widgets have no VoiceOver representation yet. A full screen-reader walk-through is still to come. |
| Keyboard focus | Fixing | On our support page, the drop-down menus show a focus ring and the typed fields darken their border on focus; we are checking whether that border is visible enough. Some dialogs do not yet keep keyboard focus inside them while open. |
| Contrast and color | Partial | In the web app, text and controls over the animated sky are checked automatically before each release, and subject colors are always paired with text labels. On our public website, low-contrast gray text and in-text links that relied on color alone were fixed on 2026-10-18. The iPad app has no automated contrast check yet. |
| Language of page | Fixing | The web app always declares English as the page language, even when a student switches the interface to another language, and does not yet switch to right-to-left for Arabic. |
| Captions / audio | N/A | No video content with audio narration. AiPa speech is short, on-demand, and the same content is rendered as on-screen text. |
Reporting a barrier or requesting alternate access
If you encounter an accessibility barrier in Potato Class, or need alternate access to information on this site, please contact us. We respond to access requests and barrier reports within two business days.
Email: partnerships@growingstandard.com with subject line beginning "Accessibility:"
What to include: the page or screen, the assistive technology you were using, and what you expected to happen versus what did. If you can include a screenshot or screen reader transcript, that's helpful but not required.
For procurement reviewers
Our VPAT 2.4 Rev WCAG (WCAG 2.1 Level A and AA, self-assessed, 2026-07-18) is available on request. It is a self-assessment, not an independent third-party audit, and it predates our 2026-10-18 WCAG 2.2 AA pre-audit; where the two differ, this page follows the pre-audit. A report covering WCAG 2.2 will replace it.
Related procurement documents: Data Privacy · DPA Summary · DPA Template · Security · Service Status
Last updated: 2026-10-18. Next scheduled review: 2026-11-10 (quarterly cadence). How we evaluate is listed under “Tested with” above. Accessibility is a continuous practice, not a certification.