The IELTS Institute
Skip to main content

Accessibility statement

What we commit to, what we have done, and what we know is still imperfect.

Last updated 30 July 2026

Draft — not yet in force. This is a working draft written to make the page real and reviewable. It has not been reviewed by a lawyer and is not a binding agreement. Have it checked for your jurisdiction and business model before launch, then remove this notice.

1. Our commitment

We aim to meet WCAG 2.2 Level AA across every page, including the test player. Accessibility is checked automatically on every build, and a build that introduces a serious or critical violation does not ship.

2. What is in place

Full keyboard operation, with a visible focus indicator on every interactive element and no keyboard traps.

Contrast of at least 4.5:1 for body text in both light and dark themes, verified automatically.

Screen reader support: landmarks, labelled controls, and live announcements for the exam timer, autosave status and errors.

Motion honours your reduced-motion preference. The test player has no non-essential animation at all.

Usable at 200% zoom and at 320px width without horizontal scrolling.

3. Extended time

Real IELTS grants extra time to candidates with documented needs, and so do we. Extended time of 25% or 50% can be applied to your account and is honoured by every timed test.

Contact us to arrange it. We do not require you to send us medical documentation.

4. Audio and transcripts

Listening transcripts are available after an attempt, but never during one — a transcript mid-test would invalidate the skill being measured.

Volume and output device can be changed at any point during Listening.

5. Known limitations

Full mock tests are difficult on small screens. They are not blocked on mobile, but we advise a larger screen and say so once, without preventing you.

Some question types — diagram labelling and map completion in particular — are inherently visual. We provide text alternatives, but they cannot fully replace the visual task.

6. Tell us when we get it wrong

If something is unusable, email us and describe what happened and what you were using. We treat accessibility defects as bugs, not feature requests, and we will tell you when it is fixed.

Questions about this document? Contact us. Governing law and jurisdiction to be confirmed before launch.