Accessibility statement

alevelmathrevision.com is committed to making mathematics education accessible to every A-Level student — including those with disabilities.

// Statement last reviewed: February 2026.

What we aim for

We aim to conform to WCAG 2.1 Level AA across the site. In practice that means:

• Every content page uses semantic HTML with a single <h1>, correct heading hierarchy, and descriptive link text.
• Every image carries an alt attribute — decorative images use alt="", informational images describe the concept.
• The site is fully keyboard-navigable — every button, link, form field and modal can be reached and operated with Tab / Shift-Tab / Enter / Esc.
• Colour contrast meets AA (4.5:1 for normal text, 3:1 for large text) throughout the marketing pages and the learning engines — despite the dark theme.
• Focus indicators (the outline around the currently-focused element) are visible and use the site's accent cyan/amber palette, not just the browser default.
• Mathematics is rendered via MathJax with accessible ARIA labels — screen readers announce equations in words rather than reading the LaTeX source.
• The site is a Progressive Web App (PWA) that installs to the home screen and works offline for previously-visited pages.

Known limitations

We're a one-person team building in the open — some parts of the site are still catching up:

• Some worked-example PDF workbooks in the downloads library are not yet fully tagged for screen-reader compatibility. If you need a tagged PDF of a specific workbook, email us and we'll send one within 3 working days.
• Interactive diagrams (e.g. graphs, mechanics free-body sketches) use inline SVG. Long-descriptions are being added — for now, a text alternative is available on request.

Reporting a barrier

If you find any part of the site that isn't accessible to you, please tell us. Send an email to pbromfield@alevelmathrevision.com including:

• The web address of the page where you had the problem
• A description of the problem, and — if useful — the assistive technology you were using
• Whether you'd like a phone call, an email reply or a text-file summary of the content

We aim to acknowledge accessibility complaints within 2 working days and provide either a fix or an alternative-access solution within 10 working days.

How we test

• Keyboard-only navigation on Chrome and Safari desktop
• NVDA (Windows) and VoiceOver (macOS + iOS) screen readers on the top 10 pages
• Automated audits with Lighthouse and axe-core (targets AA)
• Colour-contrast spot checks with the WebAIM contrast tool — extra attention paid to the dark palette

Enforcement

This statement is our own commitment. UK visitors: if we don't respond satisfactorily to an access request, you can raise the issue with the Equality Advisory and Support Service (EASS). EU visitors: your national equality body applies — Equinet directory.