← Back to blog

12–18 Months to Meet DOJ Deadlines for Web Accessibility Compliance

September 19, 2026
12–18 Months to Meet DOJ Deadlines for Web Accessibility Compliance

Web accessibility compliance in the United States means meeting WCAG-based standards as the working legal baseline under the ADA. State and local governments face a hard deadline under the Department of Justice's 2024 Title II rule, while private businesses under Title III face rising legal expectation to reach the same bar. The immediate move for any organization is a mixed automated and manual accessibility audit, followed by a documented remediation plan Secure Techies and similar compliance teams can help build and track.


TL;DR:

  • Most organizations must prioritize early, comprehensive audits combining automated scans, manual review, and assistive technology testing to ensure genuine accessibility.
  • Deadlines for public entities range from April 2026 to April 2028, requiring proactive planning of remediation, testing, and documentation efforts at least 12 months prior.
  • WCAG 2.2 introduces new criteria on focus visibility, help consistency, and authentication, but adopting it early can reduce future rework, even though current rules cite WCAG 2.1 Level AA.
  • Private lawsuits often target core barriers that prevent task completion, so prompt responses, clear feedback channels, and documented remediation are key to reducing legal risk.
  • Maintaining compliance requires ongoing monitoring, updating policies, vendor contracts, and training content editors, as well as revisiting WCAG updates to stay ahead.

Securetechie
Keep Compliance Work On Track
Secure Techies provides proactive IT management, cybersecurity, monitoring, and compliance support for organizations managing technology risk.
Explore Secure Techies

Table of Contents

Which U.S. Laws Cover Web Accessibility Compliance

Three legal frameworks govern digital accessibility in the U.S., and each applies to a different type of organization. Getting this wrong, treating a private business like a government agency or vice versa, is the first mistake compliance officers make.

Title II of the ADA covers state and local government entities: city websites, public school portals, DMV online services, public transit apps. Title III covers "places of public accommodation," which courts have broadly interpreted to include retail websites, banking portals, restaurant ordering systems, and healthcare patient portals, even though Title III doesn't name digital properties explicitly. Section 508 applies to federal agencies and any organization receiving federal funding or contracting with the federal government, and it already incorporates WCAG standards directly into procurement law.

Contractual relationships complicate this further. A city government that outsources its parking payment portal to a third-party vendor doesn't get to point at the vendor when a resident can't complete a transaction. Under Title II, the public entity remains responsible for the accessibility of services delivered on its behalf, which means procurement contracts need accessibility clauses baked in before signing, not bolted on after a complaint.

To figure out which title applies to your organization:

  • If you're a government body, school district, or public utility, Title II applies and the DOJ's phased deadlines apply directly to you.
  • If you're a private business open to the public (retail, hospitality, professional services, healthcare), Title III governs, and while it lacks a formal technical rule, DOJ guidance treats WCAG 2.1 Level AA as the practical standard courts increasingly expect.
  • If you receive federal funds or hold a federal contract, Section 508 obligations run alongside whichever of the above also applies.
  • If you're unsure which category fits, assume the stricter standard. It's cheaper to over comply than to defend a lawsuit.

WCAG 2.2 Requirements and What "Compliant" Actually Means

Accessibility compliance isn't binary. WCAG organizes success criteria into three conformance levels: A (minimum), AA (mid-range), and AAA (highest). Level AA is the standard cited in nearly every piece of U.S. guidance and rule text, including the DOJ's own final rule, because AAA is often impractical to apply site-wide without sacrificing design or content flexibility.

WCAG 2.2 builds on WCAG 2.1 rather than replacing it. Content that conforms to WCAG 2.2 automatically satisfies WCAG 2.1 and WCAG 2.0 as well, which is why adopting 2.2 as your working target, even though the current federal rule cites 2.1, tends to reduce rework down the line as policy catches up to the newer standard.

WCAG 2.2 added nine new success criteria focused on:

  • Focus visibility, so keyboard users can always see where they are on a page.
  • Consistent help mechanisms across a site, like a persistent contact or chat option.
  • Reduced reliance on dragging gestures for users with limited motor control.
  • Simpler authentication flows that don't require solving cognitive puzzles.

One concept trips up a lot of legal and IT teams: equivalent facilitation. Under Title II, an entity doesn't have to make every single element pixel-perfect compliant if it offers an alternative that provides the same or greater level of access. A city government might post a scanned historical document that can't be made fully accessible, as long as it also offers an accessible summary or a staffed phone line that can walk a resident through the content. The alternative has to genuinely match the access, not just check a box.

The DOJ's Title II Rule: Deadlines and Exceptions You Need to Know

The Department of Justice finalized its rule on web and mobile app accessibility for state and local governments in April 2024, and it's the most concrete compliance timeline currently in federal law. The rule requires covered entities to meet WCAG 2.1 Level AA across their web content and mobile applications, published formally in the Federal Register.

The rule carves out specific exceptions, and understanding them matters because misreading an exception as blanket permission is a common and costly error:

  • Archived web content that's retained only for reference, not updated, and clearly marked as archived.
  • Preexisting conventional electronic documents, like older PDFs, unless someone requests an accessible version.
  • Content posted by a third party, unless the third party is posting on behalf of the public entity.
  • Password protected or otherwise secured conventional documents tied to a specific individual's account.
  • Preexisting social media posts made before the entity's compliance date.

None of these exceptions are permanent escape hatches. The DOJ's rule also permits narrower carve outs for fundamental alteration and undue burden, but entities claiming either must document the justification and be prepared to defend it, not just assert it after the fact.

Compliance dates are staggered by population size, and this is where budgeting gets real:

  • Public entities serving populations of 50,000 or more had until April 2026.
  • Smaller public entities and special district governments have until April 2027.
  • The DOJ's small entity compliance guide confirms this staggered timeline extends compliance planning for smaller bodies into 2028 in practical terms, once remediation and verification cycles are accounted for.

Recommended milestone planning works backward from your deadline: full audit at 18 months out, remediation sprints at 12 to 6 months out, verification testing at 3 months out, and a documented monitoring plan in place before the deadline hits.

How to Properly Test for Website Accessibility Standards

A clean report from an automated scanner is not proof of compliance, and treating it as one is probably the single biggest mistake organizations make when self-assessing. DOJ guidance is explicit that automated checkers catch a real but limited slice of issues.

Here's a practical three-layer methodology that holds up under scrutiny:

  1. Run automated scans first. Tools reliably catch missing alt text, low color contrast, missing form labels, and broken heading structure. They reliably miss whether alt text is meaningful, whether a keyboard trap exists in a modal window, or whether a screen reader announces a dynamic error message at all.
  2. Follow with manual code and interface review. A qualified reviewer tabs through every interactive element without a mouse, checks that focus order matches visual order, and reads through markup for correct semantic structure, not just valid HTML.
  3. Test with actual assistive technology users. This is the step most organizations skip, and it's the one that surfaces the problems automated and manual review both miss. Someone using a screen reader might complete a signup form in a completely different order than a sighted tester expects, or find a video's captions technically present but functionally useless because they aren't synced.

Sample test cases worth running specifically: completing a multi-step signup form using only a keyboard, submitting a support ticket with a screen reader active, navigating a product catalog with voice control software, and checking whether an embedded video's captions can be turned on without a mouse.

The output of this process should never be a vague "we're mostly compliant" summary. A defensible audit deliverable includes a prioritized issue list, an impact times effort score for each item so remediation gets sequenced sensibly, a named owner for every issue, and a verification step confirming the fix actually worked once deployed. This mirrors the same manual versus automated testing logic that applies in cybersecurity assessments: automated tools are fast and cheap, but they don't replace a human looking for what the tool wasn't built to catch.

Accessibility issues moving through audit workflow

Pro Tip: Score every accessibility issue by impact times effort, not just severity. A minor contrast issue on your homepage might affect more users in a day than a major keyboard trap buried three clicks deep on a rarely visited page.

Building a Compliance Program That Survives Beyond the Audit

An audit produces a snapshot. Without a governance structure behind it, that snapshot expires the day someone on the marketing team uploads a new PDF without alt text. Turning a one-time fix into an ongoing program requires four moving parts.

Policy and ownership. Someone specific, not "the web team" generically, needs to own accessibility as a standing responsibility, with a defined review cadence (quarterly is typical) and measurable KPIs like percentage of pages passing automated scans or average time to remediate a reported issue.

Procurement language. Every vendor contract for a website, app, or digital tool should require WCAG 2.1 AA conformance as a condition of the agreement, with language specifying who's responsible for fixes when a vendor's platform falls short. This is the same discipline organizations already apply to security and compliance audits for HIPAA or SOC 2. Accessibility deserves the same contractual weight.

Remediation sprints. Structure fixes in three tiers:

  • Quick wins: alt text, form labels, contrast fixes, deployable within a sprint or two.
  • Medium-term fixes: restructuring navigation, fixing focus order, rebuilding inaccessible components.
  • Long-term architecture changes: replacing a page builder or CMS that structurally can't produce accessible markup.

Training and workflow integration. Content editors need basic training on writing alt text and using heading structure correctly before publishing, not after a scan flags it. Development teams should run accessibility checks in CI/CD pipelines so a component that fails contrast requirements never reaches production in the first place.

Pro Tip: Keep a dated remediation log, screenshots, ticket numbers, and testing notes included. If a complaint or lawsuit ever arrives, a documented good-faith timeline is often the single strongest piece of evidence an organization can produce.

Documentation isn't paperwork for its own sake. Retaining audit trails, remediation timelines, and testing evidence is exactly the kind of record that similar compliance timeline documentation practices rely on in other regulated industries, and it demonstrates the good-faith effort that matters most once enforcement enters the picture.

Enforcement Risk and How to Reduce Your Exposure

Enforcement runs through two channels: direct DOJ investigations under Title II or III, and private lawsuits filed by individuals, often through advocacy organizations or plaintiff's attorneys who specialize in ADA web claims. Private litigation is by far the more common trigger for small and mid-size businesses, usually following a specific complaint about an inaccessible checkout flow, an unusable contact form, or a video without captions.

What typically triggers action isn't a minor cosmetic issue. It's a barrier that stops someone from completing a core task: buying a product, booking an appointment, applying for a job, or accessing a government service.

Settlements and remedies commonly include a required remediation timeline, ongoing monitoring commitments, and sometimes monetary damages or attorney's fees, particularly under state laws like California's Unruh Act, which allows statutory damages on top of federal ADA claims. Budgeting for legal risk should account for both the cost of fixing the site and the cost of the dispute itself, which often exceeds the remediation cost many times over.

Organizations that reduce their exposure tend to share the same habits:

  • They respond promptly to any accessibility complaint instead of letting it sit, since a documented fast response often shapes how a dispute resolves.
  • They publish a visible accessibility statement with a working feedback channel, so users have a path to report problems before escalating to legal action.
  • They keep dated records of remediation work, per the DOJ's own guidance on fundamental alteration and undue burden claims, which require documented justification, not just an assertion after the fact.
  • They treat every legal notice as a business priority, not a low-urgency IT ticket.

Your Accessibility Checklist: Quick Wins to Deploy This Week

Start with fixes that reduce the biggest barriers for the most users, in this order:

  1. Run a free automated scan to get a baseline issue count.
  2. Add descriptive alt text to every meaningful image; mark decorative images as empty alt.
  3. Label every form field explicitly, not just with placeholder text.
  4. Add captions to all video content and transcripts where practical.
  5. Check that every interactive element is reachable and operable by keyboard alone.
  6. Fix color contrast ratios below 4.5:1 for normal text.
  7. Verify heading structure follows a logical, nested order (H1 to H2 to H3).
  8. Make sure focus indicators are visible when tabbing through the page.
  9. Add skip navigation links for keyboard and screen reader users.
  10. Create a public accessibility feedback page with a real contact method.
  11. Document every fix with a date and responsible owner.
  12. Schedule a follow-up manual and assistive-technology test to verify fixes actually work.

Fix keyboard traps and missing form labels first. Both block task completion entirely and carry the highest legal exposure. Cosmetic contrast issues matter, but they rarely stop someone from completing a purchase or filing a form the way a broken tab order does.

The Four Principles Behind Every WCAG Guideline

Every WCAG success criterion, whether it's about alt text or focus order, traces back to four organizing principles, and understanding them makes the guidelines far easier to apply to situations WCAG doesn't explicitly cover.

Perceivable means information must be presentable to users in ways they can perceive, regardless of sensory ability. A video needs captions for deaf users; an image needs alt text for blind users; text needs sufficient contrast for users with low vision.

Operable means interface elements must be usable by everyone, regardless of input method. Someone who can't use a mouse must be able to complete every task with a keyboard alone. Someone with limited fine motor control shouldn't be forced into a drag-and-drop interaction with no alternative.

Understandable means content and interface behavior must be predictable and clear. Error messages need to explain what went wrong and how to fix it, not just flash red. Navigation should behave consistently across pages, not shift unpredictably.

Robust means content must work reliably across different technologies, including current and future assistive tools. This is why semantic HTML matters more than visual styling; a screen reader interprets a properly tagged button differently than a styled div that merely looks like one.

These four principles, often abbreviated POUR, are why a compliance checklist alone isn't enough. A page can pass every individual checklist item and still fail a real user if the underlying structure doesn't hold up to how assistive technology actually parses it.

Accessibility for Video, Mobile Apps, and Emerging Interfaces

Static text and images are the easy part of accessibility. Dynamic content and newer technology formats are where most organizations still fall short, largely because guidance hasn't caught up as fast as the tools have.

Video content needs more than captions. Audio description, a narrated track describing visual action for users who can't see the screen, matters for any video where the visual content carries meaning the audio track alone doesn't convey. Auto-playing video with sound is also a frequent accessibility complaint, since it can interfere with screen readers announcing surrounding page content.

Mobile apps carry their own layer of requirements beyond responsive web design. Touch targets need to be large enough for users with limited motor control, screen reader gesture support (like VoiceOver on iOS or TalkBack on Android) needs to be tested directly rather than assumed, and dynamic content that updates without a page reload needs to be announced to assistive technology through proper ARIA live regions.

Augmented and virtual reality interfaces present the newest and least standardized challenge. Formal WCAG guidance for AR and VR is still developing, but the same core principles apply: users need alternatives to purely visual or purely gestural interaction, subtitle and caption support for spatial audio content, and a way to navigate without relying on precise physical movement. Organizations building in this space should treat the four WCAG principles as their working framework even where a specific success criterion doesn't yet exist for the technology.

Keeping Your Website Compliant After Remediation Ends

Compliance isn't a project with an end date. It's closer to patching a security vulnerability: fix it once, and a new one shows up the next time someone updates the software or publishes new content.

The most common way sites slip back out of compliance is through everyday content updates. A marketing team publishes a new landing page with an inaccessible image carousel. A developer adds a new form field without a label. None of this is malicious; it's just what happens when accessibility isn't built into the daily workflow.

Ongoing monitoring should include quarterly automated scans at minimum, a scheduled manual review at least annually, and immediate testing whenever a major redesign or new feature ships. Any new third-party tool, chat widget, booking system, payment processor, needs an accessibility check before it goes live, not after a user complains.

Treat every WCAG update the same way you'd treat a software patch note. When W3C publishes updates to WCAG 2.2 or eventually WCAG 3.0, review what changed and assess whether your site's current build addresses the new criteria. Waiting for the next DOJ rule update to force the issue means you're always playing catch up instead of staying ahead of it.

Why Most Organizations Get the Timeline Wrong

The biggest misconception in accessibility compliance isn't about the technical standard. It's about timing. Most organizations treat the DOJ's 2027 to 2028 deadlines as distant enough to defer, when in practice a full remediation cycle, audit, fix, verify, retest, routinely takes 12 to 18 months for a mid-size website. Start the clock late and the deadline arrives before the work is done.

The second misconception is treating a passed automated scan as the finish line. It isn't. It's the starting point. Every organization Secure Techies has looked at from a security and compliance standpoint eventually confronts the same gap: automated tools give a false sense of completeness precisely because they produce a clean-looking report. The real test is whether a person using a screen reader or keyboard alone can actually complete the task your website exists to support.

The good news is that accessibility work overlaps heavily with good engineering practice generally. Semantic markup, clean focus management, and clear error handling make sites more maintainable and often improve search visibility, since the same structural signals that help accessibility also help SEO crawlers understand a page. Compliance work rarely turns out to be wasted effort, even for organizations that never face a complaint.

— Alex

How Secure Techies Supports Accessibility Compliance

Secure Techies approaches accessibility the same way it approaches every compliance obligation: audit first, document everything, then build a remediation plan with real owners and deadlines. That's the difference between a one-time scan and a program that actually holds up if a complaint ever arrives.

Securetechie

If your organization needs a WCAG-based accessibility audit alongside the security and compliance work you're already managing, Secure Techies' Compliance & Security Audits service covers exactly this ground, structured triage, prioritized findings, and documentation you can point to if enforcement ever comes knocking. For organizations whose accessibility gaps trace back to an outdated site build rather than isolated fixes, Secure Techies' web development team can rebuild key pages with accessible markup from the ground up, and ongoing managed IT services keep monitoring and uptime in place so a fixed site stays fixed. Schedule an accessibility readiness review to find out exactly where your current site stands before your compliance deadline gets closer than it looks.

This article is general information, not a substitute for advice from a qualified lawyer. Consult a qualified legal professional about your own circumstances before acting on anything here.

Sources

FAQ

What Are the New WCAG Guidelines for 2026?

WCAG 2.2 is the current published standard, adding criteria for focus visibility, consistent help mechanisms, and easier authentication that WCAG 2.1 didn't cover. The DOJ's federal rule still cites WCAG 2.1 Level AA as the legal baseline, but adopting 2.2 now positions organizations ahead of future rule updates since 2.2-conformant content also satisfies 2.1.

Is WCAG the Same as Section 508 Compliance?

No, but they're closely linked. Section 508 is a federal procurement law that incorporates WCAG 2.0 Level AA as its technical requirement for federal agencies and contractors, while WCAG itself is a technical standard published by the W3C that applies more broadly across ADA Title II and Title III contexts.

Is WCAG Legally Required?

WCAG isn't named directly in the original ADA statute, but it's effectively required in practice. The DOJ's 2024 final rule makes WCAG 2.1 Level AA a formal legal requirement for state and local governments, and DOJ guidance treats it as the working standard courts apply when evaluating Title III claims against private businesses.

Can I Be Sued if My Website Is Not ADA Compliant?

Yes. Private lawsuits are the most common enforcement mechanism for businesses covered under Title III, typically triggered when a visitor can't complete a core task like checkout or booking. Prompt response to complaints, a visible accessibility feedback channel, and documented remediation timelines are the strongest practical steps to reduce that risk.

How Much Does an Accessibility Audit Cost?

Costs vary by site size and the depth of manual and assistive-technology testing required, so there's no single flat rate across the industry. Secure Techies' Compliance & Security Audits service scopes accessibility audits based on your specific site and compliance deadline, with current pricing available directly through the service page.