Accessibility Conformance Report (VPAT)
How Mighty Mathletes meets each WCAG 2.1 Level A and AA success criterion, in the VPAT 2.5 format schools and districts ask for when they buy software.
Last updated October 19, 2026
Report information
- Name of product
- Mighty Mathletes (website, student app, and teacher, school, district and family dashboards) at mightymathletes.com
- Version
- 2.0.0 (Next Generation)
- Report date
- October 2026
- Product description
- A web-based math fact fluency program for elementary students, with games, lessons, a quest, and dashboards for teachers, schools, districts and families. Built for Chromebooks; runs in current versions of Chrome, Edge, Safari and Firefox.
- Contact
- Ryan Greenstein, Founder, through the contact page
- Evaluation methods used
- A self-evaluation by the developer: keyboard-only testing, browser zoom and the program’s own text size, contrast and motion settings, reviewing the code for labels and structure, and automated checks. No outside audit has been done yet. Screen reader testing has been limited.
- Applicable standards
- Web Content Accessibility Guidelines (WCAG) 2.1, Level A and Level AA. (Level AAA is not evaluated.)
- Note
- Our Accessibility Statement describes the built-in settings and known limitations in plain language. Schools can contact us for help meeting a specific student’s needs.
Terms
- Supports
- The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports
- Some functionality of the product does not meet the criterion.
- Does Not Support
- The majority of product functionality does not meet the criterion.
- Not Applicable
- The criterion is not relevant to the product.
WCAG 2.1 Report
Table 1: Success Criteria, Level A
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | Partially Supports | Buttons, icons, avatars and dialogs have text labels, and decorative pictures are hidden from screen readers. Game boards and maps (the Quest map, Anchors Away, class-wide games) are drawn pictures that a screen reader can’t fully describe; the fact to answer is always given as text. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | There is no prerecorded audio-only or video-only content. Music and sound effects are decorative and repeat information shown on screen. |
| 1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | There is no prerecorded video with audio. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | There is no prerecorded video. |
| 1.3.1 Info and Relationships (Level A) | Partially Supports | Pages use headings, lists, tables with headers, and labeled form fields. Some game screens show information by position on a picture (for example, where players are on a board) without a text equivalent. |
| 1.3.2 Meaningful Sequence (Level A) | Supports | Reading order follows the visual order. |
| 1.3.3 Sensory Characteristics (Level A) | Partially Supports | Instructions use words, not only shape, color or position. Luma Leap asks students to jump to a glowing color; the facts in it are also given as text. |
| 1.4.1 Use of Color (Level A) | Partially Supports | Right and wrong answers are shown with words, icons and sounds as well as color. A few games (for example Luma Leap and color-coded map legends) use color as part of play. |
| 1.4.2 Audio Control (Level A) | Supports | Music and sounds can be turned off at any time with the sound button on every screen. |
| 2.1.1 Keyboard (Level A) | Partially Supports | Answers are typed, and menus, buttons and typing games work from the keyboard (Tab, Enter, arrow keys). Dragging the Quest and Anchors Away maps works best with a mouse or touch (zoom buttons are provided), and Grand Gifting asks players to drag parts into place. |
| 2.1.2 No Keyboard Trap (Level A) | Supports | Keyboard focus can always move away. Dialogs close with their buttons, and most also with the Escape key. |
| 2.1.4 Character Key Shortcuts (Level A) | Partially Supports | Inside games, number keys go straight to the answer box, and some games use W, A, S and D to walk. These only work while that game is open and never while typing in another text field, but they can’t be turned off or remapped. |
| 2.2.1 Timing Adjustable (Level A) | Partially Supports | Fact fluency is measured by quick recall, so many games are timed, and so is the second part of the fall, winter and spring check-ups (a speed round, 8 seconds per fact). The first part of each check-up has no timer. Teachers can turn games off, lower skill levels, and use the untimed learning pages and Assisted mode. Nothing signs a student out or loses work because of time. |
| 2.2.2 Pause, Stop, Hide (Level A) | Partially Supports | The Calm motion setting (and the device’s reduce-motion setting) stops bouncing, spinning and sliding in menus. Live multiplayer and class-wide games keep moving while other players play and can’t be paused by one student. |
| 2.3.1 Three Flashes or Below Threshold (Level A) | Supports | No content is designed to flash more than three times per second. |
| 2.4.1 Bypass Blocks (Level A) | Partially Supports | The website has a “Skip to content” link and page landmarks. Inside the app, screens are short and use headings, but there is no skip link. |
| 2.4.2 Page Titled (Level A) | Partially Supports | Every website page has its own title. Screens inside the app (games, dashboards) share the title “Mighty Mathletes”. |
| 2.4.3 Focus Order (Level A) | Partially Supports | Focus moves in a logical order. Student pop-ups put focus on their main button, but some teacher dashboard dialogs leave focus behind the dialog until the user tabs into it. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | Link text describes where the link goes. |
| 2.5.1 Pointer Gestures (Level A) | Supports | No multi-finger or path-based gestures are required. Maps that can be pinched or dragged also have zoom buttons. |
| 2.5.2 Pointer Cancellation (Level A) | Supports | Buttons act when the pointer is released, using standard controls. |
| 2.5.3 Label in Name (Level A) | Supports | Visible button text is part of each control’s accessible name. |
| 2.5.4 Motion Actuation (Level A) | Not Applicable | Nothing is controlled by moving or shaking the device. |
| 3.1.1 Language of Page (Level A) | Supports | Pages declare English as their language. |
| 3.2.1 On Focus (Level A) | Supports | Moving focus never changes the page by itself. |
| 3.2.2 On Input (Level A) | Supports | Changing a setting or field doesn’t move to a new page without warning. |
| 3.3.1 Error Identification (Level A) | Supports | Form errors are described in words next to the form. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Form fields have labels, and games explain how to play before they start. |
| 4.1.1 Parsing (Level A) | Supports | Pages are built with React, which produces well-formed markup. (This criterion is obsolete in WCAG 2.2.) |
| 4.1.2 Name, Role, Value (Level A) | Partially Supports | Standard controls (buttons, links, fields, switches) expose their name, role and state. Some game pieces drawn on a picture (map stops, board spaces) are not exposed as controls to assistive technology. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance level | Remarks and explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Not Applicable | There is no live audio or video. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | There is no prerecorded video. |
| 1.3.4 Orientation (Level AA) | Supports | Works in portrait and landscape. |
| 1.3.5 Identify Input Purpose (Level AA) | Partially Supports | Staff sign-up fields identify their purpose (name, email). Students don’t enter personal information. Some other staff forms don’t yet. |
| 1.4.3 Contrast (Minimum) (Level AA) | Partially Supports | Most text meets 4.5:1. A High contrast setting darkens text and makes panels solid. Some labels drawn on top of game pictures may fall below the ratio. |
| 1.4.4 Resize Text (Level AA) | Supports | Text can be enlarged with the browser to 200%, and students can choose large or extra large text in Settings. |
| 1.4.5 Images of Text (Level AA) | Supports | Text is real text, except for the logo. |
| 1.4.10 Reflow (Level AA) | Partially Supports | The website, lobby and dashboards reflow to narrow screens without sideways scrolling. Game boards and maps need a minimum size and may need scrolling or zooming out on very small screens. |
| 1.4.11 Non-text Contrast (Level AA) | Partially Supports | Buttons, fields and focus outlines have strong contrast, especially with High contrast on. Some game pieces and map details have lower contrast. |
| 1.4.12 Text Spacing (Level AA) | Partially Supports | Layouts are flexible and the website and dashboards keep working with extra text spacing. This has not been tested on every game screen. |
| 1.4.13 Content on Hover or Focus (Level AA) | Supports | Extra information on hover uses the browser’s standard tooltips, which can be dismissed. |
| 2.4.5 Multiple Ways (Level AA) | Supports | The website has menus, a footer and a site map. In the app, the lobby, dashboard tabs and Help Center link to every area. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings and labels describe their topic or purpose. |
| 2.4.7 Focus Visible (Level AA) | Supports | Keyboard focus shows a clear outline. |
| 3.1.2 Language of Parts (Level AA) | Supports | All content is in English. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | Menus and the top bar stay in the same place on every screen. |
| 3.2.4 Consistent Identification (Level AA) | Supports | Controls that do the same thing are labeled the same way throughout. |
| 3.3.3 Error Suggestion (Level AA) | Supports | Error messages say how to fix the problem (for example, “PINs are 4 digits and can’t start with 0”). |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | Supports | Purchases can be reviewed before paying, and deleting students, classes, schools or a family account asks for confirmation first. |
| 4.1.3 Status Messages (Level AA) | Partially Supports | Some status messages (saving, offline notices, form results) are announced to screen readers. Many in-game messages (right, wrong, rewards) are shown and heard but not announced. |
Revised Section 508 and EN 301 549
Mighty Mathletes is web content and software used in a web browser. Revised Section 508 (E205.4 and 501.1) and EN 301 549 (clauses 9 and 11) apply the WCAG 2.1 Level A and AA criteria above, so the conformance shown in Tables 1 and 2 applies to them as well. It has no hardware, phone or video features, and no authoring tools for creating web content.
VPAT® is a registered service mark of the Information Technology Industry Council (ITI). This report follows the VPAT 2.5 WCAG edition format.
Related: Privacy Policy · Terms of Use · Parents’ Bill of Rights · Data Security and Privacy Plan · Accessibility · VPAT · Safety and privacy