Accessibility statement

We aim to meet WCAG 2.2 levels A and AA for core journeys: course catalog, lesson reading, code examples, exercises, assessments, verification and the dashboard. Automated checks are a starting point; we also test with a keyboard and screen reader.

The current frontend includes:

• Semantic landmarks, a skip link and a logical heading outline on every page.
• Visible focus styles and full keyboard access to navigation, dialogs and form controls.
• Light and dark themes with token-based colours, designed for contrast rather than inverted by filter.
• Reduced-motion support, including animated sections and confetti celebrations.
• Labelled form controls, error messages announced to assistive technology, and no placeholder-only labels.
• Text alternatives for images and icons, and code blocks that remain readable when syntax colours are unavailable.
• Right-to-left readiness through logical CSS properties and direction-aware layout primitives.

The browser code editor is keyboard operable. Screen reader support depends on the assistive technology in use; report any barrier so we can reproduce it. Some live previews run inside an isolated iframe and may not inherit your browser extensions or font preferences.

Accessibility adjustments for assessments are reviewed individually. Contact access@edubyte.tech before starting an attempt if you need an adjustment under the published assessment policy.

If you encounter a barrier, tell us the page, the assistive technology and what happened. Email access@edubyte.tech. We will acknowledge the report and give you a realistic timeline for review.