Accessibility Statement
Goal100 aims to be usable by every learner.
The short version
- Goal100 aims to meet WCAG 2.1 Level AA, the standard U.S. public schools are required to meet for web content.
- Keyboard use, Listen button, Spanish help, text size, easy-read font, high contrast, dark mode and calm (no motion) mode.
- Every 3D scene and game has a text or alternative version.
- On November 11, 2026 we tested 60 pages with a free automatic checker and our own scripts, and fixed what we found (see “Test results”).
- Found a barrier? Tell us through the support form (topic: Accessibility); we answer by email, in writing.
This summary helps you read the full text; the full text controls.
Contents
1. Our standard
We design to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Under the U.S. Department of Justice's 2024 rule under Title II of the Americans with Disabilities Act (ADA), state and local government entities, including public school districts, must make web content and mobile apps they provide, directly or through contractors, conform to WCAG 2.1 AA. An April 2026 interim final rule set the compliance dates at April 26, 2027 (entities serving 50,000 or more people) and April 26, 2028 (smaller entities and special districts). We build Goal100 so schools can meet that standard, and Section 504 of the Rehabilitation Act and the ADA's general requirements apply in the meantime.
2. What we do
- Keyboard use everywhere, visible focus and a skip link.
- Make it mine: text size, easy-read font, wide spacing, high contrast, dark mode, calm (no motion).
- Listen button and Spanish help in every course and extra.
- “?” help buttons work by tap, click, Enter or Space, and close with Esc.
- Color is never the only signal: Required badges are solid with a shield; Extra badges are striped with a sparkle.
- 3D always has a text and picture fallback.
3. Known limits
Some 3D scenes and games are hard to use with a screen reader; each has a text version or an alternative activity. We are testing more devices and assistive technologies. We have not yet completed an independent audit, so we do not claim full conformance.
Test results, November 11, 2026
How we tested. A free, open-source automatic accessibility checker tested the rules of WCAG 2.0, 2.1 and 2.2 at Level A and AA, plus good-practice rules, in a web browser. We tested 60 pages that cover every kind of page: the home page, Explore, the course library, site and legal pages, the Teacher Center, family and school pages, search, the chapter films, 10 courses (home, one lesson and one tool), 4 Grade 6 class courses, the Practice app, the Python Lab and the Trace & Write Studio. Each page ran 4 times: phone size (400 × 860) and laptop size (1366 × 768), light and dark mode, English and Spanish (240 runs in all).
Our own scripts also checked: moving through the first 30 stops with the Tab key and seeing a focus ring at each one, buttons and links smaller than 40 pixels, the order of headings, the page language, and animations that never stop when “reduce motion” is on. The checker cannot judge text on a color blend, so we measured the text of the footer, the header and the buttons on the real screen pixels.
What we fixed:
- Darker text on small badges, counters and labels, and dark text on light buttons in dark mode.
- Every link has a name a screen reader can read, also on small phone screens.
- Lesson step dots are bigger to tap (24 pixels tall) and are no longer marked as a list.
- Headings no longer skip a level, and every course page says which language it is in.
- Search buttons, menu buttons, open/close rows and footer links are bigger to tap.
- When you close a course menu with Esc or Close, the focus goes back to the Menu button.
- A coin animation now stops when “reduce motion” is on.
- In one course, the Spanish help button sat under other buttons on phones; it now sits above them.
Still open:
- Some buttons and links are still under our own 40-pixel goal. They meet the WCAG minimum of 24 pixels.
- An automatic checker finds only part of the problems. We have not yet tested with screen readers, or on real phones, Chromebooks and interactive boards.
- 3D scenes and games: see “Known limits” above.
So we still do not claim full conformance. We test again after every big change.
- W3C Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation, version of December 12, 2024: https://www.w3.org/TR/WCAG22/ (checked Nov 11, 2026)
- W3C, Understanding Success Criterion 2.5.8 Target Size (Minimum): at least 24 by 24 CSS pixels, with exceptions: https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html (checked Nov 11, 2026)
4. Schools and procurement
Schools and districts can ask for our accessibility conformance information through the Contact page (topic: Schools). We answer in writing. We will work with the school on any accommodation a student needs.
5. Feedback and requests
Tell us about any barrier, or ask for content in another format, through the Contact page. We read every report and fix issues as fast as we can. This statement does not limit any right you have under disability laws.
Laws and official sources referenced
- W3C Web Content Accessibility Guidelines (WCAG) 2.1: https://www.w3.org/TR/WCAG21/ (checked Nov 7, 2026)
- ADA.gov fact sheet on the web and mobile app rule: https://www.ada.gov/resources/2024-03-08-web-rule/ (checked Nov 7, 2026)
- DOJ Interim Final Rule extending ADA Title II web compliance dates (Apr. 20, 2026): https://www.federalregister.gov/documents/2026/04/20/2026-07663/extension-of-compliance-dates-for-nondiscrimination-on-the-basis-of-disability-accessibility-of-web (checked Nov 7, 2026)
Questions about this document: use the Contact page; we answer in writing. We post every change on this page with a new date.