This statement covers the TheoryIQ website at www.theoryiq.co.uk and gives an overview of accessibility in the TheoryIQ app. It is provided by TheoryIQ Limited.

We want as many people as possible to be able to use TheoryIQ, whatever their abilities and whatever device or assistive technology they use.

How accessible the website is

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. We'll make a conformance claim only after an independent audit.

What we've built in:

  • a "Skip to content" link at the top of every page, so keyboard and screen reader users can jump past the navigation;
  • visible focus indicators on links, buttons, menus and the question-and-answer sections, so you can see where you are when using a keyboard;
  • keyboard support throughout. The licence category tabs on the home page work with the arrow keys and the Home and End keys, and the mobile menu tells assistive technology whether it is open or closed;
  • reduced motion: if you have turned on "reduce motion" in your device or browser settings, we switch off or reduce page animations;
  • text contrast that passed automated checks on every page we tested;
  • descriptive alternative text on images;
  • data tables with captions and properly marked headings;
  • links in our guides that open a new tab say so to screen reader users;
  • one main heading per page and a logical heading order.

Where we're improving the website

These are the areas we're working on:

  • Testing. So far we've tested with automated tools (Lighthouse) and our own keyboard checks. In-depth testing with screen readers such as VoiceOver, NVDA and JAWS, and with speech recognition software, is next.
  • Page language is set as English (en) rather than British English (en-GB). This may affect pronunciation in some screen readers.
  • The "Source" link in each licence category panel on the home page opens GOV.UK in a new tab without telling screen reader users first.
  • The App Store and Google Play badges are images showing "coming soon", not links, until the app is published.
  • Our guides are long articles. They have headings and, on larger screens, a table of contents, but no summary in Easy Read or other formats.

The TheoryIQ app

The app has its own accessibility settings: high contrast, reduced motion, and a dyslexia-friendly font option. Locked items still announce what they are and remain usable with screen readers, so the way to unlock content is never hidden.

An accessibility audit of the app on real devices is planned. Areas we're working on:

  • High contrast mode is being updated for our new colours, as some accent colours need more contrast in that mode.
  • Hazard perception practice is based on watching video and reacting to it, and has no non-visual alternative. The real DVSA test offers support for some candidates; see GOV.UK.
  • British Sign Language (BSL) versions of content aren't available yet.
  • We're checking every screen at very large text sizes.

What we are doing next

  • An independent accessibility audit of the website and app against WCAG 2.2 AA, with critical and high issues fixed before we make any conformance claim.
  • Testing with VoiceOver (iOS and macOS), TalkBack (Android) and NVDA (Windows).
  • Working through the areas listed above.

We will update this statement when we do.

Tell us about a problem, or ask for another format

If you have difficulty using any part of TheoryIQ, or you need information in a different format, please email info@theoryiq.co.uk. Please tell us the page or screen, what you were trying to do, and the device and any assistive technology you use.

If something stops you using a feature you have paid for because of a disability, tell us and we will look at reasonable adjustments, including alternative access where we can provide it.

If you are not happy with our response, you can contact the Equality Advisory and Support Service (EASS) (opens in a new tab).

How we prepared this statement

This statement was prepared on 13 October 2026 from our own review of the website code and automated testing (a Lighthouse accessibility score of 100 on every page tested on 12 October 2026, plus keyboard checks). An independent audit is planned (see above).