Clever accessibility statement
Last updated August 26, 2026
Clever is committed to digital accessibility
Good things happen when K-12 students easily log in and learn. That’s why Clever is committed to making technology accessible to schools, educators, and students. We prioritize digital accessibility for all of our users, including people with disabilities. We are continually improving the user experience of Clever’s products for everyone, and applying the relevant accessibility standards.
Ongoing efforts to ensure accessible content
As part of our commitment to providing access for all learners, Clever uses the Web Content Accessibility Guidelines (WCAG) version 2.1 when assessing the accessibility of our products. We regularly test content and features for WCAG 2.1 Level AA compliance and fix any issues to ensure we meet or exceed the standards.
Clever takes the following measures to ensure our products are accessible for our users:
- Assign clear accessibility targets and responsibilities.
- Perform a comprehensive accessibility audit of Clever’s student and teacher portals every year, using manual and AI-powered tools we’ve built in-house to help us catch and remediate issues, and partnering with an independent third-party vendor to validate that every issue has been resolved.
- Build accessibility into our products from the earliest stages of the development process, rather than treating it as a final check before launch.
- Run ongoing internal learning & development programs so every team stays current on the latest accessibility practices and standards.
Clever’s products are continuously refined to support users with a wide range of disabilities including auditory, cognitive, neurological, physical, speech, and visual.abilities.
Preparing for new accessibility requirements
Clever is closely tracking new laws and regulations that will change how school districts and vendors they work with are expected to meet digital accessibility standards.
In 2024, the U.S. Department of Justice finalized a rule under Title II of the Americans with Disabilities Act (ADA) requiring state and local government entities, including public school districts, to make their websites, mobile apps, and digital content conform to WCAG 2.1 Level AA. Importantly, this obligation extends to content and tools that districts provide through third-party vendors such as Clever, not just what districts build themselves. In April 2026, the DOJ extended the original compliance deadlines by one year: districts serving 50,000 or more residents now have until April 26, 2027, and smaller districts and special districts have until April 26, 2028.
We’re working ahead of these deadlines to make sure Clever helps districts meet their obligations rather than create risk for them. That includes testing against the newer WCAG 2.2 standard in our latest audits, keeping our Product Accessibility Conformance Reports current, and staying engaged with the evolving legal landscape so we can adjust our roadmap as guidance develops.
Product Accessibility Conformance Reports
Clever’s accessibility reports state which accessibility standards our products meet, and specify the conformance level of each WCAG standard. These reports have been written using the Voluntary Product Accessibility Template, an industry best practice for conformance reports.
| Product VPAT | Standard tested |
|---|---|
| Clever Student Portal (iOS & Web) | WCAG 2.2 A/AA |
| Student iOS Experience | WCAG 2.2 A/AA |
| Student Web Experience | WCAG 2.2 A/AA |
| Teacher Web Experience | WCAG 2.2 A/AA |
| Clever Design System Review | WCAG 2.2 A/AA |
How can we help?
We welcome your feedback on the accessibility of Clever’s student and teacher portals. Please let us know if you encounter accessibility barriers while using Clever. You can email us at accessibility@clever.com or contact us through our support page.














