The accessibility deadline your city, school or library cannot miss

If you run the website for a city, a county, a school district, a library, a utility board or any other public entity, there is a date you need on your calendar: April 26, 2027. Smaller entities get one more year, to April 26, 2028.

That is when your website and your mobile apps have to meet a specific accessibility standard under Title II of the Americans with Disabilities Act. Not “be generally accessible.” A published standard, with testable rules.

Here is the plain version of what the rule says, who it covers and what to do about it.

What the rule actually requires

The Department of Justice rule set WCAG 2.1 Level AA as the legal standard. WCAG stands for Web Content Accessibility Guidelines, and it is the same standard the industry has used for years — it is just now written into federal regulation for public entities.

Level AA is a middle tier. It is not the strictest version of the guidelines, and most of it is ordinary good practice:

• Every image carries a text description, so a screen reader can say what it shows.
• Text has enough contrast against its background to be readable by someone with low vision.
• Every function works from a keyboard, for people who cannot use a mouse.
• Video has captions, and pre-recorded audio has a transcript.
• Forms label their fields, and errors say what went wrong and how to fix it.
• Headings and landmarks are used properly, so the page can be navigated by structure rather than by sight.
• Text can be enlarged to 200% without the layout falling apart.

None of that is exotic. It is what a well-built site does anyway. The difference is that after your deadline, it stops being a nice-to-have.

Who has to comply, and by when

The deadline depends on population, not on staff size or budget:

Population comes from the 2020 Census. A special district is a body like a water board, a rural utility authority or a regional transit district, and those fall in the later group regardless of the population they serve.

Both dates moved once already. The original deadlines were April 2026 and April 2027, and in April 2026 the Department of Justice issued an interim final rule pushing each back by a year. Take the extra year as breathing room, not as evidence that it will slip again.

It covers more than the pages you built

This is the part that surprises people. The rule reaches everything provided or made available through your site, including work you did not produce:

• The agenda packets, budgets and meeting minutes you post as PDFs.
• The third-party systems you send residents to — utility billing, permit applications, online payments, job postings, course catalogs.
• Your mobile apps.
• Video of council or board meetings.

If a resident cannot use it, the fact that a vendor built it is not a defense. Which makes your vendor contracts part of this project: renewals between now and the deadline are the moment to ask suppliers for their accessibility conformance report and to get the standard written into the agreement.

The five exceptions

The rule does carve out five categories. Content is excepted if it is:

1. Archived content — posted before the deadline, kept only for reference, and not updated.
2. Preexisting documents — PDFs, Word files and spreadsheets posted before the deadline, unless they are still used to apply for or take part in a service.
3. Third-party posts — content put on your site by people genuinely unaffiliated with you, such as comments on a public forum.
4. Individualized password-protected documents — records about one person, account or property, like a specific utility bill.
5. Preexisting social media posts — posts published before the deadline.

Two cautions. First, “we will call it archived” is not an escape hatch: if residents still need the document to do something, it is not archived. Second, the exceptions only limit this rule. Your broader ADA duty to communicate effectively with people with disabilities does not go away.

Where to start, in order

You do not have to solve everything at once. A sensible sequence:

1. Find out where you stand. Run an automated scan to get a baseline, then have someone test the important paths by keyboard and with a screen reader. Automated tools catch perhaps a third of the issues. They will not tell you that your alt text is unhelpful or that your menu is a trap.

2. Fix the paths that matter most. Paying a bill, applying for a permit, finding a meeting agenda, contacting a department, reading an emergency notice. A council biography page can wait.

3. Deal with the documents. Most public entities find the PDF pile is the largest part of the job. Often the right answer is not remediating hundreds of old files, but putting the current information on a web page instead.

4. Stop the bleeding. Set a rule that new content meets the standard before it is published, and train whoever posts it. Otherwise you will be remediating the same site again in two years.

5. Write it down. Keep a record of what you tested, what you fixed and what is scheduled. An accessibility statement with a way to report a problem is both required practice and a good-faith signal.

The honest reason to do it

The deadline is the reason this is on your list. It is not the reason it matters.

About one in four American adults lives with a disability. For a public entity, a website is not marketing — it is how people pay a bill, enroll a child, request a service and find out whether the water is safe to drink. When the site is unusable, the people it fails are the ones with the least ability to work around it.

Meeting the standard is the floor. For the larger entities it arrives in spring 2027, which is less time than it sounds once budgets, vendor contracts and a backlog of documents are involved; everyone else has a year beyond that. The entities that treat it as a rebuilding project rather than a patching project will end up with better websites, not just compliant ones.

Sources

• Extension of Compliance Dates for Nondiscrimination on the Basis of Disability — the interim final rule, as published in the Federal Register on April 20, 2026.
• Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments — the Department of Justice’s own summary of the 2024 rule, including the exceptions.
• Web Content Accessibility Guidelines (WCAG) 2.1 — the standard itself, from the W3C.
• Disability Impacts All of Us — the Centers for Disease Control and Prevention on disability prevalence in the United States.

Need a read on where your site stands? We work with public entities and private organizations across Arkansas on accessibility, and we can start with an audit of your most-used pages and a plan you can budget against.