Accessibility
Accessibility statement
Gregarious is built to meet WCAG 2.1 Level AA. This page says what has been checked, how, what has not been checked yet, and how to tell us about a problem.
Last updated: October 8, 2026
What has been checked
By scripts in the code repository, on the build that is live. Each check runs again before a change ships.
- Automated rules. axe-core’s WCAG 2.1 A and AA rules pass on the 21 public pages and the 53 portal pages in the core product, at desktop and phone widths, on the current build. On September 29 they also passed on 68 more pages reachable from the portal homes.
- WCAG 2.2. On the public and core pages at phone width, axe-core’s target-size rule passes (every control is at least 24 by 24 pixels or spaced apart), and a script that tabs through every core page finds no focused element hidden under the fixed bottom navigation.
- Contrast. Text on the brand colors is near-black rather than white (5.7:1 on pink), and a test fails the build if white text comes back on a solid accent. Small gray text on the dark background is at least 4.5:1 on the checked pages.
- Keyboard. Every focusable element shows a 2px sky outline on keyboard focus. A skip-to-content link is the first thing on every page. Regions that scroll can take focus. In a sprint, the keys 1 to 5 or A to E pick an answer and Enter checks it.
- Names and labels. On the checked pages, form fields have labels and icon-only buttons have names a screen reader can say. Fields that ask for your own name, email or school declare their purpose, so a browser or assistive tool can fill them.
- Phones. No horizontal scrolling at 390px on any checked page.
- Motion. Animations stop when the operating system asks for reduced motion, or when the setting is on.
- Time. Sprints have no time limit.
- Read aloud. Sprint and review questions have a Read aloud button that reads the passage, the question and each choice in a voice that runs on the device, so the text is not sent to a speech service. A browser with no on-device English voice does not show the button.
- Page titles. Every portal page sets its own title (page, portal, Gregarious) on every navigation, and every public page has one of its own.
Settings you can change
Saved on your device and applied before the page paints, so nothing flashes. Nothing about them is sent to Gregarious.
- Text size, in four steps that scale every page (browser zoom works on top of it).
- Easier-reading text: a wide sans-serif with more space between letters and lines.
- High contrast: a black background with brighter text and stronger borders.
- Reduced motion.
- A thicker focus outline (4px instead of 2px).
What has not been checked yet
Known gaps, stated plainly. Nothing is hidden behind a roadmap.
- Nobody has tested Gregarious with a screen reader yet (VoiceOver, NVDA, JAWS or TalkBack). That is a person’s job, planned before any school uses Gregarious, and this page will name the tester and the date.
- Read aloud sounds like whatever voices the device has, and nobody who relies on text-to-speech has tried it yet.
- Studio’s game builders are pointer-driven and do not yet work by keyboard or with a screen reader. Pixel Art does (arrow keys move, Enter or Space paints), Comic does (arrow keys move a character, caption or bubble), and Story and the writing tools are ordinary forms and buttons.
- The teacher’s mastery heatmap is a table and reads row by row. Other charts have not been reviewed with a screen reader.
- There is no video, so there are no captions to check.
- The automated checks cover the pages named above. Gregarious has many more pages outside the pilot’s core, and those have not been checked.
Students with IEPs and 504 plans
Gregarious does not collect or store the contents of an IEP or a 504 plan. Sprints have no time limit. Text scales with the browser's zoom and with the text-size setting. Nothing in the product penalizes a student for using assistive technology. Accommodations that need a person, such as a reader or a scribe, work the same way they do with any other website.
Report a problem
If something on Gregarious does not work with your keyboard, screen reader, magnifier or other assistive technology, email the page address, your browser and the technology you use. Brian reads every report, and a barrier that blocks a student from a sprint or from Studio is treated as a bug to fix first.
Related: student safety and privacy.