Accessibility at MathGPT

The short version

We aim at WCAG 2.1 Level AA. We have not had an outside audit, so we do not claim to have reached it.
Keyboard access, visible focus, reduced motion, and a light or dark theme are already built in.
The drawing tools still need a pointer for some actions. That is our biggest known gap.
One address for barriers: [email protected]. Tell us the task you could not finish.

What we aim for, and where we actually stand

A lot of accessibility pages state a conformance level as though it were a finished fact. This one does not, because nobody outside the team has audited this site. What we can tell you is which things are built in and testable today, which are half done, and which are still just an aim. The table below is that list. If a row says "partly", it means we know it is not finished, and a report from you about that row is genuinely useful rather than annoying.

Accessibility goals, current status, and how to report a problem
What we aim for	Status today	How to report a problem
WCAG 2.1 Level AA across the whole site	A goal, not a certified claim. No outside audit has been carried out, so we publish no formal conformance statement.	Email [email protected] with the page address and the checkpoint you believe fails.
Every page usable with a keyboard alone	In place for navigation, menus, links, and forms. A "Skip to content" link is the first thing on every page, and focus outlines are visible as you move.	Tell us the page and the key you pressed when focus vanished or got stuck.
The drawing tools usable without a mouse	Partly. Equations, matrices, and settings go into ordinary form fields, but dragging a point on a canvas still needs a pointer.	Tell us the action you needed, and we will look for a typed way to do it.
Text and layout survive zoom and small screens	In place. Sizes are set in relative units and the layout reflows to a single column on narrow screens.	Send a screenshot with your zoom level and browser.
Respect your system's "reduce motion" setting	In place. When your device asks for reduced motion, transitions, animation, and smooth scrolling are switched off.	Name the element that still moved.
Readable colour in both light and dark	In place, with a theme toggle in the header. Contrast is checked as pages are built, not by an outside auditor.	Quote the text you could not read and say which theme you were in.
Mathematics that a screen reader can handle	Partly. Equations are rendered by MathJax rather than pasted in as pictures, and written pages put a sentence next to each equation. We have not tested every page with every screen reader.	Quote the equation your screen reader skipped or read wrongly.

What is already built in

These are not plans. They are in the code today, and you can check each one in a few seconds. We list them so a report can be specific: if one of these does not work for you, that is a bug we want, not a feature request. The same behaviours apply across the solver, the calculators, and every written page in the learning section.

Getting around without a mouse

Press Tab from the top of any page and you should be able to reach everything that does something.

The first Tab lands on "Skip to content", which jumps you past the navigation.
Focus is always visible; we never hide the outline without putting something clearer in its place.
Menus are real buttons that report whether they are open, so a screen reader announces the change.
Every page has one main heading and a sensible heading order underneath it, so you can jump by heading.

Reading comfortably

Nothing on the site depends on you having sharp eyes or a large screen.

Type scales with your browser's text size and with page zoom, because sizes are relative rather than fixed.
The layout reflows to one column on a narrow screen instead of forcing you to scroll sideways.
A light and dark theme are both maintained, and the toggle sits in the header on every page.
Colour is never the only signal. Where something is marked as correct or wrong, words say so too.

Motion and noise

The site is quiet by design, and it takes your system settings seriously.

If your device asks for reduced motion, animation and smooth scrolling are turned off site-wide.
Nothing plays sound, and nothing auto-plays video.
No pop-up asks for your attention while you are working on a problem.
There is no advertising anywhere, so nothing flashes or moves for money.

Where we know we fall short

Saying this out loud is more useful than a polished claim. The interactive tools, particularly the geometry board and the 3D surface viewer, were built around dragging, and dragging needs a pointer. You can type expressions and settings, and that covers a lot, but some constructions are still out of reach without a mouse or a trackpad. Mathematical notation is a second known gap: it is rendered as real notation rather than as an image, which is a good start, but we have not tested every equation on the site with every screen reader, and we will not claim we have.

What we are working on

In rough order of how much difference it would make.

Keyboard equivalents for the canvas actions in geometry and 3D.
Testing the practice and assessment flows end to end with a screen reader.
Checking every colour pair in both themes rather than the ones we happened to look at.
An outside audit, once the known gaps above are closed.

How to report a barrier

Email [email protected]. You do not need to know the standard, name a success criterion, or be polite about it. Describe what you were trying to do and where it stopped working. A report that names a task, such as "I could not get to the Solve button on the photo solver with a keyboard", is worth more than a general note about accessibility, because it can be reproduced and fixed the same day. If you need a page in a different format to do a piece of coursework, ask; we would rather send you what you need than leave you stuck. Access reports are handled ahead of everything else in the inbox, as the contact page explains.

What to put in the message

Five short lines is plenty.

The page address.
What you were trying to do, in your own words.
Where it stopped, and what happened instead.
Your browser, your device, and any assistive technology you use.
Whether it happens every time or only sometimes.

Help us reproduce the barrier

The most useful report names a task, not a feeling. Tell us what you were trying to do, which control or piece of content stopped you, and what happened instead. Add your browser, your device, any assistive technology you use, and whether it happens every time or only sometimes. That level of detail lets us fix the workflow instead of applying a cosmetic patch that leaves the real barrier in place. Access reports are handled ahead of everything else in the inbox.

Questions people ask about this page

Do you conform to WCAG 2.1 AA?

We aim at it and we build toward it, but we do not claim to have reached it, because no independent audit has been done. Claiming conformance without an audit would be exactly the kind of statement that makes accessibility pages useless. The table above tells you which parts are in place, which are partial, and which are still an aim.

Can I use the graphing tools with a screen reader?

Partly. Expressions are typed into ordinary labelled form fields, so building and editing a function works. Reading the picture back, and dragging points on the canvas, do not yet have a keyboard or screen reader equivalent. If you tell us the specific task you need, we will look for a typed route to the same result.

Is the mathematics readable by assistive technology?

Equations are rendered as real mathematical notation with MathJax, not pasted in as pictures, which is the necessary starting point. On written pages every equation also sits next to a sentence that says the same thing in words. We have not tested every page against every screen reader, so reports about specific equations are useful.

How quickly do you fix accessibility problems?

Access reports go to the front of the queue, ahead of feature requests and general feedback. A specific, reproducible report about one control is often fixed quickly. A structural gap, such as keyboard control of a drawing canvas, takes longer, and we will tell you honestly which kind yours is.

Contact MathGPT.now

For questions related to this page, email [email protected]. Include the page address and enough non-sensitive detail to reproduce the question or problem.