ADA Title II · 28 C.F.R. Part 35 · WCAG 2.1 Level AA

Federal accessibility, implemented where residents access, apply, and participate.

Public Layer brings municipal websites and official documents to WCAG 2.1 Level AA—and gives contracted service providers tested requirements to do the same. The work happens on the systems already in production.

Request an assessment Learn more

cityof——.gov

Screen reader

graphic
graphic
button, unlabeled
link, click here
image, IMG_4402.jpg
button, unlabeled

What assistive technology receives on a typical municipal homepage—and what it receives after implementation.

Scope

Where accessibility work happens.

Public Layer tests the paths residents use, then implements accessible structure, content, and documents in the systems already in production. Vendor-controlled services receive reproducible findings, implementation specifications, and acceptance criteria.

The digital estate

Public website

Templates, navigation, forms, search, and published content.

Official documents

Agendas, packets, applications, notices, and active records.

Contracted services

Permitting, meetings, records, resident applications, and payment services.

One technical standard

WCAG 2.1 Level AA

One accessibility program across every resident-facing system.

Representative platforms

Public Layer works within the systems already in place—not a prescribed technology stack.

CivicPlus
Granicus
Revize

Mandate

The DOJ set the standard. We implement it.

In 2024, the Department of Justice adopted WCAG 2.1 Level AA as the technical standard for state and local government web content and mobile applications. Public entities with a population of 50,000 or more must conform by April 26, 2027. Smaller entities and special districts must conform by April 26, 2028.

Population of 50,000 or more

Apr 26, 2027

Counties, larger cities, and many districts. The earlier compliance date.

Under 50,000 · special districts

Apr 26, 2028

The majority of towns. The same technical standard applies.

Source: U.S. Department of Justice Title II web and mobile accessibility rule; compliance dates extended by the interim final rule published April 20, 2026.

Process

A clear path from evidence to assurance.

Each engagement establishes what is failing, changes what residents use, and creates a practical way to hold the standard as systems and content change.

Three phases. One accountable record.

01
Assessment
Live inventory, manual testing, ranked findings, and a leadership brief.
02
Implementation
Templates, content, active documents, and vendor acceptance criteria.
03
Assurance
Inventory reviews, drift reporting, and publishing controls.

Ready for an assessment?

Start with evidence leadership can assign, track, and act on.

Request an assessment

Representative assessment excerpt

Leadership brief

Assessment · p. 1

Ranked findings

Active permit application is untagged
Vendor-controlled payment service blocks assistive technology
Current agenda packet has no text layer
Historic packet meets archive criteria

Each finding is tied to evidence, ownership, and acceptance criteria so leadership can decide what moves first.

Experience

Municipal experience, backed by professional credentials.

Public Layer's team brings hands-on municipal experience across public websites, official documents, staff publishing workflows, and resident-facing services.

We apply that context for cities, towns, counties, districts, and public authorities nationwide.

Client perspective

The work, in their words.

Draft review placement. Replace this copy and attribution with approved client language before publication.

“Public Layer gave us a clear view of the barriers residents were encountering—and a practical sequence our staff and vendors could act on.”

Client name

Title · Public entity

“The work moved accessibility from a list of findings to an accountable program with priorities, owners, and acceptance criteria.”