The ADA website deadline moved to 2027. Here is what did not change for Oklahoma cities and towns.

By Michael Bridges, CEO, Digital Venture

Bixby, Oklahoma. Published September 2026.

If you run a city or town in Oklahoma, you probably heard some version of "the ADA title II website deadline got pushed" this spring and felt your shoulders drop an inch. Fair enough. The extra year is real and it is useful.

But the extension changed one thing, the date, and left everything else in place. With the Oklahoma Municipal League Annual Conference coming to Tulsa on September 15 to 17, this is a good moment to be precise about what moved, what did not, and what a town of 4,000 people with one IT contractor should actually do about it.

This is general information from a web vendor, not legal advice. Your city attorney and a qualified accessibility professional should confirm how the rule applies to you and your ADA-related website accessibility obligations.

Did the ADA Title II website deadline get extended?

Yes. The DOJ published an interim final rule on April 20, 2026 that extends the compliance dates in its 2024 Title II web and mobile app rule by one year. The ADA Title II web accessibility rule still establishes accessibility requirements for online content and digital platforms used to provide government services.

The Federal Register notice is explicit that the amendment "extends the compliance dates but does not alter the other provisions" of the 2024 rule, and that public entities "continue to have an ongoing obligation" to make their services, programs and activities accessible under Title II. In other words, April 2027 is a compliance milestone for the technical standard. It is not the date accessibility starts.

DOJ's own stated reason for the delay is worth reading: it said automated tools, including generative AI, had not delivered the remediation it expected, and that small governments lacked the staff and money to finish on time. That is an honest description of the compliance resource constraints. It is not a waiver.

Does the rule apply to towns under 50,000?

Yes. Smaller towns got more time, not an exemption under the Americans with Disabilities Act or other federal regulations.

Here is what that means in Oklahoma. By the 2020 Census, exactly nine cities are at or above 50,000: Oklahoma City, Tulsa, Norman, Broken Arrow, Edmond, Lawton, Moore, Midwest City and Enid. Those nine, along with the larger counties, are on the April 2027 date. The other several hundred municipalities in the state are on April 2028.

The threshold is population, and only population. It is not based on your number of employees, your website traffic, your budget, or how many residents use online services. A department, library or utility office is generally treated as part of the city or county it belongs to, so it uses that larger entity's population, not its own headcount. The rule therefore applies broadly to public entities serving populations of different sizes.

Two cautions. First, confirm your classification rather than assuming it. Second, state law, grant conditions, federal funding rules and vendor contracts can carry their own accessibility requirements on their own timelines, and the DOJ extension did not touch any of those.

What is WCAG 2.1 AA in plain English?

WCAG stands for Web Content Accessibility Guidelines. Version 2.1, Level AA, is the technical standard the DOJ rule adopted. These W3C Web Content Accessibility Guidelines provide specific accessibility standards and success criteria for digital content. Stripped of the jargon, it asks whether a resident with a disability can do what every other resident can do on your site.

That means a resident can move through your site with a keyboard alone. A screen reader can make sense of your headings, menus, buttons and images. Text has enough contrast to read and can be enlarged without breaking the page. Forms can be filled out, and error messages say what went wrong. Videos have captions. Links say where they go. These are central conformance requirements, not optional design preferences. For municipalities evaluating the technical side of accessibility, accessible web development should include accessibility checks during testing, along with performance, browser and device reviews.

The part most cities miss is that the standard covers more than the homepage. It reaches your permit application, your utility payment portal, your council agendas and minutes, your meeting videos, your recreation sign-ups, and the PDFs behind all of them. It applies to online content, academic course content where relevant, digital course materials, and other designed web-based information made available through government digital environments.

The most useful question is not “does our site pass a scan?” but “can a resident who cannot see the screen apply for a building permit, pay a water bill, and find tonight’s agenda without calling us?”

Do I have to fix old PDFs?

Some, not all, and the distinction is about use, not age.

The 2024 rule includes an exception for conventional electronic documents (PDFs, Word files, spreadsheets, slide decks) that were posted before your compliance date, as long as they are not currently being used to apply for, access or participate in a service, program or activity. An archived 2017 council packet can likely stay as it is. A business license application from 2017 that residents still download and fill out cannot.

Two things pull a document out of the exception. One is active use, as above. The other is editing: DOJ's guidance says that updating a previously posted document can affect whether the exception still applies. If someone on staff opens an old PDF to change a fee or a phone number and reposts it, treat it as new.

The practical move is an inventory. Sort every document your site hosts into a handful of buckets and act accordingly.

Are accessibility overlay widgets compliant?

No. An overlay is not a substitute for an accessible website, and presenting one as your compliance strategy is a risk, not a shield.

Overlays are the small icons that offer text resizing, contrast toggles and similar features. Some also claim to fix underlying code automatically. They cannot reliably repair the things that actually block residents: missing or wrong image descriptions, broken heading structure, forms with no labels, PDFs with no reading order, keyboard traps, uncaptioned video, and third-party payment or permitting systems the widget cannot touch.

The DOJ rule measures the accessibility of the content itself, not the presence of a tool. It also expects access through the same pages everyone else uses; a separate “accessible version” is allowed only when a technical or legal limitation prevents fixing the original.

If a vendor tells you a widget solves Title II, that is the moment to get a second opinion. A municipality may need accessible website design or focused remediation of its existing site, depending on the condition of the current platform.

What counts as a good faith effort?

A documented, active program. Not a statement of intent, not a widget, and not a plan to start in early 2028.

The rule does contain limited defenses, including undue burden and fundamental alteration, but they are fact-specific and decided after the fact. What holds up in practice is evidence that you identified barriers, prioritized the ones that block essential services, assigned owners, spent real money in a sensible order, and kept going.

Concretely, a strong record looks like this: a named accessibility lead, an inventory of websites, forms, documents, portals and apps, test results for the highest-traffic resident tasks, a prioritized remediation schedule with a budget attached, procurement language requiring WCAG 2.1 AA and vendor proof, such as a VPAT or accessibility conformance report, training for the staff who publish content, a public way to report a barrier, and a log of what was tested, what was fixed, what is still open and who owns it.

For cities that need outside support with government-ready digital support, the vendor should be able to explain its accessibility process, documentation practices, testing responsibilities and approach to third-party systems.

Documentation should be specific enough that someone else could pick it up. “Website reviewed” is not a record. “Permit application form tested with keyboard and NVDA on August 12, three label errors found, two fixed, one open with the vendor, retest scheduled September 30” is.

Can we wait until budget season?

You can wait to fund the fixes. You should not wait to find out what they are.

Oklahoma municipal fiscal years start July 1, and most budgets get built in the first quarter of the calendar year. That is the right time to request money for an assessment, document remediation, captioning, accessible meeting technology, vendor changes, staff training and ongoing testing. It is the wrong time to be discovering the scope of the problem for the first time.

A practical monthly website review process can help a small municipal team turn accessibility checks, content updates, form reviews, broken-link checks and vendor follow-up into recurring work instead of a once-a-year scramble.

Three things worth doing before budget season, none of which require a new website:

1. Inventory the digital services residents rely on. Websites, forms, PDFs, payment portals, meeting platforms, mobile apps and every third-party tool with your logo on it.
2. Test the five tasks that matter most. Applying for a permit, paying a bill, registering for a program, finding an agenda or emergency notice, and contacting a department. Use a keyboard and a free screen reader, or have someone who uses one every day try it.
3. Get a phased remediation plan with numbers on it. Priorities, estimated costs, who is responsible for each item, and how it will be maintained. A one-time promise is not a plan.

With that in hand, council can make an informed choice between fixing the current site, replacing an aging system, or spreading the work across departments and fiscal years. If the current platform is too difficult to maintain or remediate, web development services may be part of a longer-term replacement plan.

Does the National Federation of the Blind lawsuit change the deadline?

Not yet, and you should plan as if it might.

On May 21, 2026, the National Federation of the Blind sued the Department of Justice and the Department of Health and Human Services in federal court in Maryland, asking the court to vacate the interim final rules and restore the original deadlines. The complaint argues the agencies skipped the notice-and-comment process the Administrative Procedure Act requires and did not adequately weigh the harm of delaying digital access. The case is pending.

A pending lawsuit is not a ruling. Do not assume the extension will be overturned, and do not assume it is permanent. The sensible course is to work toward the 2027 and 2028 dates while watching for a decision. A city that has already finished its inventory and plan can absorb a schedule change. A city that has not cannot.

What should every Oklahoma city or town do next?

Before OML, five questions for the manager, the clerk and whoever owns the website:

1. Which population threshold applies to us, and have we confirmed it rather than assumed?
2. Which online services do residents actually use most?
3. Which forms, PDFs and applications create the biggest barriers today?
4. Which vendors control pieces of our digital experience, and what do their contracts say about accessibility?
5. What should we fund, fix, test and document in the next budget cycle?

Accessibility is an operational responsibility, not an IT ticket. It belongs to leadership, communications, department owners, procurement and every vendor you pay. That is why ongoing website maintenance should include more than security updates and backups. It should also support content quality, form functionality, broken-link checks, accessibility follow-up and documentation.

The federal deadline moved. The responsibility to serve every resident did not.

Will your city or town use the extra time to plan, or let the deadline force the conversation?

About Digital Venture. Digital Venture is a veteran-owned digital agency in Bixby, Oklahoma that designs, builds and maintains accessible websites for commercial, tribal and government clients, including federal past performance with the Department of Defense. If you will be at the OML Annual Conference in Tulsa on September 15 to 17, bring your city's web address. We will look at your top three resident tasks with you on the spot, no charge and no pitch.

Sources: Federal Register, Extension of Compliance Dates for Nondiscrimination on the Basis of Disability (April 20, 2026); Federal Register, Nondiscrimination on the Basis of Disability: Accessibility of Web Information and Services of State and Local Government Entities (April 24, 2024); U.S. Department of Justice Title II web rule fact sheet; National Federation of the Blind press release (May 21, 2026); WebAIM Million 2026; AccessLumens, The State of US Local Government Accessibility 2026 (July 2026); Federal Trade Commission v. accessiBe (January 2025); U.S. Census Bureau, 2020 Decennial Census; Oklahoma Municipal League.

​Further reading

• Extension of compliance dates for Title II web accessibility
  U.S. Department of Justice, Federal Register, April 20, 2026. The interim final rule establishes the April 26, 2027 deadline for public entities with populations of 50,000 or more and the April 26, 2028 deadline for smaller public entities and special districts.
• DOJ fact sheet on web and mobile app accessibility
  U.S. Department of Justice, ADA.gov, March 8, 2024. This plain-language overview explains the Title II rule, WCAG 2.1 Level AA, covered government services, and exceptions for certain older content and documents.
• DOJ’s first steps guide for state and local governments
  U.S. Department of Justice, ADA.gov, accessed August 27, 2026. The guide offers practical direction on assessing websites, mobile apps, PDFs, third-party systems, accessibility exceptions, and ongoing ADA responsibilities.
• Current ADA Title II regulations
  U.S. Department of Justice, ADA.gov, current regulation accessed August 27, 2026. Review the regulatory language covering WCAG 2.1 Level AA, archived web content, preexisting electronic documents, third-party content, and related exceptions.
• Web Content Accessibility Guidelines (WCAG) 2.1
  World Wide Web Consortium, Web Accessibility Initiative, June 5, 2018. This is the technical standard behind WCAG 2.1 Level AA, including requirements related to keyboard access, headings, forms, contrast, captions, links, and assistive technology.
• Understanding WCAG 2.1
  World Wide Web Consortium, Web Accessibility Initiative, updated February 11, 2026. The guide explains how WCAG success criteria work and why automated scans should be supplemented with manual review, assistive-technology testing, and usability testing.
• City and town population totals: 2020–2025
  U.S. Census Bureau, May 2026. Use these population estimates and Census data files to verify the population classification that may determine which Title II compliance date applies to a municipality.
• Service Oklahoma OK Mobile ID accessibility resolution
  U.S. Department of Justice, Civil Rights Division, November 13, 2023. This Oklahoma example illustrates the importance of accessibility testing, ongoing monitoring, public feedback procedures, and equal access to government digital services.
• National Federation of the Blind lawsuit over the deadline extensions
  Democracy Forward, May 21, 2026. This filing explains the challenge to the DOJ and HHS extensions and the plaintiffs’ argument that delaying digital accessibility protections harms access to essential government and healthcare services.
• FTC case involving accessiBe
  Federal Trade Commission, final order approved April 22, 2025. The case is a useful reminder that automated accessibility products should not be presented as proof that an entire website complies with WCAG.