Skip to content

The April 2027 ADA Website Deadline: What Alabama Agencies, Boards, and Cities Need to Know

Your Website Has a Legal Deadline

What the ADA Title II rule requires, what WCAG 2.1 AA means, and how to get ready

Key takeaways

Deadline

April 26, 2027 for states and local governments serving 50,000+ people. April 26, 2028 for smaller local governments and special districts.

Standard

WCAG 2.1 Level AA, which means 50 testable success criteria.

Scope

Every page, PDF, form, and app the agency offers, including services a vendor runs for it under contract.

Try it

Six live pass/fail examples and the full checklist are below.

If your organization is a state agency, licensing board, city, county, school system, or public university, your website now has a legal deadline. This guide explains what the rule requires and what WCAG 2.1 AA means in plain language. You can also try six of its rules yourself in the live examples below.

What is the ADA Title II web accessibility rule?

In April 2024, the U.S. Department of Justice (DOJ) finalized a rule under Title II of the Americans with Disabilities Act. It covers the web content and mobile apps that state and local governments provide, including services that vendors and contractors provide on its behalf. For the first time, it sets a specific technical standard that these sites must meet: the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

When is the ADA website compliance deadline?

On April 20, 2026, the DOJ published an interim final rule that pushed every deadline back by one year:

WhoOriginal deadlineNew deadline
State governments, and local governments serving 50,000 or more peopleApril 24, 2026April 26, 2027
Local governments serving fewer than 50,000 people, and all special district governmentsApril 26, 2027April 26, 2028

Every Alabama state agency and licensing board falls under the April 2027 deadline. The extension changed only the dates. WCAG 2.1 Level AA is still the standard.

Laptop on a desk showing a website with the words ADA Compliant across the screen

What is WCAG 2.1 AA?

WCAG is published by the World Wide Web Consortium (W3C), the organization that sets web standards. Version 2.1 was published in June 2018. It’s written as testable success criteria, each of which a page either passes or fails. That pass/fail structure is why it works as a legal standard.

The success criteria are organized under four principles, often called POUR.

Perceivable

People can see or hear the content, with text alternatives, captions, and strong color contrast.

Operable

Everything works with a keyboard, focus is always visible, and nothing flashes.

Understandable

Pages behave predictably, and forms explain errors in plain words.

Robust

Clean code that screen readers and voice control can use reliably.

Three conformance levels

Each level builds on the one before it.

Level AThe essentials
30 criteria
Level AARequired by law
30
+20 = 50
Level AAANot required
30
+20
+28

The target. Meet all 50 Level A and AA criteria to conform to WCAG 2.1 AA, the level the ADA Title II rule requires.

What does ADA website compliance cover?

The rule covers far more than the homepage:

  • Every web page, including news posts, meeting notices, and minutes
  • PDFs and other documents posted online, such as forms, rules, and reports
  • Online forms, application portals, and payment pages, including those run by outside vendors
  • Images (which need alt text), videos (which need captions), and color contrast
  • Keyboard navigation and screen reader compatibility

For most boards and agencies, the biggest job isn’t the design. It’s years of PDFs that a screen reader can’t read.

Interactive tool

Try It Yourself: The Interactive WCAG 2.1 AA Lab

Six hands-on examples. Each puts a failing version beside a passing one, with the code for both.

Each example below puts a deliberately failing version (red) beside a passing one (green), with the code for both. Try the contrast checker, submit the forms, or press Tab to test keyboard access.

1. Color contrast checker

1.4.3 Contrast (Minimum) AA1.4.11 Non-text Contrast AA

Pick a text color and a background. The ratio is calculated with the WCAG relative-luminance formula, the same math audit tools use. Light gray text on white is the most common failure we find on government sites.

Try a common case

License renewal opens Dec 1

Renew online before your license expires to avoid a late fee.

2.85 : 1

    2. Images need text alternatives

    1.1.1 Non-text Content A

    Screen readers read an image's alt text aloud. When it's missing, the reader often reads the file name instead. The announcements below come from each image's real alt attribute.

    Fails chart_final_v2.png
    Screen reader says

    A common real-world example: a logo whose alt text is site-header, which is a file name, not a description.

    Passes Bar chart of license renewals by month, January to December. Renewals peak in December at 412.
    Screen reader says

    Decorative images get an empty alt="" so they're skipped entirely.

    Show the code

    Fails

    Passes

    3. Forms that explain themselves

    1.3.1 A1.3.5 Input Purpose AA3.3.1 A3.3.3 Error Suggestion AA4.1.3 Status Messages AA

    Submit both forms empty, then with a bad email. The failing form only turns borders red, which a blind or colorblind user can't detect. The passing form names each error, says how to fix it, and announces the result. Nothing is sent anywhere; this is a demo.

    Fails
    Submit
    Passes

    Numbers only, for example 2221

    Show the code

    Fails

    Passes

    4. Keyboard access and visible focus

    2.1.1 Keyboard A2.4.7 Focus Visible AA4.1.2 Name, Role, Value A

    Click "Start here," then press Tab repeatedly. The log records every stop. In the failing example, the "button" is a styled div that the keyboard skips entirely, and the link's focus outline was removed, so you can't see where you are.

    Fails
    Renew license
    Verify a license
    Passes
    Verify a license
    1. Waiting for Tab key…
    Show the code

    Fails

    Passes

    5. Headings and link text that make sense out of context

    1.3.1 A2.4.4 Link Purpose A2.4.6 Headings and Labels AA

    Screen reader users jump through a page by its headings list and links list. The lists under each sample show what a screen reader would announce from that markup. The failing sample uses patterns we often find on government sites: headings that jump from H1 to H3 to H6, a raw URL as link text, and repeated "click here."

    Fails
    Headings list
      Links list
        Passes
        Headings list
          Links list
            Show the code

            Fails

            Passes

            6. Zoom, reflow, and text spacing

            1.4.4 Resize Text AA1.4.10 Reflow AA1.4.12 Text Spacing AA

            At 400% zoom, a laptop screen behaves like a 320-pixel-wide phone. Content must reflow without sideways scrolling. People with dyslexia or low vision often widen text spacing. WCAG requires that nothing gets cut off at line height 1.5, paragraph spacing 2×, letter spacing 0.12×, and word spacing 0.16× the font size.

            Fails

            Notice to applicants

            All credit card transactions carry a 3.5% processing fee. Renewal applications received after the expiration date are subject to a late fee set by the Board.

            Fixed 560 px width and fixed height: it scrolls sideways and clips text.

            Passes

            Notice to applicants

            All credit card transactions carry a 3.5% processing fee. Renewal applications received after the expiration date are subject to a late fee set by the Board.

            Flexible width, no fixed height, sizes in rem: it reflows and grows.

            Show the code

            Fails

            Passes

            How do you make a website ADA compliant?

            1. Audit the current site. Combine automated scans with a manual screen reader and keyboard review. Automated tools catch only part of the problems.
            2. Inventory your documents. Decide which PDFs to fix, which to turn into web pages, and which to archive.
            3. Fix the foundation. That means proper headings, descriptive links, labeled forms, sufficient contrast, and visible keyboard focus.
            4. Publish an accessibility statement with a clear way for the public to report barriers.
            5. Monitor it. Every new post or upload can introduce new errors, so accessibility needs ongoing maintenance, just like security.

            Don’t wait for 2027. Redesigns, document remediation, and staff training take months, and accessibility vendors will be busier as the deadline approaches.

            Interactive checklist

            The Complete WCAG 2.1 Level AA Checklist

            All 50 success criteria in plain language. Filter by level or principle, or search for a topic like contrast or keyboard.

            Showing 50 of 50 criteria

            WCAG 2.1 Level A and AA success criteria
            CriterionNameLevelIn plain language

            Frequently asked questions

            4 questions. Select one to see the answer.

            April 26, 2027 is the current deadline for state governments and for local governments serving 50,000 or more people, under the DOJ's April 2026 interim final rule. The DOJ took public comments on the extension through June 22, 2026, so check for updates. The technical standard, WCAG 2.1 Level AA, didn't change.

            Yes. Documents posted on a covered website are web content. The rule has limited exceptions, such as certain archived content and preexisting documents that aren't currently used, but any document the public needs to use should be accessible.

            No. Overlay widgets don't fix the underlying code. WCAG conformance comes from building and maintaining the site correctly.

            It depends on the number of pages and documents and how the site is built. Yellowhammer IT includes WCAG 2.1 AA design, hosting, security, and ongoing monitoring in one flat monthly price, with no per-page fees.

            How Yellowhammer IT helps

            Yellowhammer IT is a veteran-owned Alabama IT and cybersecurity firm. We’ve delivered ADA-compliant websites for healthcare organizations and universities, and we build every site to WCAG 2.1 AA from day one. Learn about our website development and cybersecurity services, or request a free accessibility check of your website.