Compliance & Regulation · Published 2026-07-10
ADA Title II enforcement after April 2026: what OCR complaint investigations, voluntary resolution agreements, and DOJ monitoring look like for public entities that missed the captioning deadline
ADA Title II’s digital accessibility requirements became enforceable for state and local government entities on April 24, 2026. That deadline has now passed. For many public universities, public hospital systems, county governments, and K-12 school districts, the honest assessment is that the caption programme was not compliance-ready on that date — video libraries remain partially uncaptioned, accuracy standards are not documented, vendor contracts lack accuracy SLAs, written caption policies do not exist. The question for those organisations is no longer how to prepare for the deadline. It is what enforcement looks like now that the deadline has passed and what actions between now and the arrival of an OCR complaint notice still matter. This post answers that question in operational detail. It covers the OCR complaint investigation process from filing through resolution, the documentation OCR requests in a caption-specific investigation, what voluntary resolution agreements require from public entities found in violation, how DOJ monitoring operates for large public entities and state systems, what the post-deadline complaint filing patterns look like in Q2 2026, and what “good-faith progress” means to an OCR investigator evaluating an organisation that missed the deadline but is visibly working toward compliance.
TL;DR
Five things this post will surface that the pre-deadline action guides do not:
- ADA Title II enforcement is complaint-driven, not audit-driven. OCR does not proactively audit every public entity for caption compliance after the deadline. Enforcement is triggered by a complaint from an individual who has been denied access to digital content. This means the enforcement risk is concentrated among organisations whose audiences include disability advocates, disability services staff, and individuals with disabilities who use digital training content regularly — which describes every public university, public hospital system with mandatory employee training, and county government with online compliance training.
- The OCR investigation document request for caption cases is consistent and predictable. OCR requests: a sample of video content with caption files, the written caption policy (if any), accommodation request records from the past 18–24 months, vendor contracts with accuracy provisions, staff training records on captioning obligations, and any existing remediation plans. An organisation that can produce all of these — even if the caption policy is new and the remediation plan is incomplete — is in a materially different position than an organisation that can produce none of them.
- Voluntary resolution agreements for captioning typically require a written policy within 60 days, a back-catalogue remediation schedule, an accuracy standard of 99%, and quarterly reporting to OCR for two to three years. The monitoring period and reporting obligation are the practical cost of VRA resolution — they require an ongoing compliance infrastructure that most mid-market public entities do not currently have but that the annual review process and the governance policy template make operationally feasible.
- Good-faith progress is a real OCR evaluation criterion, not a technicality. OCR distinguishes between organisations making documented progress toward compliance and organisations that did nothing before and after the deadline. The distinction matters at every stage of the investigation: the initial document review, the determination of whether a VRA is appropriate, the monitoring period length, and the specificity of VRA corrective action requirements. An organisation that had zero documentation on April 24, 2026 but has a written caption policy, a vendor contract with an accuracy SLA, and a remediation plan in place when OCR makes its document request is in a substantially better position than one that still has none of these.
- Public hospital systems face overlapping enforcement from two agencies. DOE/OCR covers public hospitals as employers (ADA Title I, Title II as government entities), but HHS/OCR enforces Section 504 of the Rehabilitation Act, which applies independently of the Title II rule and predates it. A public hospital system that receives a captioning complaint may find that both DOE and HHS have jurisdiction, creating two parallel investigation tracks if the complaint references training materials the hospital is both providing to employees and publishing to the public. The compliance documentation required to satisfy both tracks is substantially the same, but the reporting relationships and VRA signatories differ.
What changed on April 24, 2026
The Department of Justice published its final rule under ADA Title II on April 24, 2024, establishing specific technical standards for digital accessibility — WCAG 2.1 Level AA — for state and local government entities. The compliance deadline for entities with populations over 50,000 was April 24, 2026. Entities with populations under 50,000 have until April 26, 2027.
For captioning specifically, the rule enforces WCAG 2.1 AA Success Criteria 1.2.2 (Captions: Prerecorded) and 1.2.4 (Captions: Live). For prerecorded content, this requires synchronised captions that are accurate, synchronised, complete, and properly positioned. For live events, this requires real-time captioning that meets the same accuracy threshold where technically feasible.
The pre-deadline guidance post (ADA Title II training videos: fix this week) covers the operational steps public entities needed to take before April 24. This post starts where that one ends: the deadline has passed, and the question is what comes next for organisations that were not ready on that date.
It is worth being clear about what “not ready” means in practice. Most public entities with existing caption programmes were not ready in the sense that their programmes had gaps: uncaptioned back-catalogue content, accuracy standards below WCAG 2.1 AA, vendor contracts without documented accuracy SLAs, written policies that were absent or incomplete, and accommodation processes that were informal rather than documented. An entity with this profile is at risk of an OCR complaint finding a violation — but the enforcement pathway is complaint-driven, and the response available to the entity depends on what documentation it can produce when OCR requests it.
For the ADA Title II captions reference overview including scope, covered entities, and technical requirements, that page provides a concise reference. The focus here is post-deadline enforcement mechanics and response strategy.
The three enforcement pathways under ADA Title II
ADA Title II digital accessibility enforcement reaches public entities through three distinct pathways. Understanding which pathway applies in a given situation determines what the investigation looks like, who conducts it, and what resolution options are available.
Pathway 1: OCR complaint investigation (primary)
The primary enforcement pathway is an individual complaint filed with the relevant Office for Civil Rights. For educational institutions — public universities, community colleges, K-12 school districts, public libraries, and public museums — the relevant OCR is within the Department of Education (DOE/OCR). For other public entities — county and municipal governments, public transit authorities, public hospitals and health systems — the relevant OCR is within the Department of Justice (DOJ) or, where Section 504 also applies, the Department of Health and Human Services (HHS/OCR).
A complaint is filed by an individual who has been denied access to or benefit from digital services due to a disability. In the captioning context, this means a Deaf or hard-of-hearing employee, student, or public service recipient who could not access training content, educational videos, public meeting recordings, or other video-format digital services because captions were absent, inaccurate, or inaccessible. The complaint can also be filed by a disability rights organisation, a legal advocacy centre, or an accessibility consultant on behalf of a class of individuals.
There is no private right of action under ADA Title II’s new digital accessibility rule itself, meaning individuals cannot directly sue a public entity for violations of the WCAG 2.1 AA standard. However, individuals can and do file OCR complaints, and OCR can refer non-compliant entities to DOJ for enforcement action. In states with their own disability civil rights laws (California, New York, Illinois), state-level private litigation is possible independently of the federal enforcement pathway.
Pathway 2: DOJ compliance review (proactive)
The DOJ Civil Rights Division can conduct proactive compliance reviews of public entities without a complaint trigger. In practice, DOJ compliance reviews are reserved for large state systems where pattern violations affect large populations: state university systems with multiple campuses, state departments of transportation, large county government systems in major metropolitan areas.
A DOJ compliance review typically follows evidence of a pattern: multiple OCR complaints against entities within the same state system, media coverage of accessibility failures at a prominent public institution, or a disability rights organisation presenting DOJ with documentation of systematic non-compliance across multiple campuses or offices. DOJ reviews are slower-moving than OCR complaint investigations but produce more demanding remediation requirements and longer monitoring periods.
Pathway 3: State AG enforcement and civil litigation
Several states have disability civil rights laws that provide private rights of action and state attorney general enforcement authority. California’s Unruh Civil Rights Act and Disabled Persons Act, New York’s Human Rights Law, and Illinois’s Human Rights Act all permit civil litigation for digital accessibility failures by public entities. The state-level compliance landscape is covered in detail in state caption compliance law beyond ADA. For purposes of this post, the relevant point is that some public entities face state-level enforcement risk in addition to federal OCR risk — and that state enforcement timelines are sometimes faster than federal investigation timelines.
The OCR complaint investigation process: step by step
Understanding the OCR complaint investigation process in operational detail matters because the steps available to a public entity to improve its compliance position depend on where in that process the investigation currently is. An entity that takes action before OCR makes its document request is in a different position than one that acts after. The sequence below describes a typical DOE/OCR caption investigation; the DOJ process for non-educational public entities follows the same general framework with different timelines.
Step 1: Complaint filing
A complainant files with DOE/OCR online, by mail, or in person at a regional OCR office. Complaints must be filed within 180 days of the alleged discriminatory act. In a captioning context, the 180-day clock runs from the last date the complainant attempted to access a specific piece of captioned content and found it inaccessible — not from the April 24, 2026 compliance deadline. This means complaints arising from accessibility failures that occurred before the deadline are also actionable if filed within 180 days.
Complaints can be filed anonymously with third-party advocates (disability rights centres, law school disability clinics, DREDF, NFB, NAD) acting on behalf of a class. A single complaint from a disability advocacy organisation referencing systemic caption failures across a large video library is treated as a systemic complaint and typically triggers a broader investigation scope than a single individual’s complaint about a specific video.
Step 2: OCR acknowledgment and jurisdiction check
OCR acknowledges receipt within approximately 10 business days and conducts an initial jurisdiction check: Is the entity a recipient of federal financial assistance? Is the complaint within the 180-day window? Does it state a viable claim under Title II or Section 504? Most public universities, community colleges, K-12 districts, and public institutions receive federal financial assistance through grant programmes, Title IV student aid, or federal contracts, satisfying the jurisdiction requirement.
OCR notifies the respondent institution that a complaint has been filed. This notification is the first formal indication the institution has that an investigation has begun. The notification letter describes the complaint in general terms without identifying the complainant, states OCR’s jurisdiction, and requests a written response within a specified period (typically 20–30 business days).
Step 3: OCR document request
The document request is the operationally significant step for a public entity. OCR sends a detailed data request specifying what documentation the institution must provide. For a captioning complaint, a typical OCR document request includes:
- A representative sample of video content and the corresponding caption files, typically selected by OCR from the specific content types referenced in the complaint (LMS training modules, public meeting recordings, faculty lecture videos, or departmental training videos)
- The institution’s written digital accessibility policy, including any caption-specific policy or standard
- Accommodation request records for the past 18–24 months, specifically requests from Deaf and hard-of-hearing individuals for captioned content or real-time captioning services
- Vendor contracts for any captioning services used, including terms relating to accuracy guarantees, turnaround time, and audit rights
- Staff training records documenting what training content producers and L&D staff have received on captioning requirements and how those requirements apply to their content
- Any existing remediation plans for back-catalogue content or identified caption accuracy deficiencies
- Technical implementation documentation: how captions are delivered in the LMS, what caption format is used, and any technical logs from the delivery system
- Contact information for the institution’s 504/ADA coordinator and documentation of that coordinator’s role and responsibilities
The document request deadline is usually 20–30 business days from the request letter. Extensions are available by written request to OCR before the deadline, and OCR typically grants reasonable extensions for organisations demonstrating active good-faith compliance work. Requests for extension are themselves a piece of evidence: an institution that asks for an extension because it is actively compiling documentation of its remediation programme is communicating something different from one that asks for an extension because it has not yet started assembling materials.
The enterprise LMS caption audit methodology covers how to systematically pull together the video sample, caption file inventory, and accuracy data that OCR will request before the document request deadline, which is materially earlier than the actual investigation conclusion.
Step 4: OCR investigation
After receiving the institution’s document response, OCR investigators review the submitted materials, may conduct follow-up interviews with institutional representatives and (separately) with complainants, and may request additional documentation. The investigation typically takes 90 to 180 days from the initial complaint filing, though complex systemic complaints affecting large institutions or state systems can take 12 to 18 months.
During the investigation, OCR investigators assess: (1) whether the captioned content meets WCAG 2.1 AA accuracy requirements (99%+ accuracy, synchronisation, completeness); (2) whether coverage is adequate (all pre-recorded training, educational, and informational content with audio); (3) whether live events are captioned via CART or an equivalent real-time service; (4) whether the accommodation process is documented and responsive; and (5) whether the institution has a governance structure (written policy, coordinator responsibility, remediation plan) that makes ongoing compliance operationally sustainable.
Step 5: Resolution
OCR investigations resolve in one of three ways:
Voluntary Resolution Agreement (VRA): OCR and the institution negotiate a binding agreement specifying corrective actions, timelines, and a monitoring period. This is the most common resolution for cases where OCR finds evidence of non-compliance. A VRA is not an admission of liability but is legally binding — failure to comply with VRA terms can result in DOJ referral and fund termination.
Finding of No Violation: OCR determines that the institution’s caption programme meets the applicable standard. This outcome is most likely for institutions that can demonstrate substantial compliance with WCAG 2.1 AA, a written policy, an adequate accommodation process, and a documented remediation plan for any identified gaps.
Early Resolution: Before OCR completes its investigation, the institution may voluntarily remediate the complaint (for example, providing fully accessible captions for the specific content at issue) and OCR may close the complaint as resolved. This option is available primarily for single-complainant complaints about a specific piece of content rather than systemic complaints about the institution’s entire caption programme.
What OCR investigators look at in caption-specific investigations
Caption investigations have a different evidentiary focus than general website accessibility investigations. Understanding what investigators specifically assess informs the documentation a public entity should have ready before a complaint notice arrives.
Accuracy measurement
The WCAG 2.1 AA standard does not specify a numeric accuracy threshold, but OCR investigations use 99% as the operational accuracy benchmark, consistent with the FCC captioning accuracy rule and the DCMP Captioning Key. OCR investigators assess accuracy by reviewing the caption files submitted against the audio of the video sample. For a captioning complaint investigation, the accuracy review covers: word error rate on a random sample of the submitted videos; completeness (whether the caption file covers all spoken audio, including background speech, sound effects, and speaker identification where material to meaning); synchronisation (whether captions appear within two seconds of the corresponding audio); and positioning (whether captions obscure significant on-screen information).
Organisations that rely on LMS auto-captions without review will typically show 80–90% baseline accuracy on general content and 60–80% on domain-specific content (clinical terminology, regulatory vocabulary, engineering terms). Both fall materially short of the 99% benchmark OCR applies. The LMS auto-caption accuracy comparison documents baseline accuracy rates across major LMS platforms and explains why unreviewed auto-captions fail the WCAG 2.1 AA standard as a compliance posture.
Coverage assessment
OCR investigators assess whether captioning coverage is comprehensive. A common finding in public entity caption investigations is selective coverage: new content is captioned but back-catalogue content is not; general training videos are captioned but departmental-specific compliance training is not; public-facing content is captioned but internal employee training is not. Title II requires accessible digital services broadly — the coverage obligation extends to all pre-recorded audio-visual content published to employees, students, and the public, not just to content produced after the compliance deadline.
This coverage obligation is what makes the back-catalogue remediation requirement so significant. An institution with 4,000 training videos in its LMS and a compliance deadline of April 24, 2026 that captioned only new content produced after January 2026 has a coverage gap that will be identified immediately in the OCR investigation sample review. The large-scale caption backlog remediation playbook covers how to structure a phased back-catalogue approach that produces a defensible remediation plan, which is what OCR will accept in lieu of complete retroactive compliance.
Accommodation process documentation
Separate from the programme-level accuracy and coverage assessment, OCR investigators examine how the institution handles individual accommodation requests from specific Deaf or hard-of-hearing individuals. The accommodation process is governed by ADA Title II’s effective communication requirement, which predates the 2026 digital accessibility rule and applies independently. An institution with no documented accommodation process for captioning requests — no designated contact, no response timeline, no record of requests received and actions taken — will face adverse findings on the accommodation process dimension even if its caption programme otherwise makes reasonable progress.
The accessibility coordinator playbook covers the coordination infrastructure needed to manage individual accommodation requests alongside programme-level compliance work, including what records to keep and how to document the timeliness and adequacy of the accommodation response.
Vendor documentation
When an institution uses a third-party captioning vendor, OCR reviews the vendor contract for accuracy provisions. OCR investigators specifically look for: an accuracy SLA with a defined measurement methodology (not just a nominal accuracy claim in a vendor sales document); the vendor’s retention obligation for source audio files and caption output (audit trail); and any remediation provision specifying what happens when a delivered file fails the accuracy standard. The vendor audit rights and examination evidence post covers exactly what contractual provisions satisfy OCR’s vendor documentation requirements and what Rev, 3Play Media, and Verbit’s standard contracts currently provide — and what to amend before OCR makes its document request.
Written policy existence and content
The written caption policy is the single document that OCR investigators use to evaluate whether the institution has made a structural commitment to captioning compliance rather than treating captions as an individual accommodation. A written policy that specifies: (a) the accuracy standard that applies to all captioned content; (b) the scope of the captioning obligation (what content types, what audiences); (c) the production workflow (who captions new content, by what deadline, with what review step); (d) the accommodation process for individual requests; and (e) the back-catalogue remediation timeline, is the document that distinguishes an institution making documented progress from one that has treated captioning as ad hoc.
The absence of a written caption policy does not automatically produce a VRA requirement — but it makes every other piece of documentation less convincing. An institution with excellent caption quality, good vendor contracts, and a thorough back-catalogue remediation plan but no written policy appears to have produced those items reactively in response to the investigation rather than as part of a deliberate compliance programme. A written policy dated before the complaint notice is a chronological signal to OCR that the compliance effort was proactive. The caption programme governance policy template provides a policy structure that satisfies OCR’s written policy requirements.
Voluntary Resolution Agreements: what they require
A Voluntary Resolution Agreement is the primary settlement instrument when OCR finds evidence of non-compliance. Understanding what a typical captioning VRA requires helps public entities understand what their compliance obligations will look like post-investigation if a complaint is filed and resolved by agreement.
Typical VRA corrective actions for captioning violations
Caption-related VRAs vary based on the scope of the violation and the size of the institution, but the corrective actions in most captioning VRAs follow a consistent pattern:
Written caption policy (within 60 days): The institution must develop and publish a written caption policy covering all the elements described in the previous section. The 60-day timeline reflects OCR’s view that a written policy is foundational and should precede any other corrective action. In practice, some institutions arrive at the VRA negotiation with a policy draft already underway, which shortens the timeline for this item and signals to OCR that the institution is actively compliant.
Accuracy standard and measurement (within 90 days): The institution must document the accuracy standard it applies to captioned content — 99% consistent with WCAG 2.1 AA — and specify how accuracy is measured (DCMP spot-check methodology, vendor-reported accuracy against a defined measurement protocol, or internal QA review using a documented sampling framework). The caption QA methodology post covers QA frameworks that satisfy this requirement.
Vendor contract amendment (within 90 days): Where the institution uses a vendor, the vendor contract must be amended to include a specific accuracy SLA with a measurement methodology defined in the contract text, not merely referenced. Accuracy claims in vendor order forms or terms-of-service documents do not satisfy this requirement — the SLA must be in the signed contract addendum. Most captioning vendors will negotiate a contract amendment without charge if approached before a VRA is signed; after the VRA, the institution is obligated to produce the amendment regardless of vendor cooperation.
Back-catalogue remediation schedule (within 120 days): The institution must submit to OCR a phased remediation plan for back-catalogue content, specifying: (a) the total estimated inventory of uncaptioned or inadequately captioned content; (b) the priority tier structure (compliance-mandatory content first, then general public-facing content, then internal reference content); (c) the monthly or quarterly remediation target in hours of video; (d) the production model being used for remediation (vendor, SaaS, in-house); and (e) the projected completion date for each tier. OCR does not require that back-catalogue remediation be complete before the VRA is signed — it requires a credible, resourced plan with milestones that OCR can track through the monitoring period.
Staff training (within 180 days): All staff with content production responsibilities — L&D teams, marketing and communications, IT training divisions, departmental training coordinators — must complete training on the institution’s captioning policy and their role in implementing it. Training records must be submitted to OCR. The caption programme change management rollout post covers how to structure the staff training programme and documentation in a way that satisfies this requirement across a large, distributed institution.
Accommodation process formalisation (within 90 days): The institution must document a formal process for individual accommodation requests related to captioning: a designated contact or office, a response timeline (typically five business days for acknowledgment, fifteen business days for resolution), a record-keeping system, and a mechanism for escalation when a request cannot be resolved within the standard timeline. This is distinct from the programme-level captioning obligation — it covers individual requests for specific content types not yet in the captioned library or for specific formats or delivery mechanisms an individual needs.
VRA monitoring period and reporting
Captioning VRAs typically impose a monitoring period of two to three years. During the monitoring period, the institution must submit quarterly or semi-annual progress reports to OCR demonstrating compliance with each corrective action item. Reports typically include: updated back-catalogue remediation progress (hours completed, percentage of total inventory); new-content captioning compliance data (percentage of new content captioned within the policy’s specified production timeline); accommodation request log for the reporting period; and any changes to the captioning production model or vendor relationships since the last report.
The monitoring period is the compliance infrastructure cost that most public entities underestimate when they consider a VRA as a resolution outcome. Quarterly reporting requires that the institution have real-time data on its caption programme performance — which requires programme tracking that most mid-market public entities do not currently have. The caption programme annual review process covers the data infrastructure needed to produce quarterly OCR reports from a system that already serves the institution’s internal programme management, so that the reporting obligation does not require a separate administrative track.
Consequences of VRA non-compliance
Failure to meet VRA milestones — submitting reports late, missing remediation targets, failing to produce vendor contract amendments — is itself a violation that OCR can refer to DOJ for enforcement action. DOJ enforcement options include: requiring fund termination proceedings (terminating the institution’s federal financial assistance if non-compliance is wilful and uncorrected), filing a civil action in federal court, and referring the matter to the Department of Education’s Office of the Under Secretary for broader institutional review. These consequences are rarely triggered by a good-faith compliance effort with delayed milestones; they are triggered by systematic non-response to OCR after a VRA is signed. The practical risk management posture is to treat VRA milestones as hard commitments with internal early-warning mechanisms rather than soft targets.
DOJ monitoring for large public entities and state systems
While OCR complaint investigations are the primary enforcement pathway for individual public entities, the DOJ Civil Rights Division conducts proactive compliance reviews of large public entities and state systems using a different process with more demanding outcomes.
What triggers DOJ attention
DOJ compliance reviews are typically triggered by one of three conditions: a pattern of OCR complaints against entities within the same state system (multiple campuses of a state university system receiving independent complaints in the same 12-month period); media or advocacy attention bringing systemic accessibility failures at a major institution to DOJ’s attention; or DOJ’s own prioritisation of a specific sector (higher education, public transit, state government) based on compliance data from its annual section 508 and ADA compliance surveys.
For public universities, the highest-risk pattern is multiple campuses of a state system each receiving independent OCR complaints in close succession. When DOJ observes this pattern, it may open a single systemwide review rather than allowing OCR to process individual campus complaints separately. A systemwide review has a much broader investigation scope — covering all campuses, all content types, and all digital services — and typically produces more demanding VRA terms because the potential harm is proportionally larger.
The captioning vendor selection guide for public universities covers the procurement and contract requirements that are specifically important for public university systems under both OCR and DOJ review standards — particularly the government procurement rules that affect which vendors are available under state contract vehicles and what documentation is required for a compliant procurement.
DOJ monitoring requirements vs. OCR VRA requirements
DOJ monitoring is structurally more demanding than an OCR VRA in several ways:
Third-party auditor requirement. DOJ agreements for large public entities typically require an independent third-party accessibility auditor to conduct annual compliance reviews and submit findings directly to DOJ. This is a materially more expensive compliance infrastructure than self-reporting under an OCR VRA and requires engaging a qualified accessibility testing firm.
Longer monitoring period. DOJ monitoring agreements for state systems typically run three to five years, compared to the two-to-three-year standard OCR VRA monitoring period. Five-year agreements require the institution to maintain a full compliance reporting infrastructure across multiple budget cycles, personnel changes, and leadership transitions.
More specific technical requirements. DOJ agreements for large systems typically include more prescriptive technical specifications: the exact measurement methodology for caption accuracy, the specific format for accommodation request records, the required content of staff training programmes, and the technical specifications for how captions must be delivered in the LMS. These specifications are negotiated before the agreement is signed and are binding throughout the monitoring period.
Systemwide scope. Where OCR investigates the specific content types at issue in the complaint, DOJ systemwide reviews cover all digital content published by all covered entities within the system. A state university system review covers lecture capture on all campuses, employee training on all campuses, public-facing video content, event recordings, and any other digital content with audio that is published by any campus unit.
Post-deadline enforcement patterns: what is happening in Q2 2026
The April 24, 2026 compliance deadline produced an anticipated surge in OCR complaint filings from disability advocacy organisations that had been monitoring public entity compliance progress. Understanding what that complaint landscape looks like in Q2 2026 helps public entities calibrate their risk exposure and prioritise the documentation work that matters most before a complaint notice arrives.
Who is filing
Post-deadline complaints are coming disproportionately from structured organisations rather than individual filers: disability rights centres (DRCs) affiliated with the National Disability Rights Network (NDRN), university disability services offices (including student-filed complaints at other institutions), the National Association of the Deaf (NAD), the Disability Rights Advocates (DRA), and the National Federation of the Blind (NFB). These organisations have legal staff, systematic monitoring capacity, and the institutional knowledge to file complaints that identify systemic failures rather than individual content items. A complaint from one of these organisations typically requests a systemwide remediation plan rather than a correction of the specific content identified in the complaint.
Individual filers continue to represent a significant share of complaints, particularly from Deaf employees at public entities with mandatory compliance training programmes. An employee who cannot access required training content has an immediate practical injury and a strong factual basis for a complaint, which makes this complainant profile particularly likely to file and to persist through the investigation.
Which entity types face the highest complaint volume
Community colleges are receiving disproportionate complaint volume relative to their size. The reasons are structural: community colleges serve high proportions of Deaf and hard-of-hearing students (many community colleges have historically large Deaf student populations as a result of their accessible tuition and flexible scheduling), they produce large volumes of instructional video content at lower funding levels than four-year institutions, and they often have less mature digital accessibility infrastructure than larger universities. Community college L&D departments often have a single instructional designer responsible for captioning across all departments, without a dedicated accessibility coordinator.
County governments with large online workforce training libraries are receiving complaints from county employees with hearing disabilities who use online compliance training. County IT departments often manage the LMS without a dedicated L&D accessibility function, and the captioning infrastructure is typically the LMS auto-caption feature without any review layer — which produces systematic accuracy failures across the entire training library.
Public universities with prominent Deaf studies or disability studies programmes are experiencing complaints filed by student researchers who are systematically evaluating their own institution’s digital accessibility compliance as part of academic projects. This complaint pattern is distinctive because the filers are motivated by academic research questions as much as by immediate access barriers, and their complaints are typically highly documented with accuracy measurements and coverage assessments that professional advocacy organisations would be proud of.
Common fact patterns in Q2 2026 caption complaints
The most common fact pattern in caption complaints filed in Q2 2026 is: institution has auto-captions enabled in its LMS, no review step in place, no written caption policy, and a back-catalogue of 1,000 to 5,000 training videos produced without any captioning requirement. The complainant either directly measured accuracy on a sample of the institution’s content or reported specific errors in required training content (a Deaf employee who cannot understand the drug names in a pharmacy compliance training, for example, or a Deaf student who cannot follow the code syntax in a computer science lecture capture).
The second most common pattern is: institution has a vendor relationship for some content but not others — new faculty lectures are captioned by the vendor but departmental employee training videos produced by departmental coordinators are not captioned at all, or are captioned using department-level auto-caption tools without the institutional accuracy standard applied.
A significant minority of complaints involve live event captioning: institution does not have a CART vendor under contract, or has a CART vendor for formal events but not for webinar-format training sessions on platforms like Zoom and Teams where the auto-caption feature is active but no CART alternative is available. The real-time CART captioning guide covers the live event caption obligation under WCAG 2.1 AA 1.2.4 and the vendor and technology options for meeting it.
OCR response patterns
OCR is handling the Q2 2026 complaint surge by triaging complaints based on: (1) whether the complaint alleges individual harm (a specific individual could not access specific required content) versus systemic non-compliance (the institution has no caption programme at all); (2) whether the entity is large (higher investigation priority) or small (managed through early resolution efforts); and (3) whether the complaint is from a structured advocacy organisation (typically assigned to the regional OCR office with the most experienced digital accessibility staff) or from an individual.
For complaints alleging systemic non-compliance at large institutions, OCR is moving to the document request step faster than in pre-deadline periods, reflecting the investment of resources in post-deadline enforcement readiness. An institution receiving a complaint notice from OCR in Q2 2026 should expect a document request within 30 to 45 days of the initial notification, with a 20-to-30-business-day response deadline from the document request letter.
What “good-faith progress” means to OCR investigators
The distinction between an institution making good-faith progress toward compliance and one that has done nothing is real and consequential in OCR investigations. It affects the determination of whether a violation finding requires corrective action, the specific terms of any VRA, the length of the monitoring period, and whether OCR escalates to DOJ. Understanding exactly what evidence constitutes good-faith progress — and what does not — is the most practically useful information a non-compliant public entity can act on.
What constitutes good-faith evidence
A written caption policy adopted before the investigation began. The single most important good-faith signal is a written policy dated before the OCR complaint notice arrived. A policy that was adopted after the notice was received is still better than no policy — it demonstrates the institution is responsive — but a pre-notice policy date is clear evidence that the compliance effort was not triggered solely by investigator attention. Most OCR investigators will ask about the adoption date explicitly. The governance policy template can be adopted and approved by institutional leadership in three to four weeks — well within the window between a Q2 2026 complaint filing and the document request deadline.
A vendor contract with an accuracy SLA, even if recently negotiated. A vendor contract addendum establishing an accuracy SLA — even one negotiated after the April 24 deadline — demonstrates that the institution is building the contractual infrastructure for documented compliance. OCR investigators understand that many institutions are in the process of remediating vendor contracts as part of post-deadline programme improvement, and recent contract amendments are read as evidence of active compliance work rather than reactive cover.
A back-catalogue remediation plan with milestones, even if not yet completed. A phased remediation plan that identifies the total back-catalogue inventory, prioritises content by compliance risk, and specifies monthly remediation targets is a substantially better response to the OCR document request than “we are aware of the backlog and are working on it.” The plan does not need to be complete. It needs to be credible (realistic targets, resourced with a specific production model, signed by someone with authority to commit the institution to the plan).
Staff training records, even from training that occurred after the deadline. Records showing that content producers and L&D staff have received training on captioning requirements since April 24, 2026 are better than no training records, even if the training post-dates the deadline. Post-deadline training is evidence of an institution that responded to the deadline by building capability, not by ignoring it. Pre-deadline training is stronger evidence, but very few public entities have it.
Accommodation request records showing responsive handling. Records of individual accommodation requests received and resolved — even informal records, even with some requests resolved more slowly than ideal — demonstrate that the institution has been responsive to individuals with disabilities who needed access to captioned content. The absence of any accommodation request records is a significant adverse signal: either the institution has never received a request (unlikely for any institution with Deaf or hard-of-hearing employees or students) or it has not been keeping records. Neither interpretation is favourable.
What does not constitute good-faith evidence
Telling OCR that the institution “intends to comply” without documented evidence of steps already taken. Providing LMS auto-caption logs as evidence of a captioning programme without accuracy measurements showing those captions meet the 99% standard. Producing a vendor contract that mentions “quality captions” without a specific accuracy threshold or measurement methodology. Claiming that the IT department “handles accessibility” without producing an accessibility coordinator role description, a coordinator contact, or a policy document signed by an institutional officer.
OCR investigators are specifically trained to distinguish between documentation of actual compliance activity and documents assembled to create the appearance of compliance activity without the underlying infrastructure. Institutional officers who assemble a compliance record specifically for OCR review rather than from a running programme will typically be unable to answer follow-up questions about programme operations — questions about how the accuracy QA process works, who reviewed specific videos in the submitted sample, and what happened to the last accommodation request received — that an institution with a genuine programme can answer immediately.
Public entity sub-types: how enforcement differs
The enforcement framework above applies broadly to all public entities under ADA Title II, but the specific enforcement patterns, jurisdictional arrangements, and compliance contexts differ meaningfully across the major public entity sub-types.
Public universities and community colleges
DOE/OCR is the primary enforcement agency for public higher education institutions. Public universities receive substantial federal financial assistance through Title IV student aid programs, research grants, and other federal funding, giving DOE/OCR clear jurisdiction over virtually all public two-year and four-year institutions.
Public universities face a particularly complex captioning compliance landscape because the captioning obligation covers three distinct content populations simultaneously: employee training content (required compliance training for all staff, which is the L&D function most analogous to corporate training); academic instructional content (lecture capture, online course videos, educational media produced by faculty); and public-facing communications and event recordings (public meeting recordings, open course materials, accessibility-centre resources, graduation ceremony recordings). All three categories fall under Title II and all three require the same accuracy standard, but the production workflows, content owners, and compliance accountability differ dramatically across them.
A large public university with 20,000 employees and 30,000 students may have captioning production activity scattered across 50 departments, each with its own LMS usage pattern, its own production tools, and its own informal understanding of what “captioned” means. The centralisation of caption compliance governance across this distributed landscape is the primary operational challenge, covered in the accessibility coordinator playbook for exactly this context.
The university lecture capture captioning guide covers the specific integration requirements for Panopto and Echo360 — the dominant lecture capture platforms in higher education — and the accuracy limitations of their built-in auto-caption features in the academic context where faculty vocabulary, domain-specific terminology, and multilingual speakers create systematic accuracy problems that the built-in tools cannot resolve without a glossary layer.
K-12 school districts
Public K-12 school districts are covered entities under Title II (state and local government) and also receive substantial federal financial assistance through Title I, IDEA, and other programs. DOE/OCR has jurisdiction over K-12 captioning compliance complaints.
K-12 captioning compliance has a distinctive dimension: the ADA Title II captioning obligation covers video content used for employee training (teacher professional development, staff compliance training, administrative training) but also potentially covers instructional content used with students who have hearing disabilities under IDEA and Section 504. The captioning compliance obligation for student-facing instructional content is established by IDEA and Section 504 (which predate the Title II rule) rather than by Title II directly, but the practical compliance question is the same: is the video content accessible to Deaf and hard-of-hearing students and staff?
The K-12 caption compliance guide covers the full compliance landscape for school districts, including the intersection of IDEA, Section 504, and ADA Title II in the K-12 context, the content types that require captioning for students versus for staff, and the district-wide caption programme governance structure that satisfies DOE/OCR’s compliance requirements across a large multi-school district.
Public hospital systems
Public hospital systems present the most complex jurisdictional picture of any public entity type. As state or local government entities, they are subject to ADA Title II and DOE/OCR jurisdiction (for their employee training functions) or DOJ jurisdiction (as government entities). As healthcare providers, they are also subject to Section 504 of the Rehabilitation Act (enforced by HHS/OCR) and to CMS Conditions of Participation (which include effective communication requirements). The captioning obligations under all four frameworks are substantially aligned — accessible, accurate captions for audio-visual content — but the enforcement agencies, complaint pathways, and documentation requirements differ.
A Deaf employee of a public hospital system who files an OCR complaint about inaccessible compliance training may trigger investigation by DOE/OCR (as the employer’s Title II authority) and HHS/OCR (under Section 504) simultaneously, if the training content is both required employee training and content that the hospital also publishes to patients or the public. Managing a parallel investigation requires a compliance record that satisfies both agencies, which in practice means a single compliance documentation framework that is comprehensive enough to present to either investigator without modification.
Public hospital system L&D teams should use the US caption compliance matrix to map their specific content types to the specific regulatory frameworks that apply to each, so the compliance documentation framework covers all applicable standards rather than just the ADA Title II rule.
Local and county government
Cities, counties, transit authorities, and other local government entities are subject to ADA Title II with DOJ as the primary enforcement agency for non-educational entities. DOJ enforces through the Civil Rights Division’s Disability Rights Section, which handles both complaint-driven investigations and proactive compliance reviews.
Local government L&D teams face captioning compliance challenges that are structurally different from university or hospital contexts: the content is primarily workforce compliance training (safety training, OSHA compliance, HR compliance, civil rights training) rather than instructional or medical content; the LMS is often a general-purpose workforce training platform (Cornerstone, Relias, or a county-procured custom system) rather than a higher-education or healthcare-specific platform; and the procurement constraints of government contracting create delays in vendor onboarding that a corporate or university context would not face.
County governments procuring captioning services must comply with local procurement rules (sealed bids for services over a threshold, cooperative contract vehicles, sole-source justification requirements) that affect the timeline for establishing a vendor relationship. A county that needs to conduct a formal RFP for captioning services before amending its LMS captioning programme cannot simply call a vendor and sign a contract in two weeks, as a private entity could. OCR investigators generally understand government procurement constraints as a mitigating factor when good-faith procurement efforts are documented, even if the procurement has not yet concluded when the document request deadline arrives.
State-level enforcement overlay
Federal OCR enforcement is not the only enforcement risk for public entities. Several states have disability civil rights laws that create additional enforcement pathways — including private rights of action that allow individuals to sue public entities directly in state court without going through federal OCR.
California
California’s Unruh Civil Rights Act and the California Disabled Persons Act provide private rights of action for digital accessibility failures, including by public entities. California’s state AG and the Department of Justice’s Division of Civil Rights have authority to investigate and enforce against systematic accessibility failures. State enforcement in California is currently the most active of any US state, with the AG’s office having announced a digital accessibility enforcement initiative in early 2026 that specifically targets state and local government digital services.
Public entities in California face the possibility of simultaneous federal OCR investigation and state AG enforcement action arising from the same captioning failure. The California enforcement pathway moves faster than federal OCR — state AG investigations often produce settlement agreements within six to nine months — and the remediation requirements are substantially similar to federal VRA requirements, so a compliance programme that satisfies state requirements will generally satisfy federal requirements as well.
New York
The New York Human Rights Law (NYHRL) prohibits discrimination on the basis of disability by public entities and provides private right of action in state court. The New York State Division of Human Rights (NYSDHR) also has administrative enforcement authority. New York state courts have been receptive to digital accessibility claims, and the NYSDHR has handled disability rights complaints involving digital content for decades under Section 296 of the NYHRL.
Public entities in New York should note that NYSDHR complaint timelines are comparable to federal OCR timelines, and NYSDHR administrative findings create a record that can be used in subsequent federal proceedings. An adverse NYSDHR finding on a captioning complaint is typically introduced in subsequent federal OCR investigations as prior adverse finding evidence.
Illinois
Illinois’s Human Rights Act covers state and local government entities and is enforced by the Illinois Human Rights Commission. Separately, Illinois requires state agency websites and digital services to comply with WCAG 2.1 AA under the Illinois Information Technology Accessibility Act (IITAA), with enforcement through the Illinois Department of Human Services. Public entities in Illinois face a three-agency landscape: federal OCR, the Illinois Human Rights Commission, and IITAA enforcement — each with distinct complaint pathways and investigation timelines.
The broader state compliance landscape — including Texas, Minnesota, Washington, and Massachusetts — is covered in detail in state caption compliance law beyond ADA. That post documents the specific enforcement authority, complaint pathway, and private right of action availability for each major state framework, which is the starting point for public entities determining their state-level enforcement exposure.
Differences from Section 508 enforcement
Public entities that also function as federal contractors or grantees may be familiar with Section 508 of the Rehabilitation Act, which predates ADA Title II’s digital accessibility rule and has its own enforcement mechanism. The differences between 508 and Title II enforcement are material for public entities managing compliance across both frameworks.
Who enforces. Section 508 is enforced administratively through the entity’s internal 504/508 coordinator, through agency complaint processes, and through the relevant federal agency’s Section 508 programme office. Title II enforcement comes from external agencies — DOE/OCR, DOJ, HHS/OCR — not from the public entity itself. The external enforcement character of Title II means that the investigating agency has subpoena authority and access to the institution’s records, whereas 508 administrative processes are managed internally.
Scope of covered content. Section 508 applies specifically to electronic and information technology procured, developed, or used by federal agencies and their contractors. Title II applies to all digital services provided by state and local government entities to the public, regardless of whether those services were built with federal funding. A public university’s LMS employee training library is covered by Title II regardless of whether the LMS was procured with federal funds — the content itself is a digital service provided to employees who are members of the public for purposes of the employment relationship.
Technical standard. Section 508 currently references WCAG 2.0 Level AA (the 2017 refresh). ADA Title II references WCAG 2.1 Level AA — a meaningfully higher bar in several respects, though the captioning-specific standards (1.2.2 and 1.2.4) are identical in both versions.
Complaint mechanism. Section 508 complaints go to the agency’s internal 504 coordinator first, then to OCR if the internal process fails. Title II complaints go directly to external OCR. This structural difference means that a 508 complaint has an internal resolution step that a Title II complaint does not, giving the institution one more opportunity to resolve the issue before an external investigator is involved. Many public entities with robust 504 complaint processes have used internal resolution to close caption complaints before they became OCR matters; the Title II external complaint pathway removes that buffer for complaints that are filed externally from the start.
The US caption compliance matrix maps the full compliance landscape — Section 508, ADA Titles I through III, WCAG 2.0 and 2.1, state laws — against the content types and entity types where each framework applies. Public entities managing multiple compliance frameworks should use that matrix to ensure their captioning programme documentation addresses all applicable standards rather than just the framework most prominent in their recent communications with OCR.
The captioning programme as enforcement defence: what makes a compliance record defensible
The aggregate of everything above points to a practical question: what does a public entity’s captioning programme record need to look like to be defensible in an OCR investigation? The answer is not “perfect compliance” — very few public entities are in that position, and OCR investigators know it. The answer is a programme record that demonstrates deliberate, documented, measurable progress toward compliance from a known starting point.
The eight documentation elements OCR looks for
Drawing from the OCR document request framework described above and the VRA corrective action requirements, a defensible compliance record for a public entity captioning programme includes eight core elements:
1. Written policy adopted by institutional leadership. Not a staff-level workflow document, but a policy approved by the institution’s ADA/504 coordinator, the relevant vice president or administrator, and ideally the institution’s legal or general counsel. The adoption date matters. The policy should specify the accuracy standard, scope, production workflow, accommodation process, and back-catalogue remediation commitment.
2. 504/ADA coordinator with captioning in their defined role. A named individual with documented responsibility for caption compliance oversight. This person is the OCR contact for the investigation and the internal accountability point for the remediation programme. The absence of a named coordinator is a structural compliance gap that VRAs routinely require to be filled as a first corrective action item.
3. Vendor contract with accuracy SLA. For institutions using a captioning vendor, a signed contract addendum specifying the accuracy standard (99% consistent with WCAG 2.1 AA), the measurement methodology (DCMP-consistent or equivalent), and the vendor’s record retention and audit obligations. The vendor SLA review checklist specifies exactly what contract provisions OCR investigators look for and what language is adequate versus inadequate.
4. QA documentation for new content. A written QA process that specifies who reviews new captioned content, how accuracy is assessed, what happens when a file fails the accuracy review, and how QA outcomes are recorded. Even a lightweight QA process — a 10-sample spot-check on each batch of vendor-produced captions, documented in a shared spreadsheet — is substantially better than no QA process, which implies that accuracy is assumed rather than verified.
5. Back-catalogue remediation plan. A documented inventory of uncaptioned or inadequately captioned back-catalogue content, prioritised by compliance risk, with monthly or quarterly remediation targets, production model identified, and projected completion date by tier. This is the document that OCR investigators use to assess whether the institution’s remediation timeline is credible and resourced.
6. Accommodation request records. A log of individual accommodation requests received related to captioning, the response timeline for each, and the resolution. The log does not need to show perfect response times — it needs to show that requests are received, tracked, and resolved within a reasonable period, and that the institution has a process for handling requests rather than addressing them ad hoc.
7. Staff training records. Documentation showing that content producers and relevant administrative staff have received training on the institution’s captioning policy and their specific obligations. Training records with dates, participant lists, and content description are the format OCR expects. Virtual training completion records from an LMS satisfy this requirement if the training content is substantive.
8. Accuracy measurement data for current production. Actual accuracy measurements on a sample of the institution’s captioned content, showing the current accuracy level and any improvement trend. If the current accuracy is below 99%, the accuracy data should be accompanied by the specific steps being taken to close the gap (vendor contract amendment, SaaS + review implementation, glossary build). Accuracy data that shows the institution knows its current performance level and is actively managing toward the standard is materially more favourable than an institution that cannot produce any accuracy data because accuracy has never been measured.
The caption compliance self-assessment checklist provides a scored 40-question evaluation across eight programme domains — including all eight documentation elements above — that gives institutions a structured way to assess their current compliance record against the criteria OCR investigators apply. Running the self-assessment before an OCR complaint notice arrives identifies the specific gaps to close and prioritises the documentation work that matters most.
The caption programme maturity model maps the eight documentation elements above to the five-level maturity progression from Reactive (Level 1) to Strategic (Level 5). OCR investigations typically find Level 1 and Level 2 organisations in violation; Level 3 organisations (Established) with the written policy, vendor SLA, and remediation plan in place often achieve early resolution or a minimal VRA; Level 4 and 5 organisations can demonstrate compliance without a VRA finding.
How much time do you have
If an OCR complaint has not yet been filed against your institution, the time available to build a defensible compliance record is the period between now and the arrival of a complaint notice — which could be weeks, months, or never, depending on whether your specific institution is in the current complaint filing patterns. The most time-efficient use of that window is: (1) adopt the written policy this week; (2) amend the vendor contract or implement SaaS + review this month; (3) document the back-catalogue remediation plan this quarter; and (4) run the staff training programme before the end of the calendar year. All four steps can be completed from a standing start in 90 to 120 days.
If an OCR complaint notice has already arrived, the time available is the period between the notice and the document request deadline. The notice typically arrives 10 to 20 business days before the document request. The document request deadline is typically 20 to 30 business days from the request letter. This gives most institutions 30 to 50 business days between the complaint notice and the document response deadline — enough time to adopt a written policy, initiate a vendor contract amendment, and document a back-catalogue remediation plan, provided the institution begins immediately on receipt of the notice.
If you have already received an OCR complaint notice
An OCR complaint notice is not a violation finding. It is notification that a complaint has been filed and that OCR has opened an investigation. The steps available in the period between the notice and the document request deadline are the most consequential actions an institution can take to improve its enforcement outcome.
Immediate actions (within five business days of notice receipt)
Retain legal counsel with civil rights and disability law experience. ADA Title II investigations are civil rights proceedings. Legal counsel should be involved from the notice receipt forward, not only when a VRA is being negotiated. Counsel with OCR investigation experience can advise on the document response strategy, the scope of the document request, and the negotiation of VRA terms if a violation finding is made.
Implement a document and evidence preservation hold. Instruct all staff responsible for captioning, the LMS, vendor management, and accommodation request handling to preserve all documents, emails, and records related to captioning and digital accessibility. Do not delete any caption files, vendor communications, accommodation request emails, or LMS configuration records. Evidence destruction after receipt of a complaint notice is spoliation, which is independently actionable and substantially worsens the institution’s enforcement position.
Identify your 504/ADA coordinator for the investigation. If the institution does not have a named coordinator with captioning in their responsibility, designate one immediately and document the designation in writing. The coordinator will be the OCR investigation contact and will need to have authority to make commitments about the institution’s compliance programme on behalf of institutional leadership.
Pull a documentation inventory. Identify what compliance documentation currently exists: written policy (if any), vendor contracts, QA records, accommodation request logs, staff training records, back-catalogue inventory estimates, accuracy measurement data. The inventory does not need to be complete in five business days — it needs to identify the documentation gaps so the institution knows what needs to be created before the document request deadline.
Before the document request deadline
Adopt a written caption policy. If no written policy exists, adopt one. Use the governance policy template as a starting point, have it reviewed by the institution’s ADA coordinator and legal counsel, and have it approved by the appropriate institutional officer before the document request deadline. The policy must be genuine — it must reflect what the institution actually plans to do — not a document created solely for OCR presentation.
Initiate vendor contract amendment or SaaS implementation. Contact the captioning vendor to initiate a contract amendment conversation. Even if the amendment is not yet signed when the document response is submitted, evidence of the initiated negotiation — email chains, draft addendum, vendor confirmation of the conversation — is better than no vendor amendment activity. If the institution is implementing a SaaS tool for the first time, get the account set up and the glossary build started so the implementation is evidence-based rather than notional.
Document the back-catalogue remediation plan. Estimate the total back-catalogue inventory, establish the tier structure, and commit to remediation targets. A plan that is honest about the scale of the problem and realistic about the timeline is more credible to OCR investigators than a plan that claims to remediate a 3,000-video library in six months without evidence of the resources to do it. The backlog remediation playbook covers how to estimate the inventory, structure the triage, and produce a credible plan from a standing start.
Submit the document response strategically. The document response is a legal submission, not an administrative form. It should be prepared with legal counsel review, should respond to each item in the document request completely and honestly, and should include a cover letter from the institution’s legal counsel explaining the institution’s compliance posture and documenting the steps taken since the complaint notice was received. The cover letter is an opportunity to frame the institution’s good-faith progress narrative directly to the OCR investigator before the formal investigation begins.
Building the caption programme now: the enforcement-readiness case
The post-deadline enforcement landscape described in this post makes the case for building a genuine, documented caption programme more compellingly than the pre-deadline preparation case. Before the deadline, the argument was about regulatory risk — the possibility of enforcement. After the deadline, the argument is about current exposure: OCR complaints are being filed now, investigations are being opened now, and the document request deadline that follows a complaint notice is 30 to 50 business days from notice receipt.
A public entity that builds a caption programme now — written policy, vendor SLA, QA process, back-catalogue remediation plan, accommodation request log, staff training records — is building the documentation that will determine its enforcement outcome when a complaint is filed. The compliance programme is also the enforcement defence.
The practical starting point for most public entities is the eight-element documentation framework above, worked through in sequence. The written policy and accommodation process formalisation can be completed in the first 30 days. The vendor SLA amendment and QA process documentation can be completed in the first 60 days. The staff training and back-catalogue remediation plan can be completed in the first 90 days. At the 90-day mark, a public entity that started from zero has a defensible compliance record that satisfies the key OCR document request items even if it does not have a fully captioned content library.
The caption compliance programme build guide covers the complete programme build sequence with the specific decisions to make at each stage — production model, accuracy standard, QA methodology, vendor selection, governance policy, staff training, and back-catalogue remediation — in an order that produces a deployable programme as quickly as possible from a standing start. That guide is the operational companion to the regulatory and enforcement context covered here.
FAQ
We missed the April 24, 2026 deadline. Are we automatically in violation and will OCR automatically investigate us?
No. ADA Title II enforcement is complaint-driven, not audit-driven. The deadline passed, but OCR does not proactively audit every public entity for caption compliance. Enforcement is triggered by a complaint from an individual who has been denied access to digital content. Missing the deadline means you are exposed to enforcement if and when a complaint is filed — it does not mean OCR has opened or will automatically open an investigation. The risk is real and material, but it is probabilistic and concentrated among institutions whose audiences include individuals with disabilities who regularly use digital training or informational content. The appropriate response is not to panic about imminent enforcement; it is to build the compliance programme now, which reduces both the probability that a complaint results in a violation finding and the consequence if it does.
What is the 180-day rule and how does it affect our complaint exposure?
Complainants must file with OCR within 180 days of the alleged discriminatory act. In a captioning context, this is typically 180 days from the date the complainant attempted to access inaccessible content. This means the complaint window for content that was inaccessible before April 24, 2026 is closing (180 days before July 10, 2026 is approximately January 12, 2026). However, for content that remains inaccessible now, the 180-day clock runs from each attempted access. A Deaf employee who attempts to access a required compliance training module today and finds it uncaptioned has a fresh 180-day window from today. The 180-day rule does not insulate institutions from future complaints about current inaccessibility — it only limits the retrospective reach of complaints about past specific incidents.
How long does an OCR captioning investigation typically take?
For a single-entity complaint, 90 to 180 days from the initial complaint filing to an initial determination. For systemic complaints involving large institutions or state systems, 12 to 18 months from filing to determination is not unusual. For DOJ proactive compliance reviews of state systems, the investigation phase alone can take 18 to 24 months. The document request step — which requires the institution’s active participation and is the most time-sensitive from the institution’s perspective — typically occurs 30 to 60 days after the initial complaint notification and has a 20-to-30-business-day response deadline.
Our vendor says their captions are “99% accurate.” Is that sufficient for OCR?
The vendor’s accuracy claim in marketing materials or order forms is not sufficient for OCR. What OCR looks for is a contractually defined accuracy standard in the signed contract, with a defined measurement methodology. “99% accurate” in a vendor brochure is a marketing claim; “99% accuracy as measured by [specific methodology] on a random sample of [specified size] from each production batch, verified by the vendor’s QA team” in a signed contract addendum is a compliance instrument. If your current vendor contract does not have this level of specificity, the contract amendment conversation is the next step. Most vendors will negotiate this addendum without charge if approached in good faith before an OCR investigation is underway. After an OCR investigation opens and the addendum is required by a VRA, the vendor has less commercial incentive to provide the amendment at no cost.
We have a back-catalogue of approximately 2,000 training videos that are uncaptioned or inadequately captioned. What does OCR expect us to do about that?
OCR expects a phased remediation plan with a credible timeline, not retroactive completion before the investigation closes. A plan that identifies the 2,000-video inventory, prioritises compliance-mandatory content (legally required training for all staff, training content directly relevant to Deaf employees’ job functions) for remediation in the first 90 days, and establishes a monthly production target that is achievable with your current or planned production model will generally satisfy OCR’s back-catalogue requirement. The plan must be resourced — “we plan to remediate 200 hours per month with our current vendor relationship” requires evidence that the vendor relationship is in place and capable of that volume. OCR does not expect the entire backlog to be resolved before a VRA is signed; it expects the plan to be in the VRA as a binding commitment with monitoring checkpoints.
We are a small community college with limited budget. Does OCR consider resource constraints in investigation and VRA terms?
OCR may consider the relative resources of a small institution in setting VRA remediation timelines but does not use resource constraints to modify the applicable compliance standard. A 99% accuracy requirement applies to a community college with 2,000 students and a $15 million operating budget the same as to a state university with 40,000 students and a $2 billion budget. What resource constraints may affect is the timeline OCR accepts for back-catalogue remediation — a small institution may receive a 24-month remediation timeline where a large institution receives 12 months — and whether OCR accepts a SaaS + review production model as an adequate compliance infrastructure rather than requiring a full human-vendor relationship. OCR is generally pragmatic about production model for small institutions that demonstrate active good-faith compliance, because the goal is accessible content, not a specific production infrastructure.
If we receive a VRA and comply with its terms, are we protected from future complaints about the same issues?
A completed VRA provides some protection against a repeat complaint about the same content types from the same period that was addressed in the VRA. However, it does not protect against future complaints about new content, new content types, or continuing accuracy failures in content the VRA did not specifically address. The monitoring period creates an ongoing reporting obligation; failure to maintain compliance during the monitoring period is itself a VRA violation. The practical protection a VRA provides is that an institution that has completed a VRA and maintained compliance through the monitoring period has a documented compliance record that is substantially more defensible in a subsequent complaint than an institution with no compliance history. The best protection against future complaints is a genuine, operational caption programme that maintains compliance as a matter of routine, not a document trail created for enforcement purposes.
GlossCap: the SaaS captioning tool that builds your compliance documentation as you produce
Every OCR document request item that public entity L&D teams struggle to produce — accuracy measurements, QA review records, glossary documentation, production workflow records — is a by-product of GlossCap’s production workflow rather than a separate documentation task. The edit interface records who reviewed each segment, what changes were made, and when the file was approved. The accuracy dashboard shows error rate by video, by content type, and by production period — the accuracy measurement data OCR investigators ask for in the first document request. The glossary records every term, every variant, and every correction applied, providing the vocabulary-handling evidence that distinguishes a documented compliance infrastructure from an ad hoc production process.
For public universities, public hospital systems, county governments, and K-12 districts building or remediating their caption programmes after the April 2026 deadline, GlossCap provides the production tool and the compliance documentation framework in a single subscription. The audit log is the OCR document response; the accuracy dashboard is the VRA progress report; the glossary is the evidence of systematic vocabulary handling that differentiates 99% accuracy from 80% accuracy on domain-specific content. The SaaS Team plan covers the production volume of most mid-market public entity L&D teams, and the compliance documentation infrastructure is available from the first video processed — not assembled retroactively when the complaint notice arrives.
See GlossCap plans and pricing or try the demo to see the edit and audit workflow in action.