English only
Education Accessibility Requirements
Prioritize core learning journeys like enrollment, course content, assessments, and student support so more learners can complete tasks without barriers.
For course-to-assessment validation, use User Journey Scanning to test enrollment, content, and submission flows end to end, or use the Chrome extension for quick checks in authoring and QA.
Education evidence to prioritize
- Eurostat reports that 16% of individuals in the EU completed an online course in 2025.
- Eurostat reports that 17% of individuals in the EU used online tools to interact with educators or fellow learners in 2025.
- Eurostat reports that 26% of individuals in the EU encountered difficulties when using the internet in 2025.
- Under EN 301 549 and WCAG 2.1 AA, educational web and document experiences should be perceivable, operable, understandable, and robust for assistive technology users.
What is required
- The European Accessibility Act became enforceable on 28 June 2025.
- EN 301 549 is the core technical standard used in EU accessibility programs.
- For web content, WCAG 2.1 Level AA remains the practical baseline under EN 301 549.
Journeys to prioritize first
- Discover and enroll in courses or programs
- Access lessons, media, and downloadable materials
- Complete quizzes, assignments, and timed assessments
- Submit forms for accommodations and student services
- Contact instructors or support and track follow-up
Where teams need a deeper accessibility review
Enrollment and learner onboarding
Enrollment often spans course search, eligibility checks, account creation, payment, consent, and orientation steps. A single inaccessible gate can stop a learner before instruction even begins.
- Test program search, start dates, and application requirements for clear structure and filter usability.
- Review registration forms, consent checkboxes, and prerequisite messaging for keyboard flow and error recovery.
- Confirm onboarding steps explain what happens next without relying on hidden hover help or visual progress alone.
Course delivery, media, and navigation
Learning platforms usually mix page content, documents, embedded video, discussion tools, and navigation sidebars. The deeper issue is consistency across modules so learners do not relearn the interface every week.
- Check module navigation, accordion menus, and lesson progression controls for consistent headings and current-state cues.
- Validate captions, transcripts, audio descriptions, and player controls across lecture media.
- Test downloadable worksheets, slide decks, and reading packs as accessible documents, not just downloadable assets.
Assessment, timing, and accommodations
Assessment flows must support students who use assistive technology, need extra time, or rely on non-mouse interaction. Timing, auto-save, and submission confirmation are common failure points.
- Review quiz navigation, question grouping, and answer status so learners always know where they are.
- Verify timers, pause controls, and timeout warnings support accommodation workflows.
- Check assignment upload, submission confirmation, and resubmission states for clear feedback and accessible file handling.
Data-driven WCAG checks
| Priority area | Why it matters | What to track |
|---|
| Learning content structure and navigation | Weak structure makes modules harder to navigate with assistive technology. | Screen-reader and keyboard navigation success across course templates |
| Assessment flow and error recovery | Form and timing issues can block submissions and affect grades. | Assessment completion and error-recovery rate |
| Media alternatives | Missing captions, transcripts, or descriptions can exclude learners. | Caption/transcript coverage for course media |
| Document and handout accessibility | Inaccessible PDFs and handouts can block coursework and accommodations. | Accessible document pass rate |
PDF compliance
If your customer journey includes statements, contracts, invoices, or policy documents, validate PDFs as part of the same release process. WCAG and EN 301 549 expectations apply to document access, not only web pages.
Scan PDF complianceNext step
Run a scan on your highest-risk journeys, then use platform workflows to track fixes over time.
Last updated: 2 September 2026
