Blog

Hands on a keyboard navigating an online course for Section 508 compliance
A practical guide for government and enterprise training teams.
Share this blog
Accessibility

Section 508 Compliance for E-Learning: What Government and Enterprise Training Teams Need to Know

A training course can look polished and still lock out part of its audience. For example, a learner who uses a keyboard, a screen reader, or captions may hit a wall in the first lesson. Section 508 compliance for e-learning is about removing those walls before the course launches.

This guide covers who Section 508 applies to and the requirements that matter most in a course. It also shows how to audit one before launch. It is written for government and enterprise training teams, and it is general information, not legal advice.

Training team reviewing an e-learning course for Section 508 compliance

Section 508 compliance for e-learning starts with testing the course as a learner would use it.

What Section 508 Means for E-Learning

Section 508 requires US federal agencies to make their electronic and information technology accessible. Employees and members of the public with disabilities must get access comparable to everyone else’s. As a result, online courses that an agency develops or buys fall within its scope.

Key facts
  • The current standards took effect on January 18, 2018, and align with WCAG 2.0.
  • Its technical standards incorporate WCAG 2.0 Level AA for web and other electronic content.
  • Federal acquisition rules require agencies to build these standards into their purchase requirements. Vendors therefore meet them through their contracts.

In practice, an agency buying a course or a learning platform will often ask the vendor for evidence of conformance. Likewise, enterprise teams that sell to agencies face the same questions. Many other organizations adopt WCAG on their own, because it gives a clear standard to build against.

Six Requirements for Section 508 Compliance for E-Learning

WCAG 2.0 contains many success criteria. However, these six come up in almost every course review.

1.2.2 Captions (Prerecorded) · Level A

Videos with sound need captions. Captions carry dialogue, speaker identity, and meaningful sound effects, so learners who cannot hear the audio still follow the lesson.

1.2.3 and 1.2.5 Audio Description · Level A and AA

When a video shows information that the narration never says, learners who cannot see it need that information in another form. A narrated description or a full text alternative can serve.

2.1.1 Keyboard · Level A

Every control must work without a mouse. Menus, quiz answers, and interactive activities all need a keyboard path, and focus must never get trapped.

1.1.1 Non-text Content · Level A

Images, charts, and diagrams need text alternatives that serve the same purpose. A diagram that teaches a process needs a description of that process.

2.2.1 Timing Adjustable · Level A

Timed quizzes and auto-advancing slides can shut out learners who need more time. Let users turn off, adjust, or extend the limit.

1.4.3 Contrast (Minimum) · Level AA

Text needs enough contrast against its background, at a ratio of at least 4.5 to 1 for normal text. Light gray text on white fails this test.

Where Section 508 Compliance for E-Learning Usually Breaks Down

Most failures trace back to authoring habits, not to bad intent. For example, reviewers tend to find the same problems again and again.

  • Slides exported as flat images. As a result, a screen reader finds nothing to read.
  • Drag-and-drop activities with no keyboard option. Learners who cannot use a mouse cannot finish them.
  • Videos without captions or transcripts. Our guide to audio and video transcription explains how to build the transcript first.
  • Unlabeled buttons and quiz controls. A screen reader announces “button” and nothing more.
  • Hard time limits and auto-advance. Learners lose their place or run out of time.

How to Audit Section 508 Compliance for E-Learning Before Launch

You can catch most serious problems with a short, structured review. Therefore, work through these steps on every course.

  1. List every media item. Note each video, audio clip, image, and downloadable handout.
  2. Use the keyboard only. Complete one full lesson, then one quiz, without touching the mouse.
  3. Run a screen reader. Listen to one lesson from start to finish and write down what is missing.
  4. Check contrast and text size. Zoom the page and confirm nothing overlaps or disappears.
  5. Record the results. Keep a dated log of what passed, what failed, and what you fixed.

That record matters later. If an agency or client asks for evidence, you can share what you tested instead of making a general claim.

Section 508 Compliance for E-Learning in Multiple Languages

However, a course that works in English can break when it is translated. For example, captions and transcripts must exist for every language version. Longer translated text can also overflow buttons and slides. Screen readers need the correct language tag to pronounce each version properly.

For that reason, plan for these issues before translation begins. Our guides to accessible-by-design localization and multimedia localization show how to keep accessibility intact across languages.

Common Questions

Who has to meet Section 508?

Federal agencies must meet it when they develop, buy, maintain, or use electronic and information technology. Vendors generally meet it through the accessibility requirements written into their contracts.

Which version of WCAG does Section 508 use?

The current standards reference WCAG 2.0 Level AA. Also, newer versions such as WCAG 2.2 build on it. Many teams therefore design to the newer version as a stronger target.

Does Section 508 apply to private companies?

It applies directly to federal agencies. A private company usually meets it when it sells to an agency. However, other laws and policies may also apply, so check with legal counsel for your situation.

Can a course be declared fully compliant after one audit?

An audit shows what passed on the day you tested. Courses change, so retest after updates and keep your records current.

Training content going multilingual or into the public sector?

Our team can help you localize course content and keep it accessible in every language.

Talk to Our Team

Related

Blogs

Product team reviewing mobile app accessibility on phones and a laptop
Meeting WCAG 2.2 and Section 508 in mobile apps.
Accessibility
People use screen readers, voice control, and larger text settings on their phones every day. As a result, mobile app accessibility decides whether those users can finish a task or give up on your app. For teams selling to US federal agencies, the stakes are higher. Section 508 sets accessibility requirements for the software those agencies buy, and that includes native mobile apps. This guide explains what Section 508 and WCAG 2.2 expect from an app. It also shows how to test for it before release. Mobile app accessibility starts with testing on a real device. What Section 508 and WCAG 2.2 Mean for Mobile App Accessibility Section 508 is the US law that requires federal agencies to buy accessible information and communication technology. Its technical standards incorporate WCAG 2.0 Level AA. They apply to web content and to other electronic content, such as software and native mobile apps. WCAG 2.2 is the newer version. According to the W3C's overview of WCAG 2.2, it adds nine success criteria and removes one obsolete one. Because it extends the older version, designing to WCAG 2.2 Level AA puts a team in a strong position. However, a buyer may still ask for a…
October 15, 2026
Professional reviewing document accessibility compliance checklist
Translationary's approach: catch the cost before it becomes a claim
Accessibility
In 2025, plaintiffs filed 3,117 website accessibility lawsuits in U.S. federal court — a 27% jump from the year before, and the highest total in three years. Add in state court filings, and the total climbs past 5,000. Nearly half of those cases targeted a repeat defendant — a company already sued once before for the same kind of problem. Most of that litigation traces back to something quietly unglamorous: a PDF without proper tags, a form with no field labels, a document that a screen reader simply can't parse correctly. The cost of inaccessible documents rarely shows up as one dramatic failure. It shows up as a slow accumulation of legal exposure, lost readers, and rework — most of it avoidable at a fraction of the eventual cost. We found a similar pattern when we looked at the real cost of poor localization. Understanding where that cost actually comes from is the first step toward keeping it small. The Legal Cost Is Rising, and It's Not Just Large Companies Web and document accessibility litigation has more than tripled since 2017, according to Seyfarth Shaw's annual tracking of ADA Title III filings. Website accessibility cases alone made up 36% of…
October 2, 2026
Team collaborating on accessible multilingual content with UI overlay icons
Translationary's approach: building accessibility and localization as one
Accessibility
Compliance
Localization
Most teams treat accessibility and localization as two separate projects, run by two different teams, on two different timelines. One group makes sure the product works with a screen reader. Another group makes sure it reads correctly in Spanish, German, and Japanese. They rarely talk to each other — and that's exactly backwards, because accessible localization isn't two problems solved twice. It's one problem, solved once, if you plan for it that way. Why These Are Actually the Same Problem Both accessibility and localization ask the same underlying question: can everyone actually use this, regardless of how they access it? A screen reader user and a non-English-speaking user hit strikingly similar walls when a product lacks flexibility. The same root cause usually explains both: the interface bakes content in directly, instead of pulling it from a structured, adaptable source. Picture a support page with a well-written FAQ. The English version has clean heading structure, proper alt text on screenshots, and good color contrast — it passes an accessibility audit easily. Then the team translates the page into Japanese, and nobody re-checks it. The accessibility work already happened once, so nobody thinks it needs to happen again. But the heading structure…
September 8, 2026