Accessibility for eLearning Courses, Programs and Resources: A Practical Guide

Accessibility for eLearning Courses, Programs and Resources: a practical start

This guide explains what accessibility means for eLearning courses, programmes and resources, and gives concrete steps you can use today. It uses WCAG 2.1 and 2.2 principles and focuses on common learning formats: HTML pages, LMS content, PDFs, video and quizzes.

Quick practical checklist

• Use semantic headings and lists so screen readers follow the content flow.
• Provide captions and a transcript for every recorded video. Add audio description when visuals carry essential meaning.
• Ensure keyboard access: all controls reachable and operable with Tab, Shift+Tab, Enter and Space.
• Check colour contrast: 4.5:1 for normal text, 3:1 for large text.
• Add clear alt text to images and meaningful link text that names the destination or action.
• Label form fields and expose inline error messages programmatically.
• Test with an automated tool, then with keyboard and a screen reader (NVDA or VoiceOver).

What standards and laws apply

WCAG basics

WCAG 2.1 and 2.2 set the technical success criteria most organisations use. They are organised into levels: A, AA and AAA. Many public bodies and institutions aim for AA conformance. Key measurable items include contrast ratios, keyboard operability, meaningful text alternatives and programmatic labelling.

UK legal context

In the UK, the Equality Act 2010 requires reasonable adjustments for disabled learners. Public sector bodies must follow the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations which reference WCAG. Use this guide as practical steps rather than legal advice. If you need legal certainty, consult in-house legal or an accessibility specialist.

Design and authoring: concrete techniques

Focus on predictable structure, consistent controls and plain language. Below are the common content types and what to do for each.

HTML pages and LMS content

• Headings: use H2, H3, H4 in order. Do not skip heading levels.
• Navigation: include a visible “skip to content” link and ensure consistent menus across pages.
• Links: make link text descriptive. Avoid “click here” and similar phrases.
• Keyboard: ensure every interactive element can be reached and operated by keyboard. Visible focus must be present.
• ARIA: prefer native HTML elements. Use ARIA only to add semantics that native elements cannot provide.

Images, charts and alt text

• Decorative images: mark as decorative so screen readers ignore them.
• Informative images: write concise alt text that conveys the information users need to understand the learning point.
• Complex graphics: provide a longer description nearby or a linked long description.
• Charts: include a text summary of the key insights and, if possible, a data table alternative.

Video and audio

• Pre-recorded video: captions, a human-checked transcript and player controls that work with keyboard and screen readers.
• Audio description: add when visual content conveys essential information not in the audio.
• Live sessions: provide live captioning where possible and a follow-up transcript. Offer reasonable adjustments when live captions are not available.

Documents (Word, PowerPoint, PDF)

Create accessible source documents before export. Tagged PDF output is only reliable when the source is structured correctly.

• Use built-in heading styles in Word and PowerPoint.
• Export to PDF with tags turned on and check tag order in the PDF editor.
• Check reading order, alt text on images and table headers.

Quizzes, assessments and interactive activities

• Avoid time limits or provide adjustments and override options.
• Make drag-and-drop alternatives available, such as select-and-match.
• Label questions and inputs programmatically so screen readers announce context.
• Provide clear feedback on submission and make errors explicit and descriptive.

Testing and validation

Combine automated tools with manual checks and real user testing. Automation highlights many issues but misses focus order, meaning of alt text and usability problems.

Automated tools

• Run an automated scanner such as Axe, WAVE or Lighthouse to find common issues.
• Use a colour contrast checker for text and UI elements.

Manual checks: keyboard and screen reader

Do these tests on representative lessons, not every file.

1. Keyboard walkthrough: try to navigate to every interactive control with Tab and operate it with Enter or Space. Ensure visible focus and logical order.
2. Screen reader test: open a page in NVDA (Windows) or VoiceOver (Mac or iOS). Verify heading order, link announcements and form field labels.
3. Mobile test: test with TalkBack on Android or VoiceOver on iOS for touch navigation and gestures.

User testing

Recruit learners with a range of needs where possible. Structured scenarios that reflect typical tasks reveal real barriers. Even one or two users will find problems that tools miss.

Common mistakes and how to fix them

Below are recurring problems seen in eLearning and step-by-step fixes you can apply quickly.

1. Inaccessible PDFs — quick fix workflow

1. Start with the source document. Apply built-in heading styles and alt text for images.
2. Export to PDF with tags enabled. In Word use the Export > Create PDF/XPS option with tagging.
3. Open the PDF in a PDF editor and inspect tag order, headings and alt text. Fix reading order where needed.
4. Run an accessibility checker in the PDF editor and fix reported issues. Re-test with a screen reader.

2. Video without captions or transcript

If captions are missing, add a human-checked caption file (SRT or VTT). Provide a transcript with speaker labels. For essential visual information, add audio description or a descriptive transcript.

3. Keyboard traps and invisible focus

Fix by ensuring all scripts and widgets follow the WAI-ARIA Authoring Practices keyboard patterns. Add visible CSS focus styles and test focus order from top to bottom.

Prioritise fixes: a simple impact vs effort matrix

Use this quick method to decide what to fix first.

• High impact, low effort: add alt text, captions, proper headings, label form fields. Do these first.
• High impact, higher effort: fix major keyboard traps, restructure content, convert untagged PDFs to tagged PDFs.
• Low impact, low effort: decorative touch-ups. Do these when time allows.

Document decisions and track fixes in your LMS or content backlog so updates do not get lost.

Procurement, governance and ownership

Make accessibility part of content production and procurement. Key actions:

• Publish an accessibility statement that explains conformance level and known issues.
• Collect Accessibility Conformance Reports or VPATs from vendors for platforms and third-party tools.
• Include accessibility acceptance criteria in contracts and test before final sign-off.
• Train authors on simple practices: headings, alt text, captions and labelled forms.

Practical next steps (first 30 days)

1. Pick three representative courses. Run automated scans and do a keyboard + screen reader test on each.
2. Fix the top three high-impact, low-effort issues you find and document the changes.
3. Publish or update your accessibility statement and add a clear contact for accessibility requests.

Further reading and tools

• WCAG 2.1 and WCAG 2.2 success criteria (refer to the W3C site for the official text).
• Automated tools: Axe, WAVE, Lighthouse. Manual tools: NVDA, VoiceOver, TalkBack.
• Consider an external audit or user testing with people who have lived experience of accessibility needs.

Accessibility for eLearning courses, programmes and resources is a continuous practice. Start with the checklist, test early, and prioritise fixes that give learners the most benefit.