New Ivake now replies to new enquiries, checks documents and chases unpaid fees on its own. See how it works
Book a demo
Platform
Platform overview Admission management Institution ERP Training & placement Alumni management AI & Automation Integrations CRM vs ERP Security Implementation Glossary Mobile apps
Solutions
Universities & groups Colleges K-12 schools Skilling & coaching
Resources
Glossary Customer stories
Book a demo Log in

Home Accessibility

Accessibility statement

Institutions are required to be accessible, and they are entitled to expect the same of the software they buy. This page says what has been tested, how, and what has not.

Conformance

This website aims to conform to WCAG 2.1 Level AA, and additionally meets the Level AA target-size criterion introduced in WCAG 2.2 (2.5.8). Every page listed in the sitemap has been tested against that standard.

Conformance is checked automatically on every build rather than once at launch, so a change that introduces a barrier fails before it ships.

How it is tested

  • Automated auditing. axe-core runs against every page in Chromium, Firefox and a mobile viewport. A WCAG A or AA violation fails the build.
  • Keyboard operation. Menus, tabs, accordions, the lifecycle explorer and the pricing calculator are each driven by keyboard in the test suite, including focus return after a menu closes.
  • Contrast. Every colour pair the design actually renders is checked against the 4.5:1 text and 3:1 non-text thresholds, including the dark sections and chart fills.
  • Text size. No text on the site renders below 12px, which is the floor at which small text stops being legible on a phone.
  • Reduced motion. With prefers-reduced-motion set, animation is switched off at the source rather than merely shortened, and all content remains visible.
  • Without JavaScript. Every page renders its content, navigation works and the accordions open using native browser behaviour.
  • Zoom and reflow. Pinch zoom is never disabled, and pages reflow without horizontal scrolling from 320px upwards.

What is not yet verified

Automated tools catch a meaningful share of barriers, not all of them. We would rather name the gap than imply coverage we do not have.

  • A screen-reader pass by a person. Semantics, labels and landmarks are checked programmatically, but the site has not yet been walked end to end by someone using VoiceOver or NVDA in earnest. That is scheduled, and this page will be updated with the date and findings when it is done.
  • Cognitive and language testing. We have not run comprehension testing with users. Content is written in plain language, but that is an intent rather than a measured result.

This statement covers this website. The Ivake application is assessed separately; ask us for its current position during evaluation and we will tell you what has and has not been tested.

Reporting a barrier

If something on this site blocks you, tell us and we will fix it. Write to hello@ivake.com with the page, what you were trying to do, and the browser or assistive technology you were using.

We aim to acknowledge within two working days and to give you a fix or a date. If you need information from a page you cannot use, ask and we will send it in a format that works for you.

Status of this statement

Prepared on 1 September 2026, based on the automated and manual testing described above. It is reviewed whenever the site changes materially.

Book a demo

See Ivake running on your own data

Send us a sample before the call: a term of enquiries, a fee structure, or a class list. We load it and set up your programmes, so you see your own institution on screen rather than a demo account.

Book a demo Explore the platform
  • 45 minutes, your data. Not a generic tour of features.
  • Migration mapped on the call. We show exactly where your current records land.
  • A written rollout plan within two working days, with phases, owners and dates.
  • No pressure to switch everything at once. Most schools and colleges start with one department or one intake.