Skip to content
ClassBreak
ACCESSIBILITY

Built for every classroom.

ClassBreak is designed to work for teachers and students of all abilities. Here's our commitment and our current status.

ClassBreak is committed to achieving WCAG 2.1 Level AA conformance across all pages and features. We are an ongoing work in progress — this page documents our current status and known issues.

What we've built

Keyboard navigation
All interactive elements — games, filters, navigation, modals — are fully keyboard accessible. Tab, Enter, and Escape work throughout the app.
Screen reader support
We use semantic HTML and ARIA labels throughout. Game instructions and timers include screen-reader-friendly descriptions.
Colour contrast
All text meets WCAG AA colour contrast ratios (minimum 4.5:1 for body text). Our yellow (#FFE400) on ink (#0A0A0A) background exceeds AAA.
Focus indicators
Visible focus rings are present on all interactive elements. We do not remove the browser's default focus indicator without replacing it.
Reduced motion
ClassBreak respects the prefers-reduced-motion system setting. Animations are paused or removed for users who prefer reduced motion.
Responsive text
All text scales with browser font size settings. Minimum body text is 14px; headings use clamp() to scale proportionally.

Known limitations

We are aware of the following areas that need improvement:

  • Some older game cards do not yet have descriptive alt text on their icon illustrations.
  • The ROI calculator sliders on the Plans page do not yet announce their current value to screen readers.
  • Video content (when added) will include captions and audio descriptions.

We are actively working on these and expect them to be resolved by Q3 2026.

Third-party content

ClassBreak uses Stripe for payments and Firebase for authentication. Their accessibility conformance is documented on their respective websites.

Feedback

Found an accessibility issue? We want to know. Email accessibility@classbreak.app and we'll respond within 2 business days. We take all accessibility feedback seriously and treat it as a high-priority bug report.