Accessibility Statement

Accessibility isn’t an add-on for us — it’s part of why Core Revision exists. We want every trainee to be able to revise in a way that works for them.

See every accessibility feature and how to switch it on →

Our commitment

Core Revision is built around the idea that people think, process and learn differently — and that revision should flex to fit the individual. Inclusive design is part of our development process, with educational oversight from an educational psychologist to reduce unnecessary cognitive load and support a wide range of learners, including those who are neurodivergent.

We are working towards the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA across our public pages and learning platform. Accessibility is an ongoing commitment rather than a finished task, and we keep improving as the platform grows.

What we do

  • Write clear, plain-English content in short, scannable sections with generous whitespace.
  • Use structured, semantic headings, descriptive links, and meaningful alternative text for images.
  • Choose a colour palette and type sizing intended to be comfortable and readable.
  • Build pages to work with keyboard navigation and assistive technologies such as screen readers.

The on-site accessibility tool

Adjust the site to suit you

Look for the accessibility button in the bottom-right corner of every page. It lets you:

  • Increase or decrease text size
  • Switch to a more readable font
  • Add extra letter, word and line spacing
  • Turn on a higher-contrast view
  • Highlight all links
  • Reduce on-screen motion and animation
  • Add a warm tint over the page (helpful for visual stress)
  • Show a reading ruler that follows your pointer
  • Turn on Focus mode for question pages — it hides the menu, footer and floating buttons while you answer, and there is a matching control in the Just Questions session bar

Your choices are saved on your device, so the site stays set up the way you like it as you move around.

Compatibility

Core Revision is designed to work with current versions of major browsers (Chrome, Edge, Safari and Firefox) on desktop, tablet and mobile, and to support common assistive technologies. Where your device or browser is set to reduce motion, we aim to respect that preference.

Known limitations

We’re honest about where we still have work to do. As of 10 October 2026: the Just Questions runner, Core Compass and the sign-in pages have been checked by keyboard and with automated tools, but a full screen-reader run-through (NVDA and VoiceOver) of the question runner and the mock simulator still has to be done by a person. The mock simulator offers 25% extra time; if your reasonable-adjustment letter gives you 50%, use a custom mock, which allows any time limit and a pause. The revision-guide chapters build their main heading in the browser rather than in the page source, which assistive technology handles but which we intend to fix at source. Some downloadable PDFs and embedded videos may not yet meet our target. We can provide an alternative format on request.

Tell us how we’re doing

If you come across anything that is difficult to use, or you need information in a different format, please tell us — it genuinely helps. Email admin@corerevision.com and we’ll do our best to put it right and respond promptly.

Accessibility improvements suggested by our community are exactly the kind of feedback we reward: if we implement your suggestion, we’ll thank you with 20% off your next renewal.

This statement was last reviewed on 10 October 2026 and is reviewed regularly as the platform develops.

Audit log

10 October 2026 — All 526 public pages were re-read for images, landmarks, skip links, headings and form labels. Images: 90 distinct images are in use and 87 already carried a description; one badge has been given one and the rest are decorative emblems inside buttons that have their own names. Fixed: visible labels on the app waiting-list form; a “Keep reading” label on the related-articles navigation of six DipMSK articles; a skip link on the sign-in and account pages, which use a different template; an empty heading on two DipMSK tendon tools that only fills when a card opens. Question runner (Just Questions): the question counter is now announced, keyboard focus lands on the new question after “Next question” instead of being lost, and option letters are read with a pause before the text. New: Focus mode, in the accessibility panel and the session bar, hides the menu, footer and floating buttons while you answer. Core Compass checked: the tabs, the heatmap links and the 116 session checkboxes are keyboard-operable and labelled. Still open: a human screen-reader run-through of the runner and the mock simulator; a 50% extra-time option inside the mock simulator; 85 pages carry a second element with the id “main” inside their content (the skip link reaches the correct one, and duplicate ids are no longer a WCAG 2.2 criterion); main headings written into the page source of the revision-guide chapters.

1 October 2026 — The AKT pages were re-checked with axe-core 4.10.2 against WCAG 2.0, 2.1 and 2.2 at levels A and AA, at desktop and phone widths. Fixed: low-contrast text on the AKT Pack page and in the related-links boxes on AKT articles; the white-on-teal labels on Core Tools; two Core Tools links that were told apart by colour alone are now underlined; the “Latest from Core Wisdom” links on the home page and the Terms checkbox at checkout now meet the 24 px target size; members-only pages now give visitors a page heading. The AKT Pack page, home page, checkout, free AKT taster, Core Tools, My Hub, terms and privacy pages now return no automated violations. Still open: manual screen-reader testing of the AKT question runners.

4 September 2026 — Every item listed in the 3 September entry is now closed across the DipMSK estate, and each fix was re-tested on the live pages with axe-core 4.10.2 against WCAG 2.0, 2.1 and 2.2 at levels A and AA. Colour contrast: corrected on My Hub, the Revision Guide chapters, Core Curriculum, Core Calendar, the videos page, the guide index and the exam guide — every DipMSK page now returns zero automated violations. Text spacing: !important removed from 46 inline line-height and letter-spacing declarations on My Hub, so reader-applied text spacing (1.4.12) now works. My Hub: the missing image description, the incorrectly marked-up list and the six controls below the 24 px target size are fixed. Question bank: answer options now show a visible focus ring when reached by keyboard (2.4.7), and the result of checking an answer is announced to screen readers through a polite live region (4.1.3). Page landmarks: the duplicate <main> is gone from every DipMSK page. Still open: the same duplicate-landmark pattern exists on roughly 130 pages elsewhere on the site — the other diploma guides and the portfolio pages — and will be cleared in a single pass; and manual screen-reader testing, which no automated tool replaces, remains scheduled. Automated checks catch a minority of accessibility problems, so if something is awkward for you, please tell us.

3 September 2026 — Re-scan of the DipMSK pages found problems the August pass had missed, because that pass did not reach every template. Open at the time of writing: insufficient colour contrast on several DipMSK pages (worst on Revision Guide chapters, Core Compass, Core Lens and the Tendon Companion); a missing image description and an incorrectly marked-up list on My Hub; six controls on My Hub below the 24 px minimum target size; no visible keyboard focus ring on question-bank answer options; no screen-reader announcement when an answer is marked right or wrong; and duplicated page landmarks on six pages. We are working through these and will date each fix here. If any of them is blocking you today, email admin@corerevision.com and we will prioritise it.

9 August 2026 — Full-estate accessibility audit: automated WCAG 2.2 AA checks (axe-core 4.10) across our main templates — including the Study App, the exam simulator mid-exam, and checkout — plus keyboard-navigation testing (skip links, visible focus) and reduced-motion support. The issues that audit found were fixed the same day (contrast corrections on five pages and larger tap targets on checkout consents). It did not cover every page: see the 3 September entry below. Manual screen-reader testing is scheduled as the next step; if you use assistive technology and hit any problem, we genuinely want to hear about it.