GlossCap

Compliance & Regulation · Published 2026-07-12

Section 508 vs. ADA Title II for L&D teams: complaint mechanisms, enforcement bodies, resolution timelines, and why federal contractors need both frameworks in their caption programme

L&D teams that operate at the intersection of government service and federal contracting routinely receive advice from compliance counsel, accessibility consultants, and LMS vendors that mixes Section 508 of the Rehabilitation Act and ADA Title II into a single “federal accessibility requirement.” They are not the same law, they do not cover the same entities, they are not enforced by the same bodies, complaints under each are filed through different mechanisms, and the resolution processes differ in ways that matter operationally. A state university L&D team has a different compliance obligation than a private company delivering training content under a federal contract — and a state university that also has federal research contracts has obligations under both frameworks that the “just meet WCAG 2.1 AA” advice handles technically but not structurally. This post maps the two frameworks as enforcement systems: who is covered, who enforces, what triggers a complaint, how complaints are investigated, what resolution looks like under each, how the private right of action differs, where Section 504 of the Rehabilitation Act creates a third enforcement track that operates alongside both, and how to prioritise compliance investment when only one framework applies or when both apply but budget is constrained.

TL;DR

Five structural differences that matter for L&D caption compliance planning:

  1. Section 508 covers federal agencies and federal contractors for ICT they procure and use. ADA Title II covers state and local government entities for all their programs and services. The overlap is narrower than most compliance guides suggest: a state university is an ADA Title II entity and also a Section 504 entity (because it receives federal financial assistance), but it is a Section 508 entity only to the extent it holds contracts with federal agencies to supply ICT. Federal grants from NSF, NIH, or the Department of Education do not make a university a “federal contractor” for Section 508 purposes under FAR 39.2.
  2. The enforcement trigger is fundamentally different. Section 508 violations surface primarily through internal audit, procurement compliance review, agency Section 508 coordinator assessments, or IG audits — not primarily through external complaints from users. ADA Title II violations are enforced through external complaints filed by individuals who have been denied access to a public entity’s digital content. This means ADA Title II has a diffuse, unpredictable complaint trigger from your user population, while Section 508 has a more structured, internally-driven audit trigger for contractors.
  3. OCR’s voluntary resolution agreement (VRA) process for ADA Title II cases is a formal, monitored structure with specific captioning requirements and multi-year reporting obligations. Section 508 violations resolved at the agency level typically involve voluntary corrective action plans without the formal VRA monitoring structure that OCR applies to Title II cases. If your institution receives an OCR complaint notice, you are entering the VRA process — not an agency-level corrective action negotiation.
  4. ADA Title II has a clear private right of action for individuals to sue in federal court. Section 508 has a significantly more limited private right of action for non-federal employees. For L&D teams at state universities and public hospital systems, this matters: a learner who cannot access captioned training content can file an OCR complaint AND potentially file a federal lawsuit under ADA Title II. Under Section 508, a private citizen (non-federal employee) generally cannot bring a direct federal lawsuit without first exhausting agency administrative remedies, and courts have split on whether Section 508 alone creates that right at all.
  5. Section 504 of the Rehabilitation Act is the most commonly overlooked enforcement track. It applies to any organisation that receives federal financial assistance — which includes virtually every public university, public school district, public hospital system, and most nonprofits. Section 504 captioning requirements are substantively similar to ADA Title II, enforced by the same OCR offices, and run parallel to Title II for entities covered by both. An organisation that understands ADA Title II enforcement understands Section 504 enforcement — the investigation process, VRA structure, and monitoring requirements are nearly identical.

What each law covers: the legislative foundations

Section 508 of the Rehabilitation Act of 1973 was added by amendment in 1998 and substantially refreshed in 2017 through the ICT (Information and Communications Technology) Accessibility Standards. The 2017 refresh incorporated WCAG 2.0 Level AA as the technical standard for web content and defined covered “electronic and information technology” broadly to include software, hardware, telecommunications products, video and multimedia products, and web-based information. The statutory requirement applies to federal agencies in their procurement and use of ICT, and extends to federal contractors and subcontractors through the Federal Acquisition Regulation (FAR Part 39.2), which requires that ICT acquired through contracts meet the Section 508 technical standards.

For L&D context: a training video produced by or for a federal agency and a web-based LMS procured by a federal agency are both ICT subject to Section 508. A federal contractor who is paid to develop training content for a federal agency must deliver that content at Section 508 standards. A training software vendor whose product is purchased by a federal agency must provide a Voluntary Product Accessibility Template (VPAT) documenting how the product meets the Section 508 technical requirements.

ADA Title II was enacted as part of the Americans with Disabilities Act of 1990. Title II covers all programs, services, and activities of state and local government entities. The statute itself does not specify technical standards for digital content, but the Department of Justice published a final rule on April 24, 2024 — which became enforceable on April 24, 2026 for entities serving populations over 50,000 — establishing WCAG 2.1 Level AA as the technical standard for web content and mobile applications. For captioning specifically, the rule enforces WCAG 2.1 AA Success Criteria 1.2.2 (Captions: Prerecorded) and 1.2.4 (Captions: Live) across all digital content that a state or local government entity makes available to the public and to its employees.

The coverage scope is critically different. Section 508 is procurement-focused: it governs what federal agencies buy and what federal contractors deliver. ADA Title II is program-focused: it governs all programs and services of state and local government entities, regardless of how the content was produced or procured. A state university’s Moodle LMS is covered by ADA Title II because the university is a state entity, not because Moodle was procured with Section 508 requirements. The compliance obligation runs from the university’s ADA Title II status, not from a procurement specification.

For the requirements-side comparison of what each framework requires technically, the US caption compliance matrix maps Section 508, ADA Title II, and WCAG 2.1 AA requirements side by side. This post focuses on the enforcement and complaint structure — not what is required, but how violations are detected, investigated, and resolved.

Enforcement body structure: who is responsible for each law

Understanding the enforcement body structure is the first step to understanding how complaints flow and what investigations look like. The two frameworks have distinct enforcement architectures with limited overlap.

Section 508 enforcement architecture

Section 508 enforcement does not have a single centralised enforcement agency with complaint jurisdiction the way ADA Title II does. Instead, enforcement is distributed across several overlapping mechanisms:

Access Board (U.S. Architectural and Transportation Barriers Compliance Board): The Access Board develops and maintains the ICT Accessibility Standards that define what “accessible” means under Section 508. It is a standards body, not an enforcement body. Compliance failures under Section 508 are not filed with the Access Board.

GSA IT Accessibility Office: The General Services Administration operates Section508.gov, maintains the VPAT framework, conducts accessibility assessments, and provides guidance to federal agencies on Section 508 compliance. GSA does not receive or investigate individual complaints about specific ICT products or training content. Its role is policy development, capacity building, and tools provision for federal agencies.

Agency Section 508 Coordinators: Every federal agency must designate a Section 508 Coordinator responsible for the agency’s ICT accessibility programme. The Section 508 Coordinator manages internal procurement requirements (ensuring that IT acquisitions include Section 508 language and that VPAT review is part of procurement evaluation), manages the agency’s internal accessibility grievance process, and coordinates remediation plans when Section 508 violations are identified. For federal employees who encounter inaccessible ICT — including inaccessible training content on the agency’s LMS — the first point of contact is the agency’s Section 508 Coordinator or the agency’s disability accommodation process.

Department of Justice, Civil Rights Division: DOJ has oversight authority for Section 508 compliance across the federal government. DOJ can investigate federal agencies for systemic Section 508 non-compliance and can require corrective action. In practice, DOJ involvement in Section 508 enforcement has focused on large-scale systemic issues (agency-wide inaccessible IT systems) rather than individual training video complaints. DOJ also enforces ADA Title II, which creates some overlap for entities subject to both.

Inspector General offices: Federal agency IG offices can audit Section 508 compliance as part of broader IT management audits. IG findings about Section 508 non-compliance can trigger agency-level corrective action requirements. For L&D content, IG audits typically focus on enterprise systems (LMS, video platforms, intranet) rather than individual course captions — but a finding that an agency-wide LMS is not accessible can encompass all caption content on that platform.

ADA Title II enforcement architecture

ADA Title II enforcement is more centralised and more clearly complaint-driven, with two primary enforcement bodies and a private litigation pathway:

Department of Education, Office for Civil Rights (DOE/OCR): OCR has jurisdiction over educational institutions that receive federal financial assistance — which includes all public universities, K-12 school districts, and community colleges. OCR also enforces Section 504 of the Rehabilitation Act for these entities. A complaint about captioning at a public university is almost always filed with DOE/OCR. OCR investigates the complaint, determines whether a violation exists, and negotiates a voluntary resolution agreement if a violation is found. The OCR investigation process for captioning cases is described in detail in the ADA Title II enforcement reality check post.

Department of Justice, Civil Rights Division: DOJ has complementary jurisdiction with OCR for state and local government entities. DOJ tends to focus on non-educational public entities (county governments, state courts, public transit agencies, state agencies) and on large systemic enforcement actions against state-level systems (state university systems, state agency networks). DOJ can initiate investigations proactively without receiving an individual complaint — a power OCR also has but uses less frequently. DOJ resolution typically takes the form of a settlement agreement or consent decree rather than a VRA, and the terms tend to be more prescriptive than OCR VRAs.

Private litigation: Individuals with disabilities can bring private civil lawsuits under ADA Title II in federal district court. This pathway does not require prior OCR complaint filing, though OCR complaint filing often precedes litigation. Successful private plaintiffs can obtain compensatory damages (if intentional discrimination is shown), injunctive relief, and attorneys’ fees. Private litigation risk is concentrated among organisations that have received accommodation requests they did not respond to adequately, have received OCR complaints that put them on notice of a violation, or serve user populations that include active disability rights advocates.

Section 504 enforcement architecture (the third track)

Section 504 of the Rehabilitation Act prohibits discrimination on the basis of disability in any program or activity receiving federal financial assistance. For captioning, Section 504 requires that electronic and information technology used in programs receiving federal assistance be accessible to individuals with disabilities. The technical requirements under Section 504 align with WCAG 2.1 AA for covered entities, making the requirements substantively similar to ADA Title II.

Section 504 enforcement is handled by OCR offices in each federal department that provides financial assistance: DOE/OCR for education programs, HHS/OCR for health programs, DOT for transportation programs, USDA for agricultural programs, and so on. For L&D teams in higher education and healthcare, DOE/OCR and HHS/OCR are the relevant enforcers. A public hospital system is covered by HHS/OCR under Section 504 (receives Medicare and Medicaid funding) AND by DOE/OCR under ADA Title II if it is a government entity. These enforcement tracks run in parallel, not in sequence.

The practical consequence for complaint handling: a complaint about inaccessible training captions at a public teaching hospital might appropriately be filed with DOE/OCR (ADA Title II, as a state entity), HHS/OCR (Section 504, as a Medicare/Medicaid recipient), or both. Both agencies have jurisdiction. Both can investigate. Both can require a VRA. An institution that settles an OCR complaint with one agency is not necessarily protected from a separate complaint to the other.

Complaint mechanisms: how violations surface under each framework

The mechanism by which a compliance failure becomes an enforcement action is one of the most practically significant differences between Section 508 and ADA Title II. The enforcement trigger determines who can initiate a complaint, what the complaint process looks like, and what the first notice of a compliance problem looks like to an L&D team.

How Section 508 violations surface

Federal employee accessibility complaints: A federal employee who has a disability and cannot access an ICT system — including a training LMS or specific training video — can file an accommodation request under the Rehabilitation Act. The process typically runs through the agency’s reasonable accommodation coordinator (for accommodation requests) or the Section 508 Coordinator (for systemic ICT accessibility complaints). The agency has a legal obligation to provide an accessible alternative if the ICT is not Section 508-compliant. For L&D specifically, this means a federal employee who cannot access a captioned training video can request an alternative format, and the agency must provide one within a reasonable time. If the agency fails to do so, the employee can escalate to the EEOC (for discrimination claims) or file directly with DOJ. Most L&D teams at federal agencies encounter Section 508 obligations through this pathway: an accommodation request that reveals an uncaptioned or inadequately captioned training course.

Procurement compliance review: Section 508 requirements must be included in federal procurement specifications (under FAR 39.2). During procurement, agencies are required to review VPATs submitted by vendors and evaluate whether the product meets Section 508 standards. If a vendor submits a VPAT with significant gaps in captioning accessibility and the agency proceeds with procurement, both the agency (for accepting non-compliant ICT) and the contractor (for supplying it) may have compliance exposure. For contractors, the VPAT is essentially the compliance certification: a VPAT that misrepresents the product’s accessibility can expose the contractor to False Claims Act liability if the contract was a federal contract.

IG and Section 508 program reviews: Federal agency IGs conduct periodic reviews of IT systems and IT management practices, including Section 508 compliance. An IG finding that an agency’s LMS has systemic captioning failures can generate a corrective action requirement and a congressional report. For federal agency internal L&D teams, IG findings are the most significant systemic enforcement trigger. These are not individual-complaint-driven — they represent programmatic reviews of the agency’s entire ICT accessibility portfolio.

Contractor audit and cure notice: If a federal contracting officer determines that a contractor’s ICT deliverable does not meet the Section 508 requirements specified in the contract, the officer can issue a cure notice requiring remediation within a specified period. For L&D content deliverables (training videos, eLearning modules, LMS implementations), a cure notice might specify that caption files must be provided or that caption accuracy must meet the Section 508 technical standard within 30 days. Failure to cure within the specified period can result in contract termination for cause.

How ADA Title II violations surface

Individual OCR complaint (primary pathway): Any person — employee, student, community member, or disability advocate — who has been denied access to a public entity’s digital content can file a complaint with OCR. For captioning, the complaint basis is typically that training, educational, or public-information video content is uncaptioned or has inadequate captions, making it inaccessible to a deaf or hard-of-hearing person. OCR receives the complaint, determines whether it has jurisdiction and whether the complaint raises an issue that warrants investigation, and if it accepts the complaint, notifies the entity and begins the investigation process. The entity typically receives a document request within 30–45 days of OCR accepting the complaint.

The triggering event for an individual OCR complaint is a specific person encountering inaccessible content. This makes the enforcement trigger diffuse and unpredictable from the public entity’s perspective: any video in the institution’s digital library that lacks adequate captions is a potential complaint trigger every time someone with a hearing disability accesses it. An institution with a 10,000-video training library that is 80% captioned has roughly 2,000 potential complaint triggers at any given time.

DOJ proactive investigation: DOJ can investigate public entities for ADA Title II compliance proactively, without receiving an individual complaint. In practice, DOJ proactive investigations of captioning compliance have focused on large state university systems and state agencies where the scale of non-compliance affects a significant population of students or employees with disabilities. State systems with 20,000+ students or employees are the primary DOJ investigation targets. For most mid-market L&D operations, the realistic enforcement pathway is OCR complaint, not DOJ proactive investigation — but a DOJ investigation, if it occurs, results in a settlement agreement rather than a VRA, with more prescriptive requirements and typically longer monitoring periods.

Private civil litigation: A learner with a hearing disability who cannot access a required training course and whose accommodation request has not been addressed in a reasonable time can file a federal lawsuit directly under ADA Title II. Successful litigation requires showing that the public entity failed to provide equal access and that the failure was not justified by an undue burden defence. For L&D specifically, cases have involved universities failing to provide captioned lecture recordings to enrolled students with hearing disabilities. The combination of a documented accommodation request, a documented failure to provide adequate captions within a reasonable time, and evidence that the institution had the resources to caption the content has been sufficient for courts to find liability. See the compliance post on ADA Title II training video compliance actions for case-level examples.

Pattern-or-practice complaints: OCR and DOJ both accept complaints that describe a pattern of inaccessibility rather than a single incident. A disability services coordinator at a public university who has observed that new courses consistently lack captions for the first several weeks of a semester, or an accessibility advocate who has documented that a state agency’s training library contains hundreds of uncaptioned videos, can file a complaint describing the pattern. Pattern complaints tend to generate broader investigations than single-incident complaints and are more likely to result in systemwide VRA requirements rather than a narrow remediation order.

The critical difference in enforcement trigger orientation

The structural implication of these different complaint mechanisms is that Section 508 compliance and ADA Title II compliance require different internal monitoring orientations. Section 508 compliance is primarily managed proactively through procurement specifications and contract management: ensuring that ICT deliverables include proper VPATs, that procurement language requires Section 508 compliance, and that accommodation requests from federal employees are handled promptly. The primary risk is systemic (an IG finding) or contractual (a cure notice), and both are addressed through internal programme management.

ADA Title II compliance is primarily managed defensively through content quality: ensuring that every accessible digital content item has adequate captions, that accommodation requests from learners with disabilities are handled within documented timelines, and that the institution can demonstrate a written policy and a remediation programme to OCR if an external complaint arrives. The primary risk is a complaint from a user — which is unpredictable in timing and source, and which triggers an investigation that the institution learns about via OCR notice, not through internal programme review.

Coverage map: which framework applies to your organisation

Before allocating compliance effort, L&D teams need to identify which frameworks actually apply to their organisation. The answer is more nuanced than the “just be WCAG 2.1 AA compliant and you’re covered” advice suggests, because coverage determines which enforcement body has jurisdiction and which complaint mechanism poses the primary risk.

Federal agencies (internal L&D teams)

Federal agencies are subject to Section 508 for all ICT they use and procure. ADA Title II does not apply to federal agencies — it applies to state and local government entities, not the federal government itself. Federal employees’ disability accommodation rights come from the Rehabilitation Act (Section 501 for federal employees) and the ADA Title I employment provisions, not from ADA Title II. For federal agency L&D teams, the operative framework is Section 508, and the enforcement mechanism is the agency’s internal Section 508 programme.

Private companies with federal contracts

A private company that holds a federal contract to supply ICT — including training content, LMS platforms, video learning tools — is subject to Section 508 for the ICT it supplies under that contract. The scope of the obligation is contract-specific: the company must ensure that the ICT it delivers under the contract meets the Section 508 technical standards specified in the contract. The company’s internal training library, its employee onboarding videos, and its internal LMS are not covered by Section 508 unless the company is also a federal agency (which private companies are not) or unless those internal systems are covered by ADA Title I employment discrimination requirements (which do not specify WCAG 2.1 AA for private employers at this time).

For L&D teams at private federal contractors: the Section 508 obligation applies to the training and educational ICT you deliver to federal agencies as contract deliverables. It does not automatically extend to your internal training programmes, which are governed by ADA Title I employment obligations (a different standard with no WCAG technical requirements imposed by federal regulation as of mid-2026 for private employers).

State universities and public higher education

This is the entity type where the multi-framework complexity is highest, and where most compliance advice oversimplifies. A state university typically has obligations under three frameworks simultaneously, with different scopes and enforcement bodies for each:

ADA Title II (DOJ rule, WCAG 2.1 AA): Applies because the university is a state entity. Covers all programs, services, and activities — including all employee training, all student-facing educational content, all public-information content, and all web-based services. The April 24, 2026 compliance deadline applied to universities serving populations over 50,000. Enforced by DOE/OCR (for educational programs) and DOJ (systemwide). Complaint trigger: individual OCR complaint from any student, employee, or community member who has been denied access to digital content.

Section 504 of the Rehabilitation Act (OCR enforcement): Applies because the university receives federal financial assistance — federal student aid (Title IV), federal research grants (NSF, NIH, DOE), federal work-study funds. Section 504 requirements for digital accessibility are substantively identical to ADA Title II requirements. Enforced by DOE/OCR under the same process as ADA Title II complaints. For most purposes, OCR investigates Section 504 and ADA Title II simultaneously in a single investigation and resolves both through a single VRA.

Section 508 of the Rehabilitation Act (FAR 39.2, procurement-specific): Applies only if the university holds contracts (not grants) with federal agencies that specify ICT deliverables subject to FAR 39.2. This is less common than many compliance officers assume. A federal research grant to a university professor does not create a Section 508 obligation — grants are not contracts for FAR purposes. A sponsored research agreement in which the university delivers a training system or educational technology product to a federal agency as a contract deliverable can create a Section 508 obligation for that specific deliverable. The distinction matters: Section 508 obligation via FAR is limited to the ICT under the contract, not the university’s entire digital content library.

For L&D teams at state universities: the broadest and most operationally important framework is ADA Title II (and Section 504 in parallel). The Section 508 obligation, where it exists, covers a narrower and more specific set of ICT deliverables under federal contracts. Compliance investment should be sized accordingly.

K-12 public school districts

K-12 public school districts are ADA Title II entities (state/local government entities) and Section 504 entities (receive federal financial assistance under IDEA, Title I, Title III, etc.). The analysis is the same as for state universities but with the additional IDEA overlay for students with disabilities. For L&D specifically: teacher training, staff compliance training, and professional development videos are covered under ADA Title II and Section 504. IDEA compliance for student-facing content is a separate analysis. The K-12 caption compliance post covers the student-facing obligations in detail; this post focuses on the staff L&D side of the K-12 compliance picture.

Public hospital systems

Public hospital systems are ADA Title II entities (owned and operated by state or local government), Section 504 entities (receive Medicare and Medicaid funding through HHS), and potentially HIPAA-covered entities. The Section 504 obligation runs from HHS/OCR (through Medicare and Medicaid), not DOE/OCR. A captioning complaint at a public hospital may be filed with DOE/OCR (ADA Title II, as a state entity) or HHS/OCR (Section 504, as a Medicare/Medicaid provider) or both. Both agencies have jurisdiction and both can open investigations. The resolution obligations under each are substantively similar but the signatories, reporting relationships, and monitoring contacts differ.

Nonprofits

Nonprofits that receive federal financial assistance — which includes the vast majority of nonprofit educational organisations, social service organisations, and healthcare organisations — are subject to Section 504. They are not ADA Title II entities (not state or local government). They are not Section 508 entities (not federal agencies or federal ICT contractors unless they hold specific ICT contracts). Their primary L&D captioning obligation runs from Section 504 as enforced by the relevant federal agency’s OCR office. The caption compliance obligations are substantively the same as ADA Title II WCAG 2.1 AA requirements, but the enforcement body and complaint pathway differ. The state caption compliance law overlay addresses additional state-level requirements that apply to nonprofits in certain states.

The state university federal contractor: why both frameworks matter

The entity type where Section 508 and ADA Title II most clearly coexist — creating operationally distinct compliance obligations — is the research university that is simultaneously a state entity (ADA Title II) and a federal contractor for sponsored research and technology transfer (Section 508).

A large state research university might have:

For the L&D team, this means:

Internal training library (employee onboarding, HR compliance training, professional development): ADA Title II and Section 504. Compliance standard: WCAG 2.1 AA (99%+ caption accuracy per OCR resolution practice). Enforcement body: DOE/OCR. Complaint trigger: individual employee complaint to OCR. Documentation: written caption policy, vendor accuracy SLA (see the caption accuracy standards and vendor contracts post for SLA clause guidance), accommodation request log, remediation schedule.

Student-facing academic content (lecture captures, recorded instructional videos, online course modules): ADA Title II and Section 504. Same standard, enforcement, and documentation as internal training. For university L&D teams that also produce academic content, the same captioning programme covers both employee and student content.

Training content delivered to federal agency clients under contract: Section 508. Compliance standard: Section 508 ICT standards (which incorporate WCAG 2.0 Level AA for web content; the 2017 refresh did not adopt WCAG 2.1). Note that WCAG 2.0 AA and WCAG 2.1 AA have the same captioning success criteria (SC 1.2.2 and 1.2.4), so the technical requirements for captions are identical under both. The difference matters more for other accessibility requirements (colour contrast, reflow, etc.) than for captioning. Enforcement body: contracting officer, agency Section 508 coordinator, potentially IG. Complaint trigger: federal employee accommodation request, procurement audit, IG review, or VPAT review during contract renewal.

The practical implication: a state university that delivers training content to both internal audiences and federal agency clients needs two compliance tracks that run on different timetables and use different documentation. The ADA Title II track requires a written policy, accommodation request process, accuracy standard, and OCR-ready documentation package. The Section 508 track requires VPATs for specific deliverables, contract-specific accessibility specifications, and a process for responding to agency Section 508 coordinator inquiries about specific deliverables. These tracks have substantial overlap (the captioning accuracy requirements are effectively identical), but the compliance documentation, the responsible party for each, and the response protocols for enforcement inquiries differ.

The caption compliance self-assessment checklist includes a framework identification question as the first step of the assessment precisely because the compliance domains that matter most — and the documentation required — differ depending on which frameworks apply to the organisation.

Resolution structures: what happens after a violation is found

If a compliance failure reaches the point of formal enforcement action, the resolution process under Section 508 and ADA Title II is structurally different in ways that affect the operational burden on L&D teams for years after the initial finding.

Section 508 resolution structures

Agency-level corrective action plan: The most common resolution for Section 508 violations at federal agencies. When an IG audit or Section 508 programme review finds that an agency’s ICT is non-compliant, the agency prepares a corrective action plan that identifies the non-compliant ICT, establishes a remediation timeline, and assigns responsible parties. For L&D content, this typically means the agency’s training programme must produce compliant captions for a specified backlog of videos within a defined period (often 6–12 months for high-priority content, 18–24 months for lower-priority backlog). There is typically no external monitoring body — the agency reports progress internally and to the IG, not to an outside enforcement agency with a formal VRA relationship.

Procurement cure notice: For federal contractor violations, the contracting officer issues a cure notice specifying what must be corrected and within what timeframe. The contractor must either cure the deficiency, demonstrate that the contract specification was met (by providing a revised VPAT and supporting documentation), or demonstrate that the claimed deficiency is incorrect. If the contractor cures the deficiency within the cure period, the contract continues. If not, the contract may be terminated for default. For caption-specific cure notices, the contractor typically must provide an updated caption file and a revised VPAT documenting the correction.

Exceptions and equivalent facilitation: Section 508 allows federal agencies to document exceptions for specific ICT where compliance would impose an undue burden or fundamentally alter the programme. An exception does not eliminate the obligation — the agency must still provide accessible content through an alternative means. For L&D, an agency that documents an exception for a specific legacy training video must still provide an accessible alternative to any employee who needs one. Exceptions are document-intensive to justify and require agency CIO or Section 508 Coordinator approval, making them a high-overhead option for individual content items.

Limited monitoring obligation: Unlike OCR VRAs for ADA Title II, Section 508 corrective action plans at the agency level do not typically create a multi-year external monitoring obligation with quarterly reporting to an outside enforcement body. The agency reports internally; the IG may follow up in a subsequent review cycle. For L&D teams at federal agencies, this means the operational burden after a Section 508 finding is concentrated in the initial remediation period rather than spread across a 2–3 year monitoring relationship with an external enforcement agency.

ADA Title II resolution structures

OCR voluntary resolution agreement (VRA): The primary resolution mechanism for ADA Title II captioning violations. When OCR investigates a captioning complaint and finds a violation, OCR offers the entity the opportunity to enter into a VRA that specifies the corrective actions the entity will take and the monitoring obligations the entity will meet. OCR does not litigate — it resolves through VRAs or refers to DOJ if the entity refuses to negotiate. For captioning-specific VRAs, the standard elements include: a written caption policy within 60–90 days, an accuracy standard (typically 99%), a back-catalogue remediation schedule by risk category, a vendor contract amendment to include accuracy provisions within 90–180 days, an accommodation request process, staff training, and quarterly compliance reports to OCR for two to three years.

The monitoring period and quarterly reporting obligation are the operationally significant consequence of a VRA. An L&D team that has signed a VRA must maintain ongoing compliance documentation — caption completion rates, accuracy audit results, accommodation request logs, vendor compliance reports — and report this documentation to OCR every quarter for the duration of the agreement. Failing to meet VRA reporting requirements can trigger a DOJ referral for enforcement of the agreement. The annual caption programme review and the governance policy template are designed to create the documentation infrastructure that makes VRA compliance sustainable as a programme function rather than an emergency project.

Letter of finding with no violation: If OCR investigates a complaint and determines that no violation occurred — either because the content was accessible, because the entity provided an adequate alternative, or because the complaint raised an issue that does not rise to a violation — OCR issues a letter of finding dismissing the complaint. A letter of finding does not create a VRA or monitoring obligation. It does create a record that OCR investigated the institution for captioning accessibility, which becomes relevant context if a subsequent complaint is filed.

DOJ settlement agreement: For large state systems and entities where OCR has referred the matter to DOJ, resolution takes the form of a settlement agreement that is more comprehensive than a VRA and may be enforceable by a federal court (consent decree). DOJ settlements for captioning accessibility typically require: systemwide remediation across all digital content properties, specific remediation timelines for identified backlog categories, ongoing accessibility officer staffing at a specified level, annual independent accessibility audits, and reporting to DOJ for five or more years. For mid-market L&D operations (50–5,000-employee organisations), DOJ settlement is not the typical enforcement pathway — but state university system offices, large urban school districts, and state health departments are the scale of entity that DOJ has historically targeted for comprehensive settlement agreements on digital accessibility.

Private litigation settlement or judgment: If a private plaintiff files a lawsuit and the case reaches settlement or trial, the resolution may include monetary damages, injunctive relief, and attorneys’ fees. For captioning cases, courts have awarded damages in the range of tens of thousands of dollars for individual plaintiffs in cases with documented accommodation request failures. Class action or pattern-and-practice litigation on behalf of a larger group of affected users can reach substantially higher settlement values. Private litigation settlements typically include injunctive relief requirements similar to VRA corrective action terms, plus monitoring provisions for a defined period. Unlike VRAs, private litigation settlements are court-enforceable and violations can be addressed through contempt proceedings.

The comparison in practical terms: Section 508 resolution is faster, less monitored, and involves fewer external reporting obligations than ADA Title II resolution. An agency-level corrective action plan might have a 12–18 month remediation timeline and no external reporting obligation. An OCR VRA for ADA Title II has a similar remediation timeline plus two to three years of quarterly reporting to OCR. For L&D teams, the implication is that an ADA Title II enforcement outcome commits the programme to an ongoing compliance reporting infrastructure for years after the initial violation — which makes proactive compliance investment significantly more cost-effective than post-complaint remediation.

Private right of action: who can sue whom under which law

The private right of action question — can an individual bring a lawsuit directly against an entity for an accessibility violation? — is the highest-stakes structural difference between Section 508 and ADA Title II for L&D teams at public entities.

ADA Title II private right of action

ADA Title II has a well-established private right of action. Individuals with disabilities can bring federal lawsuits against state and local government entities for violation of Title II rights without prior administrative exhaustion (though OCR complaint filing is the more common pathway). Successful plaintiffs can obtain: injunctive relief (requiring the entity to make specific content accessible or implement a captioning programme), compensatory damages (if intentional discrimination is shown), and attorneys’ fees. The intentional discrimination standard for damages requires showing that the entity knew of the discrimination and failed to act — a standard met, in practice, by demonstrating that the entity received an accommodation request it did not address, received an OCR complaint it ignored, or had a written policy acknowledging captioning obligations and failed to implement it.

For L&D teams: a learner with a hearing disability who requests captions for a required training course, does not receive adequate captions within a reasonable time, and suffers a concrete harm (cannot complete required training, loses a job assignment, falls behind in a required curriculum) has a plausible ADA Title II claim. The documentation record created by the accommodation request process and the caption programme timeline commitment are the primary factors that distinguish a defensible response from one that exposes the institution to damages liability. The accommodation request handling guidance in the CART captioning for live training post and the compliance self-assessment checklist both address this specific vulnerability.

Section 508 private right of action

Section 508 private right of action is significantly more limited and courts have not resolved the question uniformly. The law distinguishes between federal employees and the general public:

Federal employees: Federal employees with disabilities who are denied access to ICT in their workplace have the ability to exhaust the federal agency’s Section 508 grievance and accommodation process, and — if that process fails — to bring a lawsuit under the Rehabilitation Act. The lawsuit basis is typically Section 504 or Section 501 of the Rehabilitation Act (which creates explicit employment discrimination causes of action for federal agencies), not Section 508 directly. In this sense, federal employee ICT accessibility complaints are structurally similar to private employee ADA Title I claims, processed through the EEOC framework.

Private citizens (non-federal employees): Courts have split on whether Section 508 creates a private right of action for private citizens who encounter inaccessible ICT from a federal contractor or from a federal agency. Several circuits have found that Section 508 does not create an independent private right of action for private citizens — that the enforcement mechanism is administrative (agency Section 508 coordinator complaint, IG referral, DOJ oversight) rather than judicial for non-employees. The Access Board and GSA lack enforcement authority. A private citizen who encounters an inaccessible federal contractor ICT product generally cannot bring a Section 508 lawsuit directly; their remedies run through the agency’s accessibility process or through Section 504 if federal financial assistance is involved.

The practical implication: the litigation risk for an L&D team at a state university or public entity comes primarily from ADA Title II and Section 504, not from Section 508. The private right of action is broader, the damages are more accessible (intentional discrimination standard achievable through accommodation request records), and the disability rights litigation bar has significantly more experience with Title II claims than with Section 508 claims. Section 508 litigation exposure for L&D teams is primarily limited to the False Claims Act exposure of misrepresenting ICT accessibility in a federal procurement — a risk that is managed through accurate VPAT completion rather than through programme-level caption compliance.

Section 504 private right of action

Section 504 has a clear private right of action for individuals with disabilities who are excluded from or denied benefits of a program or activity receiving federal financial assistance. This right of action is the primary litigation pathway for disability rights cases against universities, nonprofits, and healthcare organisations — because these entities are typically Section 504 entities even if they are not ADA Title II entities (for private universities) or ADA Title I entities (for employment). The standard and damages framework for Section 504 litigation is substantively similar to ADA Title II — injunctive relief is available without showing intentional discrimination; damages require the intentional discrimination showing. For L&D teams at educational institutions, Section 504 and ADA Title II litigation risks are operationally identical to manage, which is why compliance frameworks for both are typically handled through the same programme documentation and accommodation request infrastructure.

Documentation requirements for each enforcement pathway

The documentation an institution needs to defend against an enforcement action differs based on which framework applies and which enforcement body is involved. Understanding the documentation requirements for each pathway is essential for building a caption programme that can demonstrate compliance — not just achieve it.

Section 508 compliance documentation

For federal contractors delivering ICT under a federal contract, the primary compliance documentation is:

ADA Title II and Section 504 compliance documentation

For state and local government entities and Section 504-covered organisations, the documentation that matters in an OCR investigation is substantially more comprehensive and covers the programme level rather than individual deliverables:

The documentation scope for ADA Title II and Section 504 is significantly broader than for Section 508 because the enforcement body (OCR) is evaluating the institution’s entire programme, not a specific contractual deliverable. An OCR investigation is programmatic in scope: it assesses whether the institution has a real compliance programme, not just whether specific content meets a technical standard. This is why the caption compliance programme build guide emphasises programme infrastructure — policy, vendor contract, audit process, accommodation workflow — rather than technical checklist completion.

Eight framework-confusion failure modes for L&D teams

The practical consequence of conflating Section 508 and ADA Title II is a series of predictable compliance gaps. The eight most common ones:

Failure mode 1: Treating WCAG 2.1 AA compliance as equivalent to Section 508 compliance

WCAG 2.1 AA is the technical standard for ADA Title II web content compliance. Section 508 incorporates WCAG 2.0 AA (the 2017 refresh) — not WCAG 2.1. For captioning success criteria (SC 1.2.2 and 1.2.4), WCAG 2.0 and WCAG 2.1 are identical, so meeting WCAG 2.1 AA for captions does satisfy the Section 508 captioning requirement. But for other accessibility requirements (SC 1.3.4 Orientation, SC 1.4.10 Reflow, SC 1.4.11 Non-text Contrast, SC 2.5.3 Label in Name, and others added in WCAG 2.1), the gap between WCAG 2.0 and 2.1 is substantive. An LMS vendor who claims Section 508 compliance based on a WCAG 2.0 AA self-assessment may not be WCAG 2.1 AA compliant. For captions specifically, the standards converge — but the conflation matters for the broader ICT accessibility picture.

Failure mode 2: Assuming federal grants make you a Section 508 entity

Federal grants from NSF, NIH, DOE, and other agencies do not make your organisation a federal contractor subject to Section 508 via FAR 39.2. Grants and contracts are legally distinct. Section 504 of the Rehabilitation Act applies to grant recipients, not Section 508. A university that receives $50 million in annual federal research grants is a Section 504 entity, not a Section 508 entity for its internal training content. The Section 508 obligation via FAR applies only when the organisation holds a procurement contract with a federal agency that specifies ICT deliverables.

Failure mode 3: Focusing Section 508 compliance efforts on internal training instead of federal deliverables

For private federal contractors, Section 508 compliance obligation runs from the ICT they deliver to federal agencies, not from their internal training programmes. A defence contractor that invests heavily in Section 508-compliant internal employee training — captioning every internal training video to Section 508 standards — while delivering uncaptioned training content to a DoD client under a contract is getting the compliance effort backwards. The operative Section 508 obligation is the federal deliverable, not the internal programme.

Failure mode 4: Missing the Section 504 track at public hospitals

Public hospital systems that are ADA Title II entities (because they are government-owned) and Section 504 entities (because they receive Medicare and Medicaid funding) have two active OCR enforcement tracks: DOE/OCR for the Title II side and HHS/OCR for the Section 504 side. A VRA negotiated with DOE/OCR does not resolve a pending complaint with HHS/OCR. The documentation and compliance programme infrastructure required by each is substantively identical, but the compliance relationships, reporting contacts, and monitoring periods run on separate timelines. An L&D compliance programme at a public hospital should be structured to satisfy both OCR offices, even though most compliance audits and complaint investigations come through one channel at a time.

Failure mode 5: Prioritising Section 508 compliance over ADA Title II compliance at a state university

For state universities that have federal research contracts, the temptation is to build the compliance programme around the Section 508 deliverable requirements because those are contractually specified and audited by contracting officers. The ADA Title II obligation — covering the entire training library for all employees and students — is broader but feels less immediate because it is complaint-driven rather than contract-driven. The enforcement data does not support this prioritisation. ADA Title II and Section 504 complaints about university captioning compliance have far outnumbered Section 508 procurement compliance actions in the 2020–2026 period. The complaint trigger is the student or employee with a disability who cannot access training content — not the contracting officer reviewing a VPAT.

Failure mode 6: Neglecting to document the framework analysis

An L&D team that has done the work of identifying which frameworks apply, which enforcement bodies have jurisdiction, and which documentation is required — but has not recorded that analysis — cannot demonstrate that it understands its compliance obligations. OCR investigations evaluate not just whether content is accessible but whether the institution has a functioning compliance programme. An institution that can articulate in writing which law applies to which content, which enforcement body has jurisdiction, and what the compliance standard requires for each category is demonstrating programme competency. An institution that answers “we try to be accessible” without a framework analysis is demonstrating the opposite.

Failure mode 7: Assuming ADA Title II applies only to public-facing content

ADA Title II covers all programs, services, and activities of state and local government entities — including employee training and internal operational content. The DOJ final rule does not exempt internal-only content. A public university’s mandatory employee training on HR policy, safety procedures, and compliance obligations is covered by ADA Title II for employees with hearing disabilities. A K-12 district’s professional development videos for teachers are covered. The “our training videos are internal only” argument is not a defence under ADA Title II.

Failure mode 8: Treating a VRA completion as compliance programme completion

When an OCR VRA monitoring period ends — typically after two to three years of quarterly reporting — the compliance obligation under ADA Title II does not end. The VRA monitoring period is OCR’s mechanism for verifying that the institution has corrected the specific violation and built the infrastructure to maintain compliance. After the VRA closes, the institution’s ADA Title II obligations continue indefinitely: new content must be captioned, accuracy standards must be maintained, accommodation requests must be handled, and vendor contracts must continue to include the accuracy provisions required under the VRA. An institution that dismantles its compliance programme after VRA closure is at higher litigation risk than one that had no VRA — because the institution-on-notice standard for intentional discrimination damages applies: it cannot argue it did not know about the captioning obligation after receiving an OCR complaint and signing a VRA.

Prioritisation framework: compliance investment when budget is constrained

For L&D teams operating under budget pressure, the framework identification exercise above informs where to concentrate compliance investment. The prioritisation logic differs based on entity type and enforcement risk profile.

Step 1: Identify which frameworks apply

Use the entity type analysis above to determine whether you are subject to Section 508 (federal agency or federal ICT contractor), ADA Title II (state/local government entity), Section 504 (federal financial assistance recipient), or some combination. Most L&D teams in public higher education and K-12 are primarily ADA Title II and Section 504 entities. Most L&D teams in private companies with federal contracts are primarily Section 508 entities for the contract deliverables and ADA Title I entities for their internal programmes (with no WCAG technical requirement imposed by federal regulation at this time for private employers).

Step 2: Identify highest-risk enforcement pathway

For ADA Title II and Section 504 entities, the highest-risk enforcement pathway is the individual OCR complaint from an employee or student with a hearing disability who cannot access required training content. The risk is concentrated in:

For Section 508 entities, the highest-risk enforcement pathway is a VPAT review or agency Section 508 coordinator inquiry about a specific federal deliverable. The risk is concentrated in ICT deliverables under active federal contracts, especially those with upcoming VPAT renewal or contract extension reviews.

Step 3: Prioritise the compliance self-assessment by risk category

The four-domain compliance assessment from the compliance self-assessment checklist maps directly to enforcement risk: Domain 1 (policy and governance) and Domain 3 (vendor accountability) are the documentation domains that OCR evaluates first in a complaint investigation. Domain 2 (content coverage) and Domain 4 (live events and accommodation) are the operational domains where individual enforcement triggers originate. Budget-constrained programmes should invest in Domain 1 first (written policy, VRA-defensible governance) because the documentation gap is the most visible to OCR and the least expensive to close.

Step 4: Sequence remediation by enforcement exposure, not content volume

A 10,000-video back-catalogue remediation sequenced by content recency alone (newest first) is not the same as one sequenced by enforcement exposure. Content that is actively assigned to learners with disabilities, content that received accommodation requests in the past 18 months, and required compliance training content have higher enforcement exposure than legacy library content. The sequencing framework in the L&D captioning maturity model provides a five-level rubric for assessing and sequencing remediation investment against compliance risk rather than content volume.

Step 5: Ensure vendor contracts reflect the correct framework requirements

For ADA Title II and Section 504 compliance, vendor contracts must include an accuracy standard (99% per OCR resolution practice), a measurement methodology, audit rights, and remediation provisions. For Section 508 compliance on federal contract deliverables, vendor contracts must specify which ICT accessibility standard applies (Section 508 2017 refresh incorporating WCAG 2.0 AA), require VPAT documentation from subcontractors, and give the prime contractor the right to audit subcontractor accessibility claims before deliverable submission. These are different contract requirements serving different compliance tracks — an organisation with both tracks needs both contract provisions. The vendor contract framework from the audit rights and examination evidence post is primarily designed for the ADA Title II track; for Section 508-specific contract language, the GSA Section508.gov VPAT framework provides the applicable structure.

For the typical mid-market L&D team

A 500-employee public university L&D team with a $150,000 annual training budget and one accessibility coordinator is not going to implement both a full Section 508 procurement compliance programme and a full ADA Title II VRA-ready documentation programme simultaneously. The realistic prioritisation:

  1. Write the caption policy (low cost, high OCR value, addresses the most common VRA gap)
  2. Audit vendor contract for accuracy SLA and add provisions if missing (addresses the second-most common OCR gap)
  3. Caption all required training courses assigned in the current academic or fiscal year (addresses highest-exposure individual complaint risk)
  4. Set up an accommodation request log (addresses the documentation gap that turns an OCR complaint into a damages case)
  5. For federal contract ICT deliverables: complete accurate VPATs and deliver with the content (addresses Section 508 specific risk)

This sequence addresses the highest-probability enforcement risk first at the lowest per-action cost, while laying the documentary foundation that makes subsequent compliance investment cumulative rather than reactive.

How state-law overlay affects both frameworks

State accessibility laws add a third enforcement layer that runs independently of Section 508 and ADA Title II. Several states have enacted their own digital accessibility laws or have broadly interpreted state disability rights statutes to cover web and digital content in ways that go beyond federal requirements. For L&D teams in these states, a training video that meets WCAG 2.1 AA captioning requirements and is compliant with ADA Title II may still face state-level enforcement under a stricter state accessibility standard or through a state human rights commission complaint process.

California’s Unruh Civil Rights Act, New York’s Human Rights Law, and Massachusetts’ disability access requirements have all been applied to digital content in recent years. State enforcement mechanisms vary: California allows private lawsuits under Unruh with statutory damages of $4,000 per violation regardless of actual harm — a damages structure that has driven significant private litigation activity against public and private entities that operate in California. The state caption compliance law guide covers the major state-level overlay requirements for L&D teams that operate across state boundaries.

For entities subject to both federal and state enforcement frameworks, the compliance hierarchy is: meet the most restrictive applicable standard (usually WCAG 2.1 AA at 99%+ accuracy), document compliance under the most demanding documentation framework (usually the ADA Title II OCR-ready package), and maintain state-specific complaint response procedures where state enforcement is active. Meeting the federal standard does not automatically satisfy every state standard, and state enforcement can proceed independently of and simultaneously with federal OCR proceedings.

Interaction with the financial services and healthcare regulatory overlays

For L&D teams in financial services and healthcare, Section 508 and ADA Title II interact with sector-specific regulatory frameworks that create additional captioning obligations running on parallel tracks.

Financial services: FINRA Rule 3110 requires broker-dealers to supervise training materials. SEC no-action letters and examination guidance treat employee training records as compliance records subject to books-and-records requirements. For captioning, this means that a broker-dealer’s training video must not only meet ADA Title I employment accommodation requirements (if applicable) but must also ensure that training records — including caption files if captions are part of the training record — are retained under the applicable retention schedule. The financial services captioning guide addresses the FINRA and SEC overlay in detail.

Healthcare: CMS Conditions of Participation for hospital systems require adequate training of clinical staff. Joint Commission standards for staff competency assessment create training documentation requirements. For a public hospital system (ADA Title II entity) that also receives Medicare and Medicaid (Section 504 via HHS), training content must satisfy both the accessibility requirements (WCAG 2.1 AA captions) and the sector-specific training documentation requirements (CMS CoP, Joint Commission). The caption programme that meets the OCR compliance standard also feeds the training documentation infrastructure that satisfies the regulatory compliance standard — if the caption files are retained as part of the training record and linked to the completion tracking system.

The multi-framework interaction does not typically create conflicting requirements for captioning — WCAG 2.1 AA is the technical floor for caption quality under virtually every applicable framework, and 99% accuracy is the de facto compliance threshold under both federal and state enforcement practice. What it creates is a documentation and retention requirement that multiplies: the same caption file must satisfy the accessibility compliance record, the training documentation record, the litigation hold scope, and the regulatory audit trail simultaneously. Designing the caption programme workflow to produce documentation that satisfies all applicable frameworks at once is more efficient than maintaining separate documentation systems for each.

Practical application: the university that received a complaint notice

To make the framework distinction concrete, consider how the response differs for a state research university that receives a complaint notice and a federal contractor that receives a Section 508 audit inquiry on the same day — both related to captioning of training videos.

The state university and the OCR complaint notice: The university receives an OCR letter notifying it that a complaint has been filed by a graduate student with a hearing disability who was unable to access required laboratory safety training videos. OCR’s jurisdiction: ADA Title II (state entity) and Section 504 (receives federal financial assistance). OCR will request: the written caption policy, vendor contracts with accuracy provisions, accommodation request records for the past 18–24 months, a sample of captioned training content, staff training records on captioning obligations. The university should immediately: identify all captioned and uncaptioned content assigned to the complainant’s programme, locate the accommodation request records related to this student, engage legal counsel to review the OCR response letter, pull the written caption policy (or draft one immediately if none exists), and review vendor contracts for accuracy provisions. The response window is 30–45 days from the date of OCR’s document request. See the ADA Title II enforcement reality check for the full OCR investigation response protocol.

The federal contractor and the Section 508 audit inquiry: A defence contractor receives a cure notice from the contracting officer on a DoD training content contract, citing that a training module delivered three months earlier does not have accessible captions (the auto-generated captions are present but fail the Section 508 accuracy standard for technical content). The contractor has 30 days to cure. The response: identify the affected module, assess the caption quality against the Section 508 ICT standard, engage the caption vendor to produce corrected caption files, produce a revised VPAT reflecting the corrected captioning, and deliver both to the contracting officer with documentation of the accuracy assessment. If the contractor cannot cure within 30 days, it must negotiate an extension with the contracting officer and document the remediation plan. The contractor should also review its quality control process for caption delivery on federal contracts — a second cure notice on the same contract is a meaningful contract performance risk.

The two responses draw on similar technical capabilities — both require accurate caption files — but the institutional response, the documentation required, and the enforcement body being addressed are entirely different. An L&D programme that has conflated the two frameworks and built a single compliance process will find that the process is neither OCR-ready nor contracting-officer-ready when both are needed simultaneously.

FAQ

Our institution receives NSF and NIH grants. Does that make us a federal contractor under Section 508?

No. Federal grants and federal contracts are legally distinct. Section 508 of the Rehabilitation Act applies to federal agencies and to federal contractors under FAR Part 39.2 — where “contractor” refers to organisations that hold procurement contracts with federal agencies for ICT. Federal research grants from NSF, NIH, the Department of Education, and other agencies do not create an FAR-governed contractor relationship. As a grant recipient, your organisation is subject to Section 504 of the Rehabilitation Act — which requires programmes receiving federal financial assistance to be accessible — but not to Section 508 via FAR. The distinction matters primarily for how you document compliance (VPATs for Section 508; programme documentation for Section 504) and which enforcement body has jurisdiction (agency Section 508 coordinator and contracting officer for Section 508; OCR for Section 504).

We have a DoD research contract. Does Section 508 apply to all our internal training videos?

No. Section 508 via FAR 39.2 applies to the ICT you supply to the federal agency under that specific contract — not to your institution’s entire training library. If the DoD contract specifies delivery of training materials or ICT systems, those deliverables must meet Section 508 standards. Your internal employee training, onboarding programmes, and professional development content are governed by ADA Title II (because you are a state entity) and Section 504 (because you receive federal financial assistance) — not by Section 508 via the DoD contract. The compliance obligation for internal training runs from your status as a state entity, not from the DoD contract.

What is the difference between filing an OCR complaint and filing a Section 508 complaint?

An OCR complaint about captioning at a public entity (state university, K-12 district, public hospital) is filed under ADA Title II or Section 504. The complaint goes to the relevant OCR office (DOE/OCR for education, HHS/OCR for health), which investigates, determines whether a violation occurred, and negotiates a VRA if a violation is found. A Section 508 complaint is filed through the agency’s Section 508 coordinator or with DOJ, and relates to ICT that a federal agency uses or a federal contractor supplies. The investigation, resolution structure, and documentation requested are different. In practice, most captioning complaints that L&D teams encounter in education and healthcare are OCR complaints under ADA Title II or Section 504, not Section 508 complaints. The OCR process is the one to plan for.

Can someone sue us under Section 508 the same way they can under ADA Title II?

Not in the same way. ADA Title II has a well-established private right of action: individuals with disabilities can file federal lawsuits against state and local government entities for Title II violations, with potential for compensatory damages and attorneys’ fees. Section 508 has a more limited private right of action for non-federal employees. Courts have generally held that private citizens (non-federal employees) cannot bring direct Section 508 lawsuits without exhausting agency administrative remedies, and some circuits have held that Section 508 does not create a private right of action for private citizens at all. The litigation risk from captioning accessibility deficiencies for L&D teams at public entities comes primarily from ADA Title II and Section 504 — not from Section 508.

We meet WCAG 2.1 AA for all our captioning. Does that satisfy both Section 508 and ADA Title II?

For captioning specifically, yes — the captioning success criteria (SC 1.2.2 and 1.2.4) are the same in WCAG 2.0 and WCAG 2.1, so meeting WCAG 2.1 AA for captions satisfies the Section 508 captioning technical standard and the ADA Title II captioning technical standard simultaneously. However, “technical compliance” and “enforcement readiness” are different. Meeting WCAG 2.1 AA caption accuracy in your content does not, by itself, satisfy the documentation requirements that OCR evaluates in an ADA Title II investigation: written policy, vendor contract with accuracy provisions, accommodation request log, and back-catalogue remediation plan. Technical compliance without programme documentation is still an enforcement gap.

We received an OCR complaint notice. How do we know if it is a Section 504 or ADA Title II complaint?

OCR’s complaint notice letter will identify the legal basis for the complaint. Most complaints about captioning at public educational institutions cite both ADA Title II and Section 504, because OCR enforces both and the remedy for a violation under either is the same. Practically, for an L&D team responding to an OCR complaint notice, the distinction between Section 504 and ADA Title II does not change the response: the documentation OCR requests, the VRA structure if a violation is found, and the monitoring obligations are substantively identical under both. If OCR cites Section 508 in the complaint (which is uncommon in educational institution cases), that would indicate a different enforcement track requiring legal counsel to assess the specific procurement or contractual context.

Our training videos are only shown to our own employees. Does ADA Title II still apply?

Yes, for state and local government entities. ADA Title II covers all programs, services, and activities of state and local government entities — including internal employee training. The DOJ final rule does not exempt internal-only content. A state university’s mandatory employee compliance training, HR orientation, and professional development content are covered by ADA Title II for employees with hearing disabilities, the same as student-facing content. The obligation to provide accessible training extends to everyone the institution trains, not just to external audiences or students. This is one of the most common misconceptions about the scope of ADA Title II coverage for L&D content.

Next steps in this series

This post covers the enforcement structure and complaint mechanisms for Section 508 and ADA Title II. The adjacent posts in the compliance cluster build out the programme components that enforcement preparedness requires:

Other tools from the factory: