Legal
Accessibility statement
Last updated 6 October 2026.
Everyone who is invited to a test should be able to take it. We build Medhank to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and we treat a barrier in a test as a bug.
What we do
- Every screen can be used with a keyboard alone, with a visible focus indicator.
- Controls are labelled for screen readers, and changes such as a saved answer or a warning are announced.
- Text meets WCAG contrast requirements, and pages work when zoomed to 200% and on screens down to 320 pixels wide.
- Animation is kept to a minimum and switched off when your device asks for reduced motion.
Where we know we fall short
- Some proctoring checks depend on a camera, a microphone or sharing your screen. An institution that requires them should offer another arrangement to a candidate who cannot use them; we can help it set one up.
- Looking away from the screen can be flagged where an institution turns that check on. Flags are reviewed by a person and are never, on their own, a finding against you — but tell your institution in advance if you use a screen magnifier or look away to read.
- Extra time for an individual candidate cannot yet be set in Medhank. An institution that needs to give it can set a separate test with a longer duration for that candidate.
- We have not yet had an independent accessibility audit, so we make no claim of certification.
Tell us about a barrier
If something on Medhank stops you from using it, write to [email protected] with the page and what happened. We reply within 5 working days, and fix barriers in tests before anything else. If you have a test coming up, tell your institution as well, so it can arrange an alternative in time.
In India you may also raise a complaint under the Rights of Persons with Disabilities Act 2016.