Accessibility

Our target

EduQan aims to meet WCAG 2.2 Level AA. This is a commitment, not a marketing line, so this page states what currently meets it and what does not.

What is in place

• Every route is keyboard operable, with a visible focus indicator and a logical tab order.
• Every page has one h1 and no skipped heading levels, checked on every route automatically.
• Every route is usable down to a 360px viewport with no sideways scrolling.
• Form errors are announced to a screen reader, listed above the form, and each links to the field

that caused it. Focus moves to that summary when a submission fails.

• Loading states announce themselves rather than changing the page in silence.
• Reordering controls — for example the order of courses in a learning path — work from the keyboard

and announce the new position.

• prefers-reduced-motion is respected across the site.
• Empty screens always offer a way onward; none is a dead end.

Known exceptions

Colour contrast on some secondary text and on the primary button. Our brand orange gives white text a contrast ratio of 2.83:1 where AA requires 4.5:1. This is a real failure and it is open. It affects the main call-to-action on several pages and a number of secondary labels. We are working through it as a design-system change rather than a patch, because a partial fix would leave the site inconsistent. If it makes something unusable for you, tell us and we will prioritise that surface.

Video captions. The catalogue is currently text-based. Where video is introduced, captions and a transcript will be part of publishing it, not a follow-up.

PDF documents. Certificates are rendered as web pages rather than PDFs, so they carry the page's own accessibility. Any PDF we add later will be tagged.

Testing

Automated checks run on every change: heading structure, viewport width, keyboard operability, announced form errors and contrast. Automated testing finds roughly a third of accessibility failures, so it is a floor rather than a certificate. It does not judge whether an error message is useful or whether alternative text describes the picture.

Telling us about a barrier

If any part of EduQan is difficult or impossible for you to use, please contact us and say what you were trying to do. We will reply within five working days, and we will tell you either when it will be fixed or how to get the same outcome another way in the meantime. (rewritten)