The Title II web rule and its two compliance dates by population
Local government websites are about to face their first uniform federal accessibility standard. In April 2024, the Department of Justice finalized new regulations under Title II of the Americans with Disabilities Act. Cities, towns, counties, and special districts must ensure their web content is accessible to people with disabilities. The rule sets two main compliance deadlines, based on population.
Jurisdictions with a population of 50,000 or more have until April 24, 2026, to bring their web content up to standard. Smaller jurisdictions get an extra year, with a deadline of April 26, 2027. These dates cover websites, documents uploaded since 2012, and web applications used by the public. The rule also applies to essential service information, online forms, agendas, meeting minutes, and streamed or recorded meetings.
The new requirements aim to bring consistency across states. Until now, local governments faced a patchwork of lawsuits, guidance, and voluntary adoption. By connecting compliance to population, the rule recognizes staffing and contract constraints in smaller towns, while still moving toward equal online access for all residents.
Keep reading: Retention Checklist for Minutes, Recordings, and Packets
What WCAG 2.1 Level AA asks of a minutes page
WCAG 2.1 Level AA is the technical benchmark for compliance. Many clerks have heard the phrase, but most have not worked directly with its checkpoints. For a meeting minutes page, the guidelines call for more than just readable text. They set specific standards for structure, navigation, color, and interaction.
Text and structure requirements
All text must be machine-readable, so screen readers can announce it. This means text must not be trapped in images or locked in scanned PDF files. The minutes page needs proper headings, clear lists, and logical order. Each agenda item or decision should be marked so a user can jump to it using keyboard navigation.
Contrast and color
Colors must provide enough contrast. For example, gray text on a white background will likely fail. Highlighted items, like votes or motions, cannot rely on color alone to convey meaning. If a "yes" vote is green and a "no" is red, both must also have a label or icon.
Links and attachments
All links to attachments, such as ordinances, maps, or contracts, must use descriptive text. "Download here" is not enough; the link should say what the document is. If minutes link to other web pages or documents, those destinations must also meet accessibility requirements.
Most importantly, the entire page must work with keyboard-only input. No part of the public record can require a mouse or touch screen to access, open, or understand.
Posted PDFs, scanned signatures, and the archived content exception
Minutes and supporting documents are often posted as PDFs. Some are digital from the start, but many are scanned from paper, especially older records. Scanned PDFs can present a major accessibility hurdle. Without optical character recognition, screen readers cannot interpret the text. Even with OCR, formatting and reading order can break down.
The new Title II rule does allow for an "archived content" exception, but it is narrow. To qualify, content must have been posted before March 2025 and must not have been modified since then. If an old minutes packet is updated, linked from a new agenda, or relied on for current business, it loses the exception and must become accessible.
Scanned signatures present another challenge. The rule does not require removing or altering signatures, but the text of the document must still be accessible. A scanned signature page attached to a machine-readable minutes document is acceptable, but a fully scanned minutes file is not.
For current and future postings, clerks will need to create or request accessible PDFs. This means using software or vendors that tag headings, lists, and tables for assistive technology. If posting a PDF, it should include real text, logical reading order, and alternative text for any images.
Keep reading: What It Costs to Publish One Council Meeting, Line by Line
Captioning meeting video and the audio only alternative
Many towns now stream or record meetings. Under WCAG 2.1 AA and the new web rule, video with audio must have accurate captions. Captions are not just for those who are deaf or hard of hearing, they help anyone in a noisy environment or using a mobile device.
Automatic captioning services are common, but most generate errors. The rule expects captions to be accurate enough for a listener to follow the discussion and decisions. Editing captions after the meeting is necessary. Minutes summaries can help by providing the correct names, motions, and results.
If a meeting is posted as audio only, a transcript must be available. This transcript should be time-synced or divided by agenda item if possible. The goal is for a person using a screen reader to follow along just as a hearing person would.
For towns without the budget for video, posting audio alongside an accessible minutes document is still compliant. The key requirement is that every action, vote, and discussion point is available in text for those who cannot hear or see the recording.
State laws on remote participation and quorum after 2020
The pandemic forced a rapid shift to remote and hybrid meetings. States responded with new statutes or executive orders, many of which have now been made permanent or extended. These laws govern when and how council members, boards, and the public can participate remotely.
Quorum and remote attendance
Some states now allow a full quorum to assemble through video or phone, while others require a physical majority in the meeting room. Many states permit remote participation for reasons of illness, disability, or travel, but may cap the number of remote meetings per year.
Hybrid meetings, where some members are in person and some remote, are increasingly common. Statutes may require technology that allows remote and in-person participants to hear and be heard clearly. Public comment periods must be accessible to those joining online by phone or video.
Notice and agenda posting
Remote participation has also changed notice and agenda rules. In most states, agendas must be posted online with clear instructions for remote access. Some require posting links to the video feed, call-in numbers, and accessibility accommodations in the same notice.
Recording and archiving requirements have expanded. When a meeting is held remotely or in hybrid format, the recording often becomes part of the official record. This brings new obligations for accessibility, retention, and public access.
See how GavelMinutes handles this for local government
Records requests arriving as searches instead of letters
Open records laws have always required local governments to provide access to minutes, agendas, and supporting documents. Traditionally, requests came in as written letters, emails, or forms. Increasingly, the public expects to find and search these materials online without having to ask.
ADA Title II and state laws now reinforce this expectation. If a resident with a disability cannot search for meeting decisions, download accessible minutes, or review past actions online, the website is likely out of compliance. Search tools must return results that are both accurate and accessible.
This changes how clerks prepare and publish minutes. Summaries of decisions, not just verbatim transcripts, are valuable for residents looking for a specific vote or motion. Linking agendas, minutes, and supporting documents improves transparency and reduces the burden of custom records requests.
Public search replaces many routine requests, but it also demands better organization. Files must be tagged, indexed, and described in language the public can understand. This benefits staff as well, making it easier to respond to more complex or historical records requests when they do arrive.
Budgeting remediation across an existing archive
For many local governments, the largest challenge lies not in future compliance but in the backlog. Years or decades of minutes and agendas may exist as scanned PDFs, untagged documents, or files missing key accessibility features. The new Title II rule does not require immediate remediation of all historical documents, but anything actively used or linked from a current web page must be brought up to standard.
Prioritizing content
Most clerks start by identifying which documents are viewed most often. Current year minutes, ordinances, and recent agendas take priority. If a document is routinely requested or referenced, it should be remediated first. Linking decision summaries and agendas to their supporting documents can also help prioritize what needs work.
Remediation methods
Remediation can be done in-house, with staff trained on PDF accessibility tools, or by contracting with vendors. The process involves tagging headings, enabling text reflow, fixing reading order, and adding alternative text to images. Handwritten or scanned documents may require retyping or advanced OCR services.
Budgeting for remediation is a challenge, especially for small towns. Some spread the work over several years, using annual funds to tackle a portion of the archive. Others focus on making all new documents accessible going forward, while remediating old records as public interest arises.
The process is ongoing. As technology changes and legal standards evolve, periodic reviews of the archive help ensure continued compliance. Staff training and clear policies can prevent future accessibility problems before they start.
More jurisdictions are turning to software that automates part of this process. Platforms that publish minutes in plain language, link agendas and supporting files, and make decisions searchable in an accessible format reduce manual workload and improve compliance. This approach streamlines public access while meeting federal and state requirements.
