Does your special district's website have to meet WCAG 2.1 AA by April 2028?

Water, fire, park, transit and library districts must make their websites meet WCAG 2.1 Level AA by April 26, 2028, whatever their size. Here is what the rule covers, which exceptions to check with counsel, what to fix first and how to buy the work.

If you run a water, fire, park, transit or library district, the short answer is yes. Under the Justice Department's Title II web rule, your district's website and any app you offer must meet WCAG 2.1 Level AA by April 26, 2028. This guide is for general managers and board clerks: what the rule covers, what to fix first and how to buy the work.

We are not lawyers and this is not legal advice. Use it as a plan to take to your counsel and your board.

Who counts as a special district, and why the date is April 2028.

The Census Bureau treats special districts as their own governments, with their own boards and budgets, separate from the county or city around them. It counted 40,199 special district governments in 2025. Water and sewer, fire protection, parks, transit, library, irrigation and hospital districts all sit in that group.

The 2024 rule first set April 24, 2026 for public entities of 50,000 people or more and April 26, 2027 for smaller entities and special districts. In April 2026 the Justice Department published an interim final rule that added one year, so smaller entities and special districts now have until April 26, 2028. The DOJ fact sheet confirms that date for any special district government and keeps WCAG 2.1 Level AA as the standard.

Two things matter for a district. Your population does not change your date: special districts get April 26, 2028 no matter how many people they serve. And the rule may still move. The extension left the requirements as they were, and the DOJ signaled it intends to conduct additional review of the digital accessibility requirements. Plan to the current rule and keep an eye on updates. If your district takes HHS funding, a hospital district for example, ask counsel about the separate Section 504 rules, which run on their own dates.

What the rule covers on a small district's website.

A simple test: can a resident use this page or file to do something with the district? If yes, assume it is covered. On a typical district site that means:

• Board agendas, packets and minutes, including the PDFs most districts post them as
• Rate notices, budgets, water quality reports and public hearing notices
• Forms to start service, apply for a permit, rent a facility or request records
• Bill pay portals, outage maps, meeting video, agenda software and event sign-ups
• Emergency notices, including any posted as an image or a scanned flyer

Tools you buy from vendors count too. The rule reaches content a public entity provides directly or through contractual, licensing or other arrangements. If residents pay their water bill through your billing vendor's portal, that portal is part of your obligation.

A login does not get you off the hook either. The DOJ's own water bill example says a PDF about a rate increase for all customers, posted behind a password, still usually needs to meet WCAG 2.1 Level AA.

The exceptions to check with counsel.

The rule has five exceptions: archived web content, preexisting conventional electronic documents, third-party content not posted under a contract or agreement, individualized password-protected documents and preexisting social media posts. Two of them matter most to districts with years of PDFs online.

Archived content only qualifies when it meets all four points: created before your compliance date, kept only for reference, research or recordkeeping, kept in a separate area marked as archived and left unchanged since. Labeling a file "archive" on a live page is not enough.

Older documents get their own exception. PDFs, Word files, spreadsheets and slides posted before your compliance date are exempt unless they are currently used to apply for, gain access to or participate in your services. So minutes from 2019 can likely stay as they are, while a 2015 service application that people still download cannot. Where that line falls for your records is a question for counsel.

What to fix first on a small budget and a small staff.

Most districts have one or two people who touch the website. Work in this order: what residents need to act on, then the site's page templates, then the documents you publish every month, then the old material. Start publishing new documents accessibly now, so the backlog stops growing while you work on the rest.

The table below is the order we would suggest to a district with a small staff. It uses the April 26, 2028 compliance date from the DOJ fact sheet, counts vendor tools as yours because the rule covers content provided through contractual, licensing or other arrangements and treats old documents as exempt only when they are not currently used to reach a service.

Two cheap wins: delete pages nobody visits, and train the clerk to use real headings and alt text in Word before exporting to PDF. If your site sits on an old WordPress install with a stack of plugins, fixing every template can cost more than starting again. Our free Website Health Check shows how outdated and exposed a site is, which helps you decide between repair and a website rebuild.

How to buy the work.

Keep the scope short. One or two pages is enough: the sections of the site, the vendor tools you use, roughly how many documents you post each month, the standard (WCAG 2.1 Level AA) and the date you need it done. Our guide on how to write a website RFP has a structure you can borrow.

Then ask every bidder the same questions:

• How do you test? Look for automated scans plus manual keyboard and screen reader checks on each page template, done by a named person.
• Do you rely on an overlay widget? A script added on top will not tag your PDFs or label your forms.
• Will you test our vendor tools and give us a written list of problems to send to those vendors?
• What do we get at the end: an issues log, the fixes and an accessibility statement?
• Who fixes problems after launch? How fast, at what cost and for how long?
• Will you train our clerk to publish accessible documents without you?
• Do we own the site and its content if we leave?

Nobody can promise a district it will never face a complaint; treat a bidder who does as a warning sign. What you can buy is a site built on accessible templates, staff who know how to keep it that way and a record showing you did the work.

We build public sector and contractor websites on Next.js and Payload CMS, where accessible page templates are set once and staff publish into them. See how we work with government contractors and public bodies, or read our wider guide to the ADA Title II website deadlines.