Accessibility
We want everyone to be able to learn here, including people who use a keyboard, a screen reader, magnification or other assistive technology. This page says what we have done, where we fall short, and how to tell us.
Last updated
Our aim
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We have not had the site audited by an outside expert, so we do not claim that it meets them fully.
What we have done
- The site's own controls work with a keyboard and show where the focus is. A link at the top of each page skips to its content.
- Its colours are chosen to reach the WCAG contrast ratios, in light mode and in dark mode. The site follows your system's choice of light or dark, and of more contrast.
- How well you know an idea is shown with a word and a symbol as well as a colour.
- Pages are made to work on a screen 320 pixels wide, and when zoomed, without scrolling sideways.
- Movement stops when your system asks for reduced motion.
- You can type your answers, or speak them where your browser turns speech into text on your device. There is no time limit and nothing to drag.
- Error messages stay on screen until you dismiss them or move on, and most appear next to the thing that went wrong.
- The public pages, including this one, work without JavaScript.
- Automated tests check focus, contrast, reduced motion and phone widths in a real browser.
Known limits
- Interactive pictures are written by the AI for each lesson. Their sliders and charts may not work well with a screen reader. The lesson's explanation and questions do not depend on them.
- Mathematics is shown with KaTeX, which also includes MathML. How well it is read aloud depends on your screen reader.
- The AI's own words are not always as plain as we would like. You can ask the tutor to explain something more simply.
- The microphone button appears only in browsers that turn speech into text on the device itself. For now, that is Chrome and some versions of Edge on a computer. Elsewhere, your device's own dictation works in every box. Help says how.
- Payments happen on Stripe's own pages, whose accessibility is Stripe's.
- We have not yet tested the site with people who use screen readers, or with every major screen reader.
No overlays
We do not use an accessibility overlay or widget. They do not fix the underlying problems and often get in the way of assistive technology. We fix problems in the site itself.
Reporting a problem
If something does not work for you, email help@thoughtpantheon.com. Say which page you were on, what you were trying to do, and what technology you use, if you are happy to.