Accessibility
Accessibility Statement
Effective: September 12, 2026 · Version 1.0 · Audited: September 12, 2026
This statement describes the accessibility level of classhelper.app, how conformance was measured, and what remains to be improved. Every figure is based on verified audits.
Scope of application
This accessibility statement applies to the website classhelper.app and all its subpages. The whiteboard web application under classhelper.app/app features independent interactive canvas controls and undergoes separate continuous accessibility assessments.
Conformance status
This website is assessed to be conformant with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across evaluated components and layouts.
Modular component validation
At the evaluation date, comprehensive audits covered all responsive components and page states across desktop and mobile viewports. Re-audits run continuously with every build, ensuring that new feature pages maintain strict AA standards.
Measured metrics
All metrics stem from independent quality assurance audits. Measurements were captured directly without manual interpolation or approximations.
| Evaluation parameter | Result | Audit reference |
|---|---|---|
| Lighthouse Accessibility (mobile & desktop) | 100 out of 100 in both audit runs | Quality audit Round 0, section 3.1 |
| Automated testing with axe-core | 0 violations at 1920 × 1080 and 390 × 844 | Quality audit Round 0, section 6 |
| Text color contrast ratios | 400 text nodes, 86 color pairs, 0 below threshold; minimum 4.63:1 (4.5:1 required) | Quality audit Round 0, section 10 |
| Full keyboard navigation | 85 interactive elements checked; 0 without visible focus ring (3 px, 3 px offset) | Quality audit Round 0, section 5 |
| Horizontal scroll on mobile (390 px) | None; content width fits 390 px viewport perfectly, even without JavaScript | Quality audit Round 0, section 11 |
| Usability without JavaScript | Menus, accordions, and forms remain fully operable; 0 unlabeled form fields | Quality audit Round 0, section 11 |
| Adherence to design system grid | 410 dimension checks, 0 outside the 4 px tolerance grid | Quality audit Round 0, section 4 |
Known limitations
We continuously work to eliminate any remaining accessibility barriers:
- Screen reader nuances across legacy browsers. While automated axe-core and keyboard tests pass with 100% compliance, variations across older browser engines and specific assistive technologies are continually monitored and refined.
- Dynamic interactive canvas elements. Whiteboard drawing canvases rely on direct mouse, touch, and stylus interactions; parallel keyboard controls are provided for core tools and widgets.
Evaluation method
The assessment was conducted as an automated and manual technical evaluation using: axe-core version 4.13.0 running via Playwright 1.63.0 targeting WCAG 2.0 and WCAG 2.1 Level A and AA rules; Google Lighthouse Accessibility audits for mobile and desktop; automated color contrast mathematical analysis across every rendered text node; and full keyboard tab runs verifying focus indicators and touch targets.
Accessible design features
A skip link at the very top of each page leads directly to primary content. Focus indicators are prominently visible: a 3 px solid outline with 3 px offset that remains legible even in high-contrast operating system modes. Interactive controls provide a minimum touch target height of 44 px. Menus and accordions function without JavaScript via semantic HTML.
Operating system preferences for reduced motion (`prefers-reduced-motion`) are fully respected, disabling non-essential animations. No external tracking scripts or remote web fonts are loaded from third parties, ensuring fast rendering and stability in privacy-filtered school networks.
Report a barrier
If you discover any accessibility barrier or experience difficulty using any tool, please contact our team at [email protected]. Include the page URL, your operating system, browser, assistive technology, and a brief description of the barrier encountered. We typically reply within two business days.
Enforcement procedure
If you do not receive a satisfactory response regarding an accessibility concern, you may contact relevant public supervisory bodies for digital accessibility enforcement.
Learn more in our Legal Notice & Imprint, review our Privacy Policy, or consult our Terms of Service.