Accessibility at Classed

Effective September 10, 2026 · Classed Inc.

Our commitment: Classed should work for everyone on campus, including people who use assistive technology. We build the web dashboards to WCAG 2.1 Level AA and the iOS and Android apps to Apple’s and Google’s accessibility guidelines. We aren’t there everywhere yet, and this page says plainly where we stand. If something gets in your way, email accessibility@classedcampus.com.

1.The standard we hold ourselves to

Our target is WCAG 2.1 Level AA for the web dashboards, moving to WCAG 2.2 AA as those criteria are adopted, and the platform accessibility guidelines for the native apps: the Apple Human Interface Guidelines for accessibility, exercised with VoiceOver, and the Android accessibility guidelines, exercised with TalkBack. This aligns with Section 508 of the Rehabilitation Act and the ADA Title II web rule that our customer institutions must meet. We will agree to these standards contractually, with a remediation plan and timeline for any documented exception.

2.Where we stand today

This is our honest baseline as of September 2026. We would rather tell you what is unfinished than overstate it.

  • Web dashboards. Built on semantic HTML with dialog roles, ARIA attributes, Escape-to-close, and managed focus in the shell and drawers. A full WCAG audit has not yet been performed, and automated accessibility checks do not yet run in our build pipeline.
  • Android app. Content descriptions and semantics are applied broadly, with decorative icons correctly hidden from screen readers. TalkBack coverage has not been systematically verified.
  • iOS app. Accessibility labels and hints and Dynamic Type are used across chat, profile, and onboarding. VoiceOver coverage has not been systematically verified.
  • Conformance report. We have not yet published a VPAT (Voluntary Product Accessibility Template) or Accessibility Conformance Report. One is in preparation and will be published on this page.

3.What we build in

Every new or changed screen is checked against these rules before it ships:

  • Keyboard. Every action is reachable and operable from the keyboard, with a visible focus indicator, a logical order, and no traps.
  • Screen readers. Controls, images, and icons have meaningful names; chat updates announce through live regions; pages use headings and landmarks; the mobile apps use native labels.
  • Vision. Text contrast of at least 4.5:1 (3:1 for large text and UI components); color is never the only signal; text scales to 200% and the apps respect Dynamic Type and large fonts.
  • Motion. The reduced-motion preference is honored everywhere, including on this website.
  • Forms. Every field is labeled, errors are identified with suggestions, and there are no time limits that cannot be extended.
  • Media. Classed-authored media includes captions or transcripts. Video that people upload is not auto-captioned today.
  • Touch. Touch targets are at least 44 × 44 points on mobile.

4.What we’re working on

  • Automated accessibility checks in the build pipeline for every dashboard.
  • A manual audit of the core flows (sign-in, class chat, the dashboard home, and bookings) with VoiceOver, TalkBack, NVDA, and keyboard only, with every issue logged and prioritized.
  • A self-assessed VPAT 2.5 (WCAG edition) conformance report published here, with a known-issues list and remediation dates.
  • A third-party accessibility audit and an updated report.
  • Accessibility training for every engineer and designer as part of onboarding.

5.Tell us about a barrier

Email accessibility@classedcampus.com and tell us what you were trying to do, which app or dashboard you were using, and the assistive technology involved, if any.

We respond within 5 business days. Barriers to core educational functions are fixed within 30 days; others go into the next planned release. While a fix is in progress we work with your school to arrange an alternative way to get what you need.