Skip to main content

Accessibility statement

Accessibility

AlgeBridge is built to work on a school Chromebook, a phone and a projector, with a keyboard, a screen reader, larger text or less motion. This page says what works today, what does not yet, and how to tell us when something gets in a student's way.

Last reviewed: October 16, 2026

The standard we aim for

AlgeBridge aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA.

This statement comes from a review of the app's own code by the AlgeBridge team on October 16, 2026. It is not a third-party audit, and AlgeBridge does not claim conformance yet. What was checked is below, and so is what has not been fixed.

What works now

  • Keyboard

    The pages work from the keyboard, and the first Tab stop on each one is a Skip to main content link. On a practice card, Enter checks the answer and Enter again moves to the next problem, the keys 1 to 9 pick a multiple-choice answer, the arrow keys move across the choices, and Escape closes a dialog.

  • Visible focus

    Links, buttons, tabs and fields show a 2px blue outline when reached by keyboard. On a colored banner the outline turns white, so it stays visible.

  • Screen readers

    A status line on the practice card announces each new problem and each verdict. The answer box is described by its problem, buttons that show only an icon carry a text label, and Archie's conversation is marked as a log, with each reply announced once in full.

  • Read aloud

    A speaker button reads the problem aloud, and another reads the hint, with the voice built into the device. Math is spoken as words: × as times, √ as square root of, x² as x squared. The buttons show where the browser has speech built in.

  • Text size and motion

    The Display menu in the header, in the phone menu and on the account page sets the text size in three steps, normal, large and largest, and has a Reduce motion switch that stops animations the way the device's own setting does. Both are saved on that device, with or without an account, and applied before the page first paints.

  • Touch screens

    Small text fields read at 16px on a touch screen, so an iPhone does not zoom the page when one is focused, and small text links and buttons are at least 24px tall to tap.

  • Color contrast

    A test that runs with the practice tests checks the gray text colors and every unit and interest hue against the 4.5:1 floor for text, on every surface they can land on.

  • Dialogs

    A dialog takes the keyboard when it opens, keeps Tab and Shift+Tab inside it, closes on Escape, and puts the keyboard back where it was.

Known gaps

  • The sports games

    The games are animated scenes drawn in SVG. The arrow keys or W A S D move your player (a second player takes the other set), Escape leaves the game, and each head-math problem comes up in an ordinary dialog. But a screen reader hears the game's name and its keys, not where the ball and the players are, and on a phone the game is played by dragging.

  • The 3D Bridgey House

    The house is drawn on a canvas. W A S D or the arrow keys walk your character, R turns a selected piece, Escape lets go of a piece or stops a walk, and the canvas carries a short description of the view. But moving a piece means dragging it and using one means tapping it, so a keyboard alone cannot arrange a room, and the rooms themselves are not read out.

  • Archie's reactions

    Archie's chat is text. His reactions to an answer are visual: his pose and the short line in his bubble are hidden from screen readers. The verdict itself is announced by the practice card, so only the cheer is missed.

  • Lesson videos

    Lesson videos are YouTube embeds from public math channels. Captions are whatever YouTube offers for that video; AlgeBridge adds none of its own.

  • No VPAT yet

    There is no VPAT (Voluntary Product Accessibility Template) and no third-party audit yet. This page is the team's own review of the code, and it will change as the gaps above close.

Report a problem

Email support@algebridge.org or use the Feedback page, which works with or without an account. Say which page it was, what you were using (a screen reader, the keyboard alone, a phone, larger text) and what happened.