Back to Study Scout

Accessibility

Last reviewed November 12, 2026

Our goal

Every student, parent and program staff member should be able to use Study Scout, including people who use a keyboard instead of a mouse, a screen reader, screen magnification, or high-contrast settings. We build and test against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

Where we are today

Study Scout partially conforms to WCAG 2.1 Level AA. “Partially” means most of the product meets the standard and the parts listed under Known limitations don’t yet.

  • Sign-in, setting your SAT goals when you sign up, practice (choosing, submitting and reviewing an answer), study guides, quizzes, flashcards, the study plan, insights (including choosing a week on the “Topics started” chart with the arrow keys), settings, the parent pages and the program-staff pages work with a keyboard alone. On every page of the main app, the first Tab stop is a “Skip to main content” link.
  • Buttons, links and form fields have names a screen reader announces. An answer you pick is announced as selected, and the result (“Correct” or “Not quite”) is read out.
  • On the pages we test before every release, text meets the AA contrast ratio in both the light and the dark theme.
  • Pages reflow to a single column at 400% zoom (320 pixels wide) without sideways scrolling.
  • Math in questions and study guides is published as MathML alongside the visual math, for screen readers that read it.
  • Graphs and figures in questions have a text description, and you can cross out an answer choice with its own “Cross out” button from the keyboard.
  • Our four product tour videos have captions shown in the picture.

Known limitations

  • Scratch pad. Drawing on the scratch pad needs a mouse, touch screen or pen, and a drawing you send has no text description. A screen reader announces the drawing area and what it’s for, and the scratch pad’s buttons work from the keyboard. Instead of drawing, you can type your working to the AI tutor during practice, or work on paper.
  • Graphing calculator. The calculator is provided by Desmos. You can open it, type expressions and close it from the keyboard. We haven’t tested every Desmos feature with a screen reader inside Study Scout.
  • Answer choices that are math. In Chrome and Edge, a math answer choice may be announced by its letter only (“A, button”), with the value read when you move into the choice; we haven’t yet checked this with a screen reader in those browsers. VoiceOver with Safari reads the value.
  • Video captions. Captions are shown in the picture (open captions) rather than as a separate track you can restyle, and there is no separate transcript yet. The short narrated videos in our SAT shortcuts article show a headline for each spoken line rather than full captions; the article text beside each video teaches the same shortcut.
  • Graph descriptions. A question’s graph or figure is described in words, conveying what a sighted student can read off it: any description we wrote for it (leaving out a sentence that states the correct choice), followed by details generated from its data — the axes, labelled points, whether each graph is a line (with grid points it passes through, never a point where two graphs meet) or a curve, whether it is dashed and which side is shaded, and where it crosses the axes, as precisely as the grid shows them. Generated details don’t yet cover every feature, such as a curve’s turning points.
  • Public articles. Math in our public SAT articles is drawn visually only, without MathML.
  • Mastery colours. On the Practice page, a topic’s mastery level is shown by the colour of its count; the level itself is in that count’s tooltip.
  • Tooltips. A tooltip closes if you move the pointer onto it. Tooltips also open on keyboard focus and close with Escape.

Our plan for each of these is in our Accessibility Conformance Report. Email [email protected] for a copy.

Report a problem

If something doesn’t work for you, email [email protected] with “Accessibility” in the subject. It helps to include the page, what you were trying to do, and the browser and any assistive technology you use.

  • We reply within 2 business days.
  • If the problem stops you from studying, signing in, paying or reaching your data, we’ll offer a workaround in that first reply and deploy a fix within 7 days.
  • If it makes something harder but still possible, we fix it within 30 days.
  • Minor problems are fixed in our next scheduled release.
  • We tell you when the fix is live.

How we test

Automated WCAG 2.1 checks run on our main student, parent and program-staff pages, the first and last steps of sign-up, the subscribe page, and our home, pricing, how-it-works, contact and guides pages, in both themes, before every release. A release that fails them doesn’t ship. Before major releases we also test by hand with a keyboard and a screen reader (VoiceOver with Safari), and check contrast, zoom and reflow.