Accessibility
Last updated: November 3, 2026.
Pursiva should work for every student and family, including people who use a screen reader, navigate with a keyboard, magnify the screen, or need more contrast.
This statement covers the Pursiva website (pursivaprep.com) and the Pursiva app (app.pursivaprep.com).
Our standard
Pursiva is designed and tested to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, the standard published by the World Wide Web Consortium (W3C).
What we do
- Pursiva is built to be used with a keyboard alone, with a visible focus indicator. Where something can be dragged, there is also a button that does the same thing.
- Pages have their own titles, real headings and landmarks, so screen readers can tell pages apart and move around them.
- Buttons and form fields have names a screen reader can read. When an answer needs fixing, the message appears next to that field, in words, the field is marked as needing attention, and the cursor moves to it.
- When Pursiva is working on something for you, such as writing a plan, a screen reader is told when it starts, when it is done, and if it did not work.
- Images that carry meaning have text descriptions; decorative images are hidden from screen readers. Charts can also be shown as a table.
- Math in SAT practice questions is published as MathML, the web standard for math, so screen readers and braille displays can read and step through it.
- Text and controls meet WCAG contrast ratios, and color is never the only way information is shown.
- Pursiva works when text is enlarged up to 200% and on small screens.
- Walkthrough videos have English captions and a written transcript next to each one. They never play by themselves.
We do not use an "accessibility overlay" widget. We fix the pages themselves instead.
How we check
- Every change to Pursiva is checked automatically before it is released.
- The website: before each update goes live, an automated browser checks every page against WCAG 2.2 AA at computer and phone sizes, and checks that every page fits a narrow phone screen without scrolling sideways. If a page fails, the update is not published.
- The app: an automated browser visits every page, signed out and signed in, checks it against WCAG 2.2 AA, and also works through the main journeys the way a family would.
- Our code is checked for common accessibility mistakes as it is written.
- We also check the main student journeys by hand: with a keyboard alone, and by reviewing what each page gives a screen reader (names, headings, landmarks and announcements).
Other websites and services
Pursiva links to other websites, such as the sources cited in our guides, and uses a few outside services, such as Stripe for payments. Those websites and services follow their own accessibility policies. If one of them stops you from using Pursiva, tell us and we will help you another way.
Tell us about a problem
If something in Pursiva is hard to use, please tell us at support@pursivaprep.com, with the page and what happened. We aim to reply within 2 business days, and to fix the problem or offer another way to do what you need.