Pennsylvania towns, boroughs, townships and other local government entities now have specific federal accessibility requirements for their websites and mobile apps under Title II of the Americans with Disabilities Act. For municipal managers, IT departments, communications teams and elected officials, the most important point is simple: website accessibility now has a defined technical standard and a compliance deadline.
The U.S. Department of Justice (DOJ) requires covered state and local government web content and mobile applications to meet WCAG 2.1 Level AA. In April 2026, the DOJ extended the original compliance dates by one year. For detailed guidance, municipalities can review the DOJ's Title II web and mobile accessibility requirements.
For Pennsylvania municipalities, the current deadlines are:
- April 26, 2027 — public entities with a population of 50,000 or more
- April 26, 2028 — public entities with a population of less than 50,000
- April 26, 2028 — special district governments
These dates may sound distant, but municipalities with large websites, years of PDF documents, third-party portals and multiple departments should start evaluating accessibility well before the deadline.
What Does the ADA Title II Website Rule Actually Require?
Title II applies to state and local government services, programs and activities, including services delivered through websites and mobile applications. Under the rule, covered web content and mobile apps generally must conform to WCAG 2.1 Level AA.
WCAG—the Web Content Accessibility Guidelines—addresses barriers that can prevent people with disabilities from using digital services effectively. For a municipal website, accessibility can affect navigation using only a keyboard, text and background color contrast, alternative text for meaningful images, proper heading structure, accessible online forms, form labels and error messages, links and buttons that screen readers can identify, captions for video content, accessible PDFs and other documents, mobile usability and zoom, and public payment, permitting and reservation systems.
Municipalities that want an initial picture of common technical issues can start with OST's free WCAG Accessibility Checker, which can scan public pages against WCAG standards. Automated testing, however, should be considered a starting point rather than a complete accessibility audit.
Which Deadline Applies to Your Pennsylvania Municipality?
DOJ generally bases the deadline on the public entity's population. If the entity has a population in the 2020 decennial Census, DOJ says to use that population when determining which compliance date applies. The number of government employees or the number of residents who use a particular department does not determine the deadline.
For example, a Pennsylvania township with a 2020 Census population of 60,000 would generally fall under the April 26, 2027 deadline, while a borough with a population of 15,000 would generally fall under the April 26, 2028 deadline. Special district governments also have until April 26, 2028. DOJ defines these separately from counties, municipalities and townships.
Municipalities near the 50,000 threshold should verify their classification and applicable population rather than relying on current estimates or website traffic.
What Should a Municipality Check First?
The first step should not be redesigning the website. It should be understanding what the municipality actually has online. DOJ recommends identifying the full range of web content and mobile applications a public entity provides.
A practical inventory should include public webpages such as department pages, ordinances, meeting information, public notices, police information, recreation programs and service pages; online forms such as permit applications, public records requests, employment forms, registrations, complaints and contact forms; documents such as PDFs, Word files, spreadsheets, council agendas, meeting minutes, budgets, reports and applications; third-party services such as payment systems, permitting portals, calendars, reservation tools and mapping applications; and any mobile applications the municipality provides directly or through a vendor.
Social media should also be considered, particularly content published after the municipality's applicable compliance date. Once the inventory is complete, municipalities can identify which areas present the greatest accessibility risk and which require manual testing.
Do Old PDFs Have to Be Made Accessible?
This is one of the most important questions for local governments because municipal websites may contain years of meeting minutes, agendas, reports and scanned records. The rule includes a limited exception for certain preexisting conventional electronic documents, including PDFs, Word documents, presentations and spreadsheets.
Generally, a preexisting document may fall within the exception if it was available before the municipality's compliance date and is not currently used to apply for, access or participate in a government service, program or activity.
That distinction matters. An old flyer for an event that ended years ago may qualify for an exception. A PDF application that residents still use to obtain a business license probably does not. Municipalities therefore should not assume that every PDF posted before 2027 or 2028 can simply remain inaccessible.
Your Website Vendor Does Not Remove the Municipality's Responsibility
Outsourcing the website does not outsource Title II responsibility. DOJ specifically states that when a public entity uses a contractor, vendor or other third party to provide web content or mobile applications on its behalf, the public entity still must make sure those services satisfy applicable Title II accessibility requirements.
This is especially relevant for Pennsylvania municipalities using outside vendors for website development, website maintenance, online payments, recreation registration, permit applications, meeting management, public records systems or mobile applications. Now is a good time to review vendor contracts, accessibility requirements and procurement language.
OST's Pennsylvania web development and public-sector procurement experience includes WCAG and Section 508 requirements as part of government-focused web engagements.
Automated Scanning Alone Is Not Enough
An automated accessibility checker can identify many technical problems quickly, but DOJ explicitly cautions that automated testing tools cannot evaluate every aspect of accessibility. Public entities should use a combination of automated and manual assessment.
Manual review is especially important for questions such as whether alternative text actually describes an image meaningfully, whether every function can be completed with a keyboard, whether a screen reader announces content in a sensible order, whether form instructions are understandable, whether error messages help users recover, whether menus and interactive controls are predictable, and whether PDFs are logically structured for assistive technology.
OST's accessibility approach includes automated and manual testing, keyboard navigation, screen reader support, semantic markup, form accessibility and visual accessibility checks.
What Should Pennsylvania Municipalities Prioritize?
DOJ recommends prioritizing content that supports important and frequently used government activities.
A reasonable order for many municipalities would be:
- Online payments, permits and applications
- Public forms and service requests
- Main navigation and search
- Current council or board materials
- Public notices and emergency information
- Frequently used department pages
- Third-party platforms
- Current PDFs and downloadable forms
- Mobile applications
- Less frequently accessed historical material
Municipalities should also stop creating new accessibility problems while older issues are being remediated. New pages, documents, forms and vendor purchases should be reviewed for accessibility from the beginning.
The Deadline Is Not the Finish Line
Compliance is not a one-time website project. After the applicable deadline, municipalities must continue maintaining accessible web content and mobile applications.
That means local governments need an ongoing process for staff training, accessible document creation, content publishing, vendor procurement, website updates, accessibility testing, responding to accessibility complaints and periodic regression testing.
For municipalities planning a redesign or major modernization, building accessibility into the project from the beginning is generally more practical than attempting to remediate an inaccessible platform immediately before the deadline. OST's custom web development process includes accessibility requirements within the baseline development approach.
What Pennsylvania Municipalities Should Do Now
The most useful first step is simple: find out where your website stands today. Confirm your deadline, inventory your websites, PDFs, forms, mobile apps and third-party tools, run an initial automated scan, and then conduct manual testing of the services residents rely on most.
For municipalities over 50,000 people, April 26, 2027 is now close enough that accessibility planning should already be underway. Smaller Pennsylvania towns, boroughs and townships have until April 26, 2028, but large document libraries or older websites can require substantial remediation work.
Accessibility is ultimately about more than passing a technical test. Municipal websites increasingly serve as the front door to government services. Residents should be able to use that front door independently, whether they access it with a mouse, keyboard, screen reader, voice technology or another assistive tool.
Starting early gives Pennsylvania municipalities time to identify problems, prioritize essential services, work with vendors and make accessibility part of normal digital operations rather than a last-minute compliance project.


