Accessibility Statement
Last updated: August 19, 2026
Our commitment
QuantegyAI aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, and to the Revised Section 508 standards at 36 C.F.R. Part 1194. We treat accessibility as part of building the product, not as a step at the end.
We would rather tell you exactly where we fall short than publish an unqualified claim. The known gaps are listed below.
Conformance status
Partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not fully conform to the accessibility standard.
A detailed Accessibility Conformance Report (VPAT® 2.5 Rev) covering every Level A and Level AA success criterion, together with the Revised Section 508 functional performance criteria, is available to institutions and to any user who requests it. Write to support@quantegyai.com and we will send it.
What works today
- Keyboard operation of navigation, forms, dialogs, and the practice-question flow. Dialogs move focus in when they open, keep focus inside while open, close on Escape, and return focus to the control you came from.
- Screen reader support through semantic HTML, landmark regions, descriptive headings, and a polite live region that announces screen changes and answer feedback without stealing focus.
- A skip-to-content link so you can bypass repeated navigation.
- Accessible names on every form field and on icon-only controls.
- Text alternatives on all images.
- Mathematical notation as real, structured math. Equations are typeset with KaTeX, which produces a MathML representation alongside the visual rendering, so a screen reader receives the structure of an expression rather than a picture of it. Square roots, fractions, exponents, and vector norms are marked up as mathematics, not as lookalike characters.
- Reduced motion. If your operating system requests reduced motion, non-essential animation is suppressed.
- Responsive reflow down to a 320 px viewport and text resizing to 200% without loss of content or function.
- Contrast meeting the 4.5:1 minimum for body text and remediated at the interface points where our own audits found failures.
- Untimed practice by default, so nothing expires while you work.
Known limitations
The following are areas where QuantegyAI does not yet meet WCAG 2.1 Level AA. We are working on each of them.
| Limitation | Who it affects | What we are doing |
|---|---|---|
| Interactive mathematics widgets drawn on canvas. Some manipulatives render to a graphics canvas, which assistive technology cannot read, and are operated by dragging without a keyboard equivalent. | Screen reader users; keyboard-only users; users with limited manipulation | Adding a text description of each widget's current state, a keyboard control path, and a non-canvas fallback view of the underlying data. Prioritised by how often each widget is used. |
| Some custom buttons built as generic elements with a button role are not all verified for keyboard activation. | Keyboard-only users; screen reader users | Auditing every instance, converting to native buttons where possible, and adding an automated test so the problem cannot return. |
| Contrast has not been exhaustively verified on every colour pair across every page, particularly muted secondary text and disabled controls. | Users with low vision | Running a complete automated contrast sweep, fixing what it finds, and adding that sweep to our continuous integration. |
| Some progress and mastery indicators rely largely on colour in their most compact form. | Users who do not perceive colour differences | Pairing every band with a text or shape indicator in all variants. |
How we evaluate accessibility
Our current assessment is a self-evaluation. It combines a source-level review of every page, an automated test suite that includes accessibility regression tests, and viewport testing in a headless browser at phone and desktop sizes.
We want to be straightforward about the limits of that: we have not yet completed a full manual evaluation with screen readers such as JAWS, NVDA, or VoiceOver, and we have not yet commissioned an independent third-party accessibility audit. Both are planned, and we will publish the results and an updated conformance report when they are done.
Third-party content
Payment is handled on Stripe's own hosted checkout page. That page is outside our control and is covered by Stripe's accessibility conformance reporting rather than ours.
Compatibility
QuantegyAI is designed to work with current versions of Chrome, Edge, Firefox, and Safari on desktop and mobile, together with the assistive technology those browsers support. It requires JavaScript.
Feedback, and how to get help
If you meet a barrier on QuantegyAI, please tell us. Reports from users are the fastest way we find real problems, and we treat them as priority work rather than as complaints.
Email: support@quantegyai.com
Please include, if you can: the page address, what you were trying to do, and the browser and assistive technology you were using.
Our commitment: we acknowledge accessibility reports within 2 business days and will tell you what we intend to do and when.
Need an accommodation now? If something on the platform blocks you and the fix will take time, contact us and we will find another way to get you the material — including a direct session with a human tutor at no additional cost.
For institutions
Institutional reviewers, procurement offices, and disability services teams can request our full VPAT® 2.5 Rev Accessibility Conformance Report, our remediation roadmap with committed dates, and our related compliance documentation by writing to support@quantegyai.com.
Formal complaints
If you are a student at an institution that provides QuantegyAI to you, you may also raise a concern through that institution's disability services or ADA/Section 504 coordinator. We will cooperate fully with any institutional accessibility review.
VPAT® is a registered service mark of the Information Technology Industry Council (ITI).
← Back to QuantegyAI