Trust

Accessibility

Draft — not yet in effect

KiteQuad is used by teachers and by students across a wide range of ages and needs, often on a school Chromebook. We build it to be usable by everyone, and we check that automatically on every release.

Our target

We aim to meet WCAG 2.1 Level AA across the teacher dashboard, the student sign-in and app screens, and these public pages. This is the standard the ADA Title II rule points to for content provided through vendors.

How we check

• Automated checks on every page. We run axe-core against every dashboard page, every student screen and every marketing page as part of our tests, and a release is held if any page has a serious or critical violation.
• Readable by default. Interface text is at least 16 px and tap targets at least 44 px, so the product works for younger students and on touch screens.
• Built for the school Chromebook. Every screen is designed to work at 1366×768, the common Chromebook size, without horizontal scrolling.
• Keyboard and screen reader. Pages use real headings, labels and focus styles, respect "reduce motion", and can be used with a keyboard or a screen reader.

Automated checks catch a lot but not everything, so some judgement calls are still made by hand. If something is hard to use, we want to hear about it.

Known limits

A teacher's published app is the teacher's own work, built in another tool. KiteQuad's check reports accessibility issues it finds in an app and suggests fixes, but KiteQuad can't guarantee a teacher-made app meets WCAG — that's up to the app. This statement covers KiteQuad's own screens.

Reporting a problem

If you hit an accessibility barrier anywhere in KiteQuad, email support@kitequad.com. Tell us the page, what you were trying to do, and the device or assistive technology you were using. We'll reply, and we treat accessibility problems as bugs to fix, not requests to queue.