Accessibility Statement

Conformance Status

This platform aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. WCAG 2.1 defines requirements for designers and developers to improve accessibility for people with disabilities across four principles: perceivable, operable, understandable, and robust.

Keyboard Navigation

All interactive elements—including links, buttons, form controls, quiz answers, drag-and-drop exercises, and navigation menus—are fully operable via keyboard. We use semantic HTML elements and maintain a logical tab order throughout every page. Focus indicators are clearly visible with high-contrast outlines. Interactive targets meet the minimum 48×48 pixel touch target size recommendation.

• Tab and Shift+Tab navigate between interactive elements.
• Enter and Space activate buttons and links.
• Escape closes modals, drawers, and dropdown menus.
• Arrow keys navigate within composite widgets like quiz option groups.

Screen Reader Support

Pages are structured with proper heading hierarchies, landmark regions (navigation, main, complementary), and ARIA attributes where native semantics are insufficient. Form inputs include associated labels. Dynamic content changes—such as toast notifications, quiz feedback, and progress updates—are announced via ARIA live regions. Images carry descriptive alt text, and decorative elements are hidden from assistive technology using aria-hidden="true".

Colour Contrast

Text and interactive elements maintain a minimum contrast ratio of 4.5:1 against their backgrounds, meeting WCAG 2.1 AA requirements. Large text (18pt or 14pt bold) maintains at least 3:1. We avoid conveying information through colour alone; icons, patterns, and text labels supplement colour-coded states such as quiz correctness and completion status.

Motion and Animation

Animations respect the user's operating system preference for reduced motion via the prefers-reduced-motion media query. When reduced motion is requested, transitions are minimised to opacity changes without movement.

Reporting Accessibility Issues

We welcome feedback on accessibility. If you encounter barriers while using this platform, please report them so we can address them promptly. Include the URL of the affected page, a description of the issue, the assistive technology and browser you were using, and steps to reproduce the problem.

Open an issue on our public source code repository or contact the maintainers directly. We aim to respond to accessibility reports within five business days and resolve confirmed issues in the next release cycle.