Accessibility statement

We aim to meet WCAG 2.2 to level AA. Most of the site meets that standard today, and the parts that don't are listed under non-accessible content. We designed in the register of the GOV.UK Design System and the DfE Design Manual: a calm, high-contrast palette, large readable text (18px base), visible keyboard focus, and full keyboard operability.

Accessibility is checked automatically on every change, not just at audit time. Two gates run in our continuous integration before any change can ship:

• Colour contrast. Every colour-token pair in the design system is re-checked against the WCAG AA contrast ratios (4.5:1 for text, 3:1 for large text and interface components), in both light and dark mode. A pair that drops below AA fails the build.
• Accessibility linting. The interface code is linted with eslint-plugin-jsx-a11y, which catches missing image text, unlabelled form fields, invalid ARIA and similar issues automatically.

We also build on accessible foundations: semantic headings, a “skip to content” link, a clear keyboard-focus indicator shown only when navigating by keyboard, support for prefers-reduced-motion, touch targets of at least 44px, and full light/dark theming that respects the operating-system setting.

We know about the following issues and are working to fix them. The content below is not yet fully accessible:

• Mathematical notation. Some questions render maths that may not always be announced ideally by every screen reader. We are reviewing the maths rendering for better assistive-technology support.

We're always trying to improve. If you find a problem that isn't listed here, or you need information in a different format, please tell us - contact [email protected] and describe the problem and the page it's on. We aim to reply within five working days.

GCSEwiz is committed to making its website accessible, in line with good practice for digital services used by schools and families.

This website is partially compliant with WCAG 2.2 level AA, because of the non-accessible content listed above.

The design tokens are tested automatically for colour contrast on every change, and the interface is checked with automated accessibility linting in continuous integration. These are complemented by manual keyboard and screen-reader checks of the core journeys (practice, exam mode, and progress reports).