Web Accessibility Acts Explained: What Compliance Teams Must Do Now

A Compliance Team Faces the Deadline

A public university's IT director receives a formal complaint in February 2026: a blind graduate student cannot access the institution's PDF course materials using a screen reader. The university's website lists the documents as accessible, but none have been remediated to PDF/UA-1 (ISO 14289-1:2014) standards. The institution has 50,000-plus constituents, placing it squarely under the ADA Title II deadline of April 24, 2026. Litigation exposure and remediation costs now arrive simultaneously.

This scenario repeats across higher education, municipal government, and corporate sectors because compliance teams are managing multiple overlapping frameworks—ADA Title II, Section 508, the European Accessibility Act (EAA), and the underlying Web Content Accessibility Guidelines—without a unified implementation roadmap. The frameworks share technical requirements but differ in scope, enforcement mechanisms, and deadlines, and failing to distinguish them produces exactly the kind of gap the scenario above illustrates.

Answer Block — What Is the Web Accessibility Act and What Does It Require?

No single law carries the name Web Accessibility Act. The phrase is an umbrella term for a cluster of laws that regulate digital accessibility: the European Accessibility Act (EAA, Directive (EU) 2019/882), the US Department of Justice's ADA Title II web rule (28 CFR Part 35), Section 508 of the Rehabilitation Act, and the EU Web Accessibility Directive (2016/2102). The frameworks differ in scope and enforcement, but they converge on the Web Content Accessibility Guidelines as the technical baseline—WCAG 2.1 Level AA for the EAA and ADA Title II, WCAG 2.0 Level AA for Section 508—and all of them treat documents delivered through websites, including PDFs, as covered content. Compliance teams must determine which frameworks apply to their organization, audit web content and document repositories against the governing WCAG version, remediate by the applicable deadline—April 24, 2026 or April 26, 2027 for ADA Title II; already in force since June 28, 2025 for the EAA—and embed accessibility verification into publishing workflows so conformance survives the next content cycle.

The Four Frameworks Behind the Term Web Accessibility Act

Obligations arrive under at least four distinct legal instruments, and the first task for any compliance team is identifying which ones attach to the organization. An organization can sit under several at once: a public university with EU-facing online programs answers to ADA Title II, Section 508 (through federal funding instruments and procurement), and potentially the EAA simultaneously.

The European Accessibility Act (Directive (EU) 2019/882)

The EAA is the broadest private-sector accessibility law currently in force. It covers services placed on the EU market—e-commerce, consumer banking, electronic communications, passenger transport interfaces, e-books, and audiovisual media platforms—regardless of where the provider is headquartered. The directive has applied to services placed on the market since June 28, 2025, with a transition period for pre-existing service contracts that expires June 28, 2030. Microenterprises providing services—fewer than 10 employees and annual turnover not exceeding €2 million—are exempt. Technical conformance is measured against EN 301 549, the harmonized European standard that incorporates WCAG 2.1 Level AA for web content.

ADA Title II: The DOJ Web and Mobile Rule (28 CFR Part 35)

In April 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act that establishes WCAG 2.1 Level AA as the enforceable technical standard for web content and mobile apps provided by state and local government entities—public schools and universities, courts, transit authorities, county health departments, and special districts. Compliance dates are staged by population: April 24, 2026 for entities serving 50,000 or more people; April 26, 2027 for smaller entities and special district governments. Critically, the rule names conventional electronic documents—PDFs, word processing files, spreadsheets, and presentations—as covered web content.

Section 508 of the Rehabilitation Act

Section 508 binds US federal agencies and the information and communication technology they develop, procure, maintain, or use. The 2017 refresh incorporated WCAG 2.0 Level AA as its technical baseline, applied to both web content and electronic documents. Its practical reach extends well beyond government payroll: contractors and vendors delivering digital content or documents to federal customers inherit the requirement through procurement clauses. The relationship between Section 508, WCAG, and PDF/UA is a frequent source of confusion, but the short version is that they are nested rather than competing standards.

The EU Web Accessibility Directive (2016/2102)

Predating the EAA, the Web Accessibility Directive covers public-sector websites and mobile applications across EU member states and has been fully in force since June 2021. It requires conformance with EN 301 549, a published accessibility statement, and a monitored feedback mechanism. For European public bodies, the directive and the EAA now operate in parallel; for private companies, the directive matters mainly as the regulatory template the EAA scaled outward.

Other Instruments Compliance Teams Track

Ontario's AODA requires WCAG 2.0 Level AA for organizations with 50 or more employees. The UK's Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 apply EN 301 549 to public bodies post-Brexit. In the US private sector, ADA Title III web litigation continues to apply WCAG as the de facto standard even without a formal regulation. The pattern across every jurisdiction is convergence: whatever the statute's name, the technical target is WCAG.

The Deadlines That Define 2026 and 2027

Compliance calendars across frameworks now stack within a 24-month window:

• June 28, 2025 (passed): The EAA applies to covered services placed on the EU market. Member-state market surveillance and enforcement activity is ramping through 2026.
• April 24, 2026: ADA Title II compliance date for public entities with a total population of 50,000 or more—including the public university in the opening scenario.
• April 26, 2027: ADA Title II compliance date for public entities under 50,000 and for special district governments.
• June 28, 2030: The EAA's transition window for pre-existing service contracts closes; legacy arrangements lose their grace period.

WCAG 2.1 Level AA: The Shared Technical Baseline

Every framework above delegates its technical definition of accessible to the Web Content Accessibility Guidelines, either directly (ADA Title II, Section 508) or through EN 301 549 (EAA, Web Accessibility Directive). Understanding the baseline once therefore covers most of the compliance surface.

Four Principles, Fifty Success Criteria

WCAG organizes requirements under four principles—content must be perceivable, operable, understandable, and robust. At Levels A and AA combined, WCAG 2.1 comprises 50 testable success criteria. Representative requirements include text alternatives for non-text content, a 4.5:1 contrast ratio for normal text, full keyboard operability, content reflow at 320px width without horizontal scrolling, programmatically determinable structure (headings, lists, tables), and status messages exposed to assistive technology.

Where the Frameworks Diverge on Versions

Section 508 remains pinned to WCAG 2.0 Level AA, which lacks the 12 Level A/AA criteria that version 2.1 added for mobile interaction, low vision, and cognitive accessibility. The EAA (via EN 301 549) and ADA Title II both require WCAG 2.1 Level AA. WCAG 2.2, published in October 2023, has not yet been incorporated into any of the four frameworks. The practical strategy is simple: build and audit to WCAG 2.1 Level AA, which satisfies 2.0 by inclusion. A fuller breakdown of how WCAG applies to document remediation is available for teams scoping that work.

Documents Are Covered Content: The Obligation Teams Scope Out Too Late

Web accessibility programs habitually start—and stall—at HTML. Templates get fixed, components get audited, and the document repository sitting behind the website is deferred to a later phase that never arrives. Every framework discussed here reaches those documents.

How ADA Title II Treats PDFs

The DOJ rule includes a narrow exception for preexisting conventional electronic documents, but the exception evaporates the moment a document is currently used to apply for, gain access to, or participate in a public entity's services, programs, or activities. Enrollment forms, course syllabi, benefits applications, public meeting agendas, and permit instructions all fail the exception test. The DOJ's 28 CFR Part 35 language on PDFs deserves a close read by any team tempted to rely on the preexisting-content carve-out.

PDF/UA-1: The Conformance Target for Documents

WCAG was written for web pages; for PDF files the operative conformance standard is PDF/UA-1 (ISO 14289-1:2014), which translates WCAG's principles into PDF-specific requirements: a complete and correctly ordered tag tree, a logical reading order, alternative text on images, properly headed tables, document language metadata, and a meaningful title. A visually clean PDF with no tag structure is, to a screen reader, an empty document.

Why Document Backlogs Dominate Remediation Budgets

An organization with a decade of publishing history typically holds thousands of documents across its CMS, portals, and intranets, and manual remediation runs hours per file. This is why document backlogs—not web templates—consume the bulk of accessibility budgets and timelines. Automated remediation platforms such as RemeDocs process documents to PDF/UA-1 conformance in minutes with an audit trail, which converts the backlog from a multi-year staffing problem into a managed pipeline. Teams sizing the problem can run any file through the free PDF accessibility checker to see exactly which conformance failures a given document carries.

Enforcement: What Non-Compliance Actually Costs

In the US, ADA Title II is enforced both by the Department of Justice—through investigations, settlement agreements, and consent decrees—and by private plaintiffs, who can obtain injunctive relief and attorneys' fees. State statutes such as California's Unruh Act layer monetary damages on top. Plaintiffs' firms now run automated scans against public-sector and high-traffic commercial sites, and inaccessible documents are among the most common lawsuit triggers: a single untagged PDF is a self-contained, easily demonstrated exhibit.

In the EU, member-state market surveillance authorities can demand corrective action, impose fines under national transposing legislation, and ultimately order withdrawal of non-conforming services from the market. The mandatory accessibility statement compounds the exposure—an inaccurate statement is public, self-documented evidence of the gap. Beyond regulators, accessibility conformance is increasingly a procurement gate: organizations that cannot produce a credible conformance report lose bids before any enforcement body gets involved.

The Implementation Checklist for Compliance Teams

The following sequence is structured for a team starting now, against either the April 2026 or April 2027 deadline.

Phase 1: Scope and Inventory (Weeks 1–4)

• Determine applicable frameworks: Map the organization against ADA Title II (public entity? population tier?), Section 508 (federal funds or contracts?), and the EAA (services placed on the EU market?). Record the governing deadline for each.
• Crawl all web properties: Enumerate sites, subdomains, mobile apps, and authenticated portals. Shadow properties—event microsites, legacy department pages—are routine audit findings.
• Inventory the document corpus: Count every PDF and conventional electronic document reachable through covered properties, including those behind logins. This number drives the remediation budget more than any other.
• Classify documents by exposure: Flag documents currently used to apply for, access, or participate in services—these have no exception coverage and remediate first.

Phase 2: Audit Against the Governing Standard (Weeks 4–10)

• Run automated scanning for breadth: Apply WCAG 2.1 Level AA scanning across the full crawl to surface systemic failures in templates and components.
• Run manual assistive technology testing for depth: Screen reader passes (NVDA, JAWS, VoiceOver) on critical user journeys—applications, payments, enrollment—catch the failures automation cannot.
• Audit documents against PDF/UA-1: Validate tag structure, reading order, alternative text, and table semantics per file; classify each document as conformant, remediable, or requiring reconstruction.
• Produce a prioritized defect register: Tie every finding to a success criterion, a severity, and an owner.

Phase 3: Remediate in Priority Order (Months 2–6)

• Fix templates and shared components first: A corrected navigation, form pattern, or page template repairs every page that inherits it.
• Remediate service-critical pages and documents next: Content used to access services carries the legal exposure; traffic data settles ordering disputes.
• Route the document backlog through an automated pipeline: Automated PDF/UA-1 remediation with human spot-QA is the only approach that clears thousands of files inside a deadline window.
• Address third-party content: Replace inaccessible embedded widgets or obtain documented conformance (an ACR/VPAT) from the vendor; third-party origin does not transfer the obligation.

Phase 4: Operationalize (Ongoing)

• Gate releases on accessibility checks: Integrate automated scanning into CI/CD and require accessibility sign-off for new templates and components.
• Gate document publishing: No PDF reaches a covered property without passing conformance checking—remediation at publish time is orders of magnitude cheaper than backlog remediation.
• Publish an accessibility statement with a feedback channel: Required outright in the EU and best practice everywhere; keep it accurate and current.
• Schedule recurring manual audits: Quarterly assistive technology testing on critical journeys catches the drift automated tools miss.

Frequently Asked Questions: Web Accessibility Act Compliance

Is there a single law called the Web Accessibility Act?

No. The phrase is an informal umbrella term. The operative laws are the European Accessibility Act, the DOJ's ADA Title II web rule (28 CFR Part 35), Section 508 of the Rehabilitation Act, and the EU Web Accessibility Directive, plus national instruments such as Ontario's AODA.

What technical standard do web accessibility laws require?

WCAG 2.1 Level AA is the dominant baseline—required by ADA Title II directly and by the EAA through EN 301 549. Section 508 currently requires WCAG 2.0 Level AA. Building to WCAG 2.1 Level AA satisfies all four frameworks' web requirements.

When is the ADA Title II compliance deadline?

April 24, 2026 for state and local government entities with a total population of 50,000 or more; April 26, 2027 for smaller entities and special district governments. The deadlines apply to existing content, not only content published afterward.

Does the European Accessibility Act apply to companies outside the EU?

Yes. The EAA applies to covered services placed on the EU market regardless of where the provider is established. A US company selling covered services to EU consumers is in scope; only microenterprise service providers are exempt.

Are PDFs covered by web accessibility laws?

Yes. ADA Title II explicitly covers conventional electronic documents, Section 508 covers electronic documents, and the EAA reaches documents delivered through covered services. The document-level conformance standard is PDF/UA-1 (ISO 14289-1:2014).

What happens if an organization misses the deadline?

In the US: DOJ enforcement, private litigation with injunctive relief and attorneys' fees, and state-law damages in some jurisdictions. In the EU: corrective-action orders, fines under member-state law, and potential market withdrawal. In both: lost procurement opportunities and reputational exposure.

Immediate Next Steps for Compliance Teams

Five actions executable within the current planning cycle:

1. Confirm your governing frameworks and deadlines this week: Population tier for Title II, federal instruments for Section 508, EU market exposure for the EAA. Everything downstream depends on this determination.
2. Count your documents: Inventory every PDF reachable through covered properties and flag those used to access services. Run representative samples through the free PDF accessibility checker to calibrate the remediation effort per file.
3. Commission a WCAG 2.1 Level AA audit: Automated scanning for coverage, manual assistive technology testing for critical journeys, documented against individual success criteria.
4. Stand up a document remediation pipeline: Manual remediation does not scale to a deadline; automated PDF/UA-1 remediation with human QA does. RemeDocs provides structured remediation workflows for exactly this document class.
5. Publish an accessibility statement and feedback mechanism: Accurate, findable, and monitored—then keep it true by gating new content on conformance checks.