PageAudit
Back to blog

The April 2027 Government Website Accessibility Deadline: What Small Municipalities Need to Do Now

·PageAuditors Team

The April 2027 Government Website Accessibility Deadline: What Small Municipalities Need to Do Now

April 26, 2027 is just over 14 months away. That is the federal deadline for all state and local government entities serving populations under 50,000 to make their websites conform to WCAG 2.1 Level AA.

Fourteen months sounds like plenty of time. It is not.

Municipal budget cycles run 12 months. Procurement for web accessibility services can take 3-6 months. Remediation of a typical municipal website takes 2-6 months depending on size and complexity. If your municipality has not started the process, you are already behind the timeline that leads to on-time compliance.

The DOJ's Final Rule under ADA Title II is not a suggestion. It is a federal mandate. Settlements for noncompliance routinely exceed $100,000, and they come with years of monitoring requirements and public consent decrees. The cost of compliance is a fraction of the cost of enforcement.

Here is exactly what your municipality needs to do, starting now.

What the DOJ's Final Rule Means for Small Municipalities

In April 2024, the Department of Justice published its Final Rule under Title II of the Americans with Disabilities Act. The rule establishes WCAG 2.1 Level AA as the enforceable accessibility standard for all web content and mobile applications published by state and local government entities.

The rule created two deadline tiers:

PopulationDeadline
50,000 or moreApril 24, 2026 (already past for many)
Under 50,000April 26, 2027

"Under 50,000" covers the vast majority of municipalities in the United States. According to the Census Bureau, over 89% of incorporated places in the U.S. have populations under 50,000. This rule affects nearly every city, town, village, borough, and county in the country.

The rule applies to all web content your municipality publishes or maintains, including:

  • Your official website (every page, not just the homepage)
  • Online forms (permit applications, utility payments, public records requests)
  • Published documents (meeting agendas, budgets, ordinances, public notices)
  • Embedded media (recorded meetings, informational videos)
  • Third-party tools integrated into your site (payment processors, scheduling widgets, mapping tools)

Why April 2027 Is Closer Than You Think

Municipal government does not move at the speed of a startup. Here is the realistic timeline for achieving compliance:

Budget Approval: 1-3 Months

Most municipalities operate on an annual budget cycle. If accessibility remediation is not already in your current budget, you need to get it into the next one. That means preparing a budget request, presenting it to council or the board, and waiting for approval. Depending on your fiscal year, this alone could consume 1-3 months.

Vendor Procurement: 2-4 Months

If your municipality follows public procurement rules (most do for contracts above a threshold), you need to issue an RFP, evaluate responses, select a vendor, and execute a contract. Even informal procurement takes time. Government procurement for web services typically takes 2-4 months from RFP to signed contract.

Initial Audit: 2-4 Weeks

Before any remediation begins, you need a comprehensive audit of your current website. This includes automated scanning (which takes minutes) and manual testing of complex interactions (which takes days to weeks depending on site size).

Remediation: 2-6 Months

This is the actual work of fixing accessibility issues. The timeline depends on:

  • Site size: A 50-page municipal website is very different from a 500-page site with multiple departments
  • Complexity: Simple content fixes (alt text, heading structure) are fast; complex fixes (form redesigns, third-party widget replacements) take longer
  • PDF volume: Many municipalities have hundreds or thousands of PDF documents that need to be made accessible or converted to HTML
  • Third-party dependencies: If a critical tool (payment processor, GIS map, meeting management system) is inaccessible, you may need to migrate to a new vendor

Testing and Verification: 2-4 Weeks

After remediation, you need to verify that the fixes work and have not introduced new issues. This requires another round of automated and manual testing.

Total Realistic Timeline: 6-14 Months

Add these up and you get 6-14 months for a typical small municipality. With just over 14 months until the deadline, municipalities that have not started are at serious risk of noncompliance.

What WCAG 2.1 AA Looks Like for a Municipal Website

WCAG 2.1 Level AA is a technical standard with 50 success criteria. For a typical municipal website, here is what compliance looks like in practical terms:

Every Page

  • All images have descriptive alt text (or are marked as decorative)
  • Text meets minimum contrast ratios (4.5:1 for body text, 3:1 for large text)
  • Headings are in logical order (h1, h2, h3 -- no skipping levels)
  • The page has a descriptive title tag
  • The HTML lang attribute is set correctly
  • All interactive elements work with a keyboard (tab, enter, escape)
  • Focus indicators are visible when tabbing through the page

Forms (Permit Applications, Utility Payments, Public Records Requests)

  • Every form field has a visible label associated with it
  • Required fields are clearly indicated (not just by color)
  • Error messages are specific and appear near the relevant field
  • The form can be completed entirely with a keyboard
  • Timeout warnings allow users to extend their session

Documents (Meeting Agendas, Budgets, Ordinances)

  • PDF documents have proper tag structure (headings, lists, tables)
  • PDF documents have a logical reading order
  • Images in PDFs have alt text
  • Tables in PDFs have proper header cells
  • Scanned documents (image-only PDFs) are converted to searchable text with proper structure

Video and Audio (Council Meetings, Public Hearings)

  • All videos have synchronized captions
  • Captions are accurate (not just auto-generated without review)
  • Audio-only content has transcripts
  • Media players have accessible controls (keyboard-operable, labeled buttons)

Interactive Elements (Maps, Calendars, Widgets)

  • Embedded maps have text alternatives describing the information the map conveys
  • Calendar widgets are keyboard accessible
  • Third-party widgets meet the same WCAG 2.1 AA standard as your own content

The 5 Most Common Accessibility Failures on Government Websites

Based on automated scans of thousands of government websites, these are the issues that appear most frequently:

1. Inaccessible PDF Documents

This is the single biggest challenge for most municipalities. Years of meeting agendas, budgets, ordinances, and public notices are published as PDFs -- many of them scanned images with no text layer, no heading structure, and no alt text. The DOJ's rule includes a limited exception for preexisting documents that are not modified, but this exception disappears the moment someone requests an accessible version or you update the document.

Fix priority: High. Start by making all new documents accessible going forward. Then work backward through existing documents, prioritizing those that are most frequently accessed or legally required.

2. Missing Alt Text on Images

Photos of town events, staff headshots, building images, maps, and infographics published without alt text are invisible to screen reader users. This is one of the most common violations cited in DOJ enforcement actions.

Fix priority: High. This is also one of the easiest fixes. Audit all images and add descriptive alt text. For decorative images, add empty alt attributes (alt="").

3. Form Accessibility Issues

Online permit applications, utility payment forms, and public records request forms frequently lack proper labels, have poor error handling, and are not keyboard accessible. If a resident cannot complete a government form, that is a direct denial of a government service.

Fix priority: Critical. Forms that handle essential government services (payments, applications, requests) must be fully accessible.

4. Video Without Captions

Recorded city council meetings, public hearings, and informational videos are published without captions. Auto-generated captions from platforms like YouTube are a starting point but are not sufficient -- they contain errors that must be reviewed and corrected.

Fix priority: Medium-High. Start captioning all new video content immediately. For existing recordings, prioritize those that are still actively referenced (recent meetings, current informational videos).

5. Poor Color Contrast and Heading Structure

Many municipal websites use light gray text, low-contrast link colors, or heading tags chosen for visual appearance rather than document structure. These issues affect users with low vision and users who navigate by heading structure.

Fix priority: Medium. These are typically CSS-level fixes that can be applied site-wide relatively quickly.

Recommended 12-Month Action Plan

Month 1-2: Assess and Budget

  • Run an automated accessibility scan of your entire website to establish a baseline
  • Inventory your content: How many pages? How many PDFs? How many embedded videos?
  • Identify third-party tools and check their accessibility compliance (or contact vendors)
  • Prepare a budget request for remediation work, including staff time, vendor costs, and tool subscriptions
  • Brief your council/board on the DOJ requirement and the deadline

Month 3-4: Procure and Plan

  • Issue an RFP for accessibility remediation services (if using an outside vendor)
  • Establish an accessibility policy for all new content published to the website
  • Train content editors on basic accessibility: alt text, heading structure, accessible documents
  • Begin making all new PDFs accessible using your word processor's built-in accessibility tools

Month 5-8: Remediate

  • Fix site-wide issues first: contrast, heading structure, navigation, skip links, keyboard access
  • Remediate forms for all essential government services
  • Address PDF documents, prioritizing those most frequently accessed and legally required
  • Add captions to videos, starting with current content and working backward
  • Replace or reconfigure any third-party tools that do not meet WCAG 2.1 AA

Month 9-10: Test and Verify

  • Run another automated scan to measure progress and catch regressions
  • Conduct manual testing with keyboard navigation and screen readers
  • Test with real users who use assistive technology (local disability organizations can often help)
  • Fix remaining issues identified during testing

Month 11-12: Document and Maintain

  • Publish an accessibility statement on your website with contact information for feedback
  • Establish a monitoring schedule (monthly automated scans, quarterly manual reviews)
  • Document your compliance efforts -- if the DOJ ever investigates, a clear record of proactive effort demonstrates good faith
  • Set up a process for handling accessibility feedback from residents

Budget Considerations

Free and Low-Cost Options

  • Automated scanning -- tools like PageAuditors offer free initial scans that identify the most common and legally significant issues
  • Content fixes -- alt text, heading structure, and contrast fixes can be done by existing staff with basic training
  • Document accessibility -- Microsoft Word and Google Docs have built-in accessibility checkers; train staff to use them before converting to PDF
  • Caption tools -- YouTube's auto-captioning provides a starting draft that staff can edit

Costs You Should Budget For

  • Comprehensive manual audit: $3,000-$10,000 depending on site size
  • Remediation services (if outsourced): $5,000-$25,000 for a typical municipal website
  • PDF remediation (if you have hundreds of documents): $50-$200 per short document (5-20 pages); longer documents cost more
  • Ongoing monitoring tools: $20-$100/month for automated scanning
  • Staff training: $500-$2,000 for team accessibility training

Compare these numbers to the $100,000+ cost of a DOJ settlement plus years of mandatory monitoring, and the investment case is clear.

Do Not Wait for the Deadline

The municipalities that will be in the strongest position on April 26, 2027 are the ones that start today. Every month of delay compresses the remaining timeline and increases the risk of missing the deadline.

A DOJ investigation does not wait for your budget cycle. A resident complaint does not wait for your procurement process. And the DOJ has signaled clearly that it intends to enforce this rule.

Start with a scan. Understand where you stand. Then build a plan to get where you need to be.

Start your free government website scan at PageAuditors