On April 20, 2026, the Department of Justice published an Interim Final Rule extending the compliance deadlines for the ADA Title II web and mobile application accessibility requirements originally adopted on April 24, 2024. This is significant news for every state and local government IT organization.

The original rule required state and local governments to ensure their web content and mobile apps meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA technical standard. The new Interim Final Rule shifts those deadlines:

For government IT leaders, this extra year is not a reason to slow down. It is an opportunity to build a more comprehensive and sustainable accessibility program rather than rushing to check boxes.

Why the DOJ Extended the Deadlines

The DOJ cited several factors in its decision (91 FR 20902):

• Technology gaps: Advanced technology, including generative AI, does not yet reliably automate the remediation of inaccessible content at scale. Human oversight remains essential, particularly for complex content like STEM materials.
• Resource constraints: Many state and local governments, particularly smaller entities and school districts, reported limited financial and staffing resources for compliance. The Small Business Administration’s Office of Advocacy noted that compliance burdens were underestimated for small public entities.
• AI-generated content risks: Government agencies are increasingly using generative AI to produce web content, but that AI-generated content is often inaccessible by default (for example, AI image generators do not produce alternative text).
• Litigation risk concerns: Without the extension, agencies that had not yet achieved compliance would face immediate litigation exposure, even where circumstances outside their control prevented timely compliance.

Importantly, the DOJ emphasized that the underlying requirement remains unchanged: state and local governments must make their web content and mobile apps meet WCAG 2.1 Level AA. The rule’s substantive obligations are not going away; only the enforcement timeline has shifted.

What WCAG 2.1 Level AA Actually Requires

For IT teams beginning their accessibility journey, WCAG 2.1 Level AA is organized around four principles:

1. Perceivable: Content must be presentable in ways all users can perceive (alt text for images, captions for video, sufficient color contrast).
2. Operable: UI components and navigation must be operable via keyboard, with no time-dependent interactions that cannot be adjusted.
3. Understandable: Information and operation of the UI must be understandable (readable text, predictable behavior, input assistance).
4. Robust: Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies like screen readers.

The ADA.gov fact sheet on the web accessibility rule provides a plain-language overview of these requirements and the limited exceptions (archived content, preexisting documents, third-party posts, and password-protected individualized documents).

How Azure and Microsoft Tools Help You Prepare

The extended deadline is an opportunity to invest in the right tooling and processes. Microsoft offers a comprehensive set of tools across the development lifecycle that directly support WCAG 2.1 Level AA compliance.

GitHub Accessibility Scanner: AI-Powered Scanning and Remediation

The GitHub Accessibility Scanner is an AI-powered GitHub Action from GitHub that detects accessibility barriers across your websites, automatically creates trackable GitHub Issues for each finding, and leverages GitHub Copilot to propose fixes via pull requests. For government development teams working toward WCAG compliance, this is the most impactful tool you can add to your CI/CD pipeline.

• Automated scanning runs axe-core and additional plugins against your live URLs, catching WCAG violations across your entire site without manual testing.
• Issue tracking automatically files a GitHub Issue for each accessibility finding, giving your team a clear remediation backlog with full context.
• AI-powered fixes assign issues to GitHub Copilot, which can open pull requests with proposed code changes that your team reviews before merging, dramatically accelerating the remediation cycle.
• Reflow scanning detects issues with content reflow at different viewport sizes, addressing WCAG 2.1 success criteria around responsive design (Success Criterion 1.4.10).

Setting up the scanner in your repository is straightforward:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

# Example GitHub Actions workflow for the Accessibility Scanner
name: Accessibility Scanner
on: workflow_dispatch

jobs:
  accessibility_scanner:
    runs-on: ubuntu-latest
    steps:
      - uses: github/accessibility-scanner@v3
        with:
          urls: |
            https://your-government-site.gov
          repository: your-org/your-repo
          token: ${{ secrets.GH_TOKEN }}
          cache_key: a11y-scan-gov-site

The scanner requires a fine-grained Personal Access Token with write access to actions, contents, issues, and pull requests. It supports authenticated scanning for sites behind login pages, screenshot capture for visual context in filed issues, and grouped tracking issues that organize findings by violation type. For government teams managing multiple web properties, you can configure separate workflows per site and use the cache_key parameter to track results independently across runs.

Azure AI Speech Service: Captioning and Audio Accessibility

WCAG 2.1 Level AA requires captions for prerecorded and live audio content (Success Criteria 1.2.2 and 1.2.4). Azure AI Speech Service provides:

• Real-time speech-to-text transcription for live events such as town halls and public meetings, supporting automatic captioning.
• Batch transcription for processing archived recordings of council meetings, public hearings, or training sessions.
• Text-to-speech with neural voices for generating audio versions of web content, supporting users with visual impairments or reading difficulties.

Azure Speech Service is available in Azure Government (US Gov Virginia and US Gov Arizona regions), supporting real-time transcription, batch transcription, custom speech, and neural voice capabilities. This is critical for agencies that must keep data within FedRAMP-authorized boundaries.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15

// Example: Real-time captioning for a public meeting using Azure Speech SDK
var speechConfig = SpeechConfig.FromSubscription("YourSubscriptionKey", "usgovvirginia");
speechConfig.SpeechRecognitionLanguage = "en-US";

using var recognizer = new SpeechRecognizer(speechConfig);
recognizer.Recognized += (s, e) =>
{
    if (e.Result.Reason == ResultReason.RecognizedSpeech)
    {
        // Send caption text to your live captioning display
        Console.WriteLine($"Caption: {e.Result.Text}");
    }
};

await recognizer.StartContinuousRecognitionAsync();

Azure AI Vision and Document Intelligence: Alt Text and Document Remediation

Azure AI Vision can generate image descriptions programmatically, helping agencies add alternative text to the thousands of images on their websites. Azure Document Intelligence extracts structured content from PDFs and scanned documents, a key capability for remediating the backlog of inaccessible PDF documents that many government websites have accumulated.

While the DOJ noted that AI cannot yet fully automate accessibility remediation at scale, these tools significantly accelerate the process when combined with human review.

Immersive Reader: Built-In Reading Accessibility

Azure Immersive Reader is an inclusively designed tool that can be embedded directly into government web applications. It provides text-to-speech, syllable splitting, part-of-speech highlighting, real-time translation, and a picture dictionary, all of which improve reading comprehension for users with learning differences such as dyslexia.

Immersive Reader is available as a client library for C#, JavaScript, Java, Kotlin, and Swift, making it straightforward to integrate into existing web portals and citizen-facing applications.

Microsoft 365 Accessibility Checker

Government staff produce thousands of documents, presentations, and spreadsheets that end up on public websites. The built-in Accessibility Checker in Microsoft 365 evaluates content against accessibility standards and provides specific fix-it guidance. Training staff to run the Accessibility Checker before publishing documents is one of the simplest, highest-impact steps any agency can take.

Building an Accessibility Roadmap: Practical Steps

With the extended deadline, here is a practical approach for government IT organizations:

Phase 1 - Assess (Months 1-3):

• Audit your web properties using Accessibility Insights Assessment mode
• Inventory all PDF documents and multimedia content on your sites
• Identify third-party vendor applications that need accessibility evaluation
• Establish a baseline WCAG 2.1 AA compliance score

Phase 2 - Remediate (Months 4-9):

• Fix critical issues identified by FastPass across all public-facing sites
• Implement Azure AI Speech for captioning video and audio content
• Use Azure Document Intelligence to begin remediating PDF backlogs
• Integrate automated accessibility checks into your CI/CD pipelines

Phase 3 - Sustain (Months 10-12+):

• Train content creators on the Microsoft 365 Accessibility Checker
• Establish accessibility review gates in your content publishing workflow
• Embed Immersive Reader in citizen-facing portals
• Set up recurring automated scans to catch regressions

Why This Matters for Government

The one-year extension is welcome news, but the clock is still ticking. Every state and local government in the country must bring its web content and mobile apps into WCAG 2.1 Level AA compliance. The consequences of inaction are real: the ADA includes a private right of action, meaning citizens can file lawsuits against non-compliant agencies and recover attorneys’ fees.

More importantly, digital accessibility is a civil rights obligation. The DOJ’s rule exists because millions of Americans with disabilities are unable to access government services that are quickly and easily available to others online: applying for permits, paying utility bills, accessing public meeting information, or participating in civic life.

The DOJ’s own analysis highlighted that generative AI is creating new accessibility challenges as agencies adopt it for content creation. AI-generated images without alt text, AI-produced documents without proper heading structure, and AI-created web content without semantic markup all create barriers. Government agencies adopting AI tools should be building accessibility requirements into their AI governance frameworks now.

Microsoft’s ecosystem of accessibility tools, from developer testing with Accessibility Insights to AI-powered remediation with Azure AI services to content-creation guardrails in Microsoft 365, provides a comprehensive toolkit for meeting this challenge. The key is to start now and use the extended timeline to build sustainable processes rather than treating compliance as a one-time project.

The Microsoft Accessibility Fundamentals learning path is a free training resource that can help your team build foundational knowledge, and Microsoft’s Accessibility page provides ongoing updates on accessibility features across the product portfolio.

The deadline may have moved, but the obligation has not. Use this time wisely.