Accessibility

Last updated October 8, 2026

Our accessibility standard, what is built in today, known limitations and how to report a barrier.

iSoar is used every day by students, families and school staff with a wide range of abilities and devices. We want every one of them to be able to use it fully.

1. Our standard

We design and test iSoar against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We are working toward full conformance and fix issues as we find them.

2. What is built in today

  • Every page works with a keyboard, with a visible focus outline and a link to skip straight to the main content.
  • Pages use proper headings and landmarks for screen readers, and controls have text labels.
  • Text and controls are designed to meet WCAG AA color contrast, in both light and dark themes.
  • Status is never shown by color alone; badges also use words or shapes.
  • Anything that moves on its own has a pause button, and animation is turned off when your device asks for reduced motion.
  • Pages fit phone screens down to 320 pixels wide without sideways scrolling, and touch targets are sized for fingers.
  • Messages and announcements can be read in Spanish, Vietnamese, Russian, Chinese and Somali.

3. Known limitations

  • Some older screens in the app are still being updated to the current design and may have smaller targets or weaker contrast.
  • Charts in district analytics are summarized in text and tables, but the charts themselves are not yet fully navigable by screen reader.
  • Files uploaded by users, such as PDFs, are only as accessible as the documents themselves.

4. Tell us about a barrier

If something in iSoar is hard or impossible to use, email theisoarnetwork@gmail.com with the subject "Accessibility". Tell us the page, what you were trying to do, and the device or assistive technology you use. We will reply, and we will help you get the information you need while we fix it.

Questions about this page?

Write to iSoar Network at theisoarnetwork@gmail.com.

Email us