Accessibility
Accessibility statement for Edvation
We build the public site and the product to WCAG 2.2 Level AA — the level GOV.UK, GIGW 3.0 and IS 17802 converge on. This statement says what is in place, what is not yet, and how to reach us when something is in your way.
Last reviewed 2026-09-13. Reviewed with every release that touches the public surface.
What standard do we build to?
WCAG 2.2 at Level AA, the standard the Rights of Persons with Disabilities Act 2016 (s. 46) points private service providers at through IS 17802 (Parts 1 and 2), and the one GIGW 3.0 uses for Indian public buyers. English pages carry lang="en-IN", Hindi pages lang="hi", and inline phrases in the other script are tagged so screen readers switch voices.
What is in place today?
On every public page: a skip link as the first tab stop; every control reachable and operable by keyboard with a visible focus ring; 44px touch targets in the header and the mobile sheet; text contrast at or above 4.5:1 on paper and ink grounds; no information carried by colour alone; every photograph and drawing with an alternative text or marked decorative.
- Motion respects two switches — the operating system’s reduce-motion preference and an in-page toggle — and when either is on every animation sits at rest, including the 3D depth effects, which are never a dependency for reading anything.
- Anything that moves for more than five seconds has a visible pause control: the agent book and the language marquee both stop on a button, not only on hover.
- The role rail on the landing page is a real tablist — arrow keys, Home and End move between the twenty roles — and the FAQ uses native disclosure elements.
- Menus open on click, close on Escape, and return focus to the control that opened them. The mobile menu traps focus while it is open and locks the page behind it.
- Headings are in order, one h1 per page, landmarks named, forms labelled, and the two languages are complete mirrors of one another.
What is not done yet?
We have not commissioned an independent conformance audit and do not claim conformance. An IS 17802 Accessibility Conformance Report is on the roadmap because the draft RPwD (Amendment) Rules 2026 make one a filing obligation; we will publish it here when it exists, with its date.
- Embedded third-party surfaces — the demo-booking calendar — follow their own provider’s accessibility work, which we do not control.
- Generated PDF exports from inside the product (report cards, registers) are tagged for reading order but have not been audited screen by screen.
- Some data-dense screens inside the product rely on tables whose column headers are announced but whose row headers are not yet.
How do you tell us?
Write to info@edvation.ai with the page address and what happened, and the assistive technology you were using if you know it. We reply within ten working days, and an accessibility problem that blocks a task is treated as a defect, not a request.