Skip to content

Accessibility

Last updated

IEP Atlas is built for special educators, so it should work for everyone who uses it, including people who use a keyboard, a screen reader, or zoom.

Our goal

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across the public site and the workspace. We don't claim full conformance, and we haven't had an independent audit. This statement covers iepatlas.com, including the workspace.

What we do

  • Our test suite runs automated accessibility checks (axe, WCAG 2.2 A and AA rules) on public pages and workspace screens.
  • Pages and workspace screens are built to work with a keyboard, with a visible focus outline and a link to skip to the main content.
  • Pages reflow without sideways scrolling at 200% zoom and on a narrow phone screen.
  • Form fields and buttons have labels that screen readers announce, and errors are announced as well as shown.
  • Animation is reduced when your device asks for reduced motion.
  • The session runner has single-key shortcuts for counting, as well as large touch targets.

Known limitations

  • PDF files that IEP Atlas makes in your browser (data sheets, goal packets, and reports) are not tagged for screen readers. The same information is available on screen, and data sheets and reports can also be downloaded as CSV.
  • The sign-up, log-in, and contact forms use Cloudflare Turnstile, a third-party bot check. It usually needs no action, but if it blocks you, email us and we will help you directly.

Report a barrier

If something on IEP Atlas is hard or impossible to use, email support@iepatlas.com with the page address and what happened, or use the contact form. A person reads every message and replies, usually within two working days. If your district needs accessibility documentation for a purchase, ask us and we will send what we have.