01
Websites & web content
Pages, templates, navigation,
and published information.
ADA Title II
Digital access for public services.
Title II sets an accessibility standard for state and local government websites and mobile applications.
We help public teams identify barriers, prioritize fixes, and plan what to address first.
Technical accessibility services, not legal advice or compliance certification.
Who is affected and when
A shared standard,different timelines.
Title II applies to state and local government entities. The rule names WCAG 2.1 Level AA as the technical standard for covered web content and mobile applications.
Read current DOJ guidance50,000 or more people
0–49,999 people and special district governments
Scope depends on how many documents a site publishes, and that count is almost always larger than teams expect, which is why an inventory comes first rather than last.
Population and entity type determine the applicable compliance date.
What the rule reaches
Four surfaces, one obligation.
02
Forms & public workflows
Applications, payments,
registrations, and requests.
03
Documents & media
Agendas, minutes, policies,
notices, video, and audio.
04
Apps & vendor systems
Mobile applications, portals,
booking tools, and third-party platforms.
Overlays and widgets
A widget does notchange what is underneath.
Overlay products load on top of a page and adjust what a visitor sees. The page you publish, the files you attach, and the systems you buy stay as they were.
How automated checks and human judgment differWhat it does not reach
- Websites & web content
- Runtime changes apply in the visitor's browser. What you publish is unchanged.
- Documents & downloads
- An agenda or a scanned record downloads exactly as it was published.
- Forms & public workflows
- A permit application still has to be completable from start to finish.
- Apps & vendor systems
- A native app is not a web page, and a vendor's portal loads its own code.
Overlays sit on top. They do not repair the underlying website.
Content, vendors, and exceptions
Some contentrequires a closer look.
Older documents and archived content are not all treated the same way. Third-party contributions and vendor-managed systems can add another layer.
Current use, location, ownership, and relationship to a public service all matter. A file label or vendor name does not answer the question by itself.
Preparing your organization
A practical place to begin.
- 01
Assign ownership
Name the teams responsible for websites, content, procurement, and accessibility.
- 02
Build an inventory
List websites, applications, documents, public workflows, and vendor platforms.
- 03
Set priorities
Begin with essential and frequently used public services.
- 04
Make it repeatable
Carry accessibility into publishing, procurement, training, and maintenance.
See the DOJ's complete First Steps guidance
These are practical starting points; each public entity may require additional preparation.
Technical accessibility support
Understand what needs attention, and what to address first.
CK Works reviews an agreed portion of the public experience, confirms meaningful barriers, and turns the findings into practical next steps.
Explore the general accessibility service- 01Scope
Review an agreed scope
Representative pages, templates, documents, forms, public workflows, and vendor touchpoints are defined before the review begins.
- 02Impact
Organize confirmed barriers
Findings identify where a barrier occurs, how it affects access, whether it repeats elsewhere, and what should happen next.
- 03Next step
Support improvements and rechecking
CK Works can address issues within its control, provide guidance for other teams or vendors, and recheck completed changes when included in scope.
Technical accessibility support: not legal advice, compliance certification, or a guarantee that every barrier has been identified.
FAQ
Questions from public entities.
Common questions about who the rule covers, what a review includes, and where the boundaries are.
Public-entity accessibility
Start with a focused review.
Share the public services, pages, documents, or systems that matter most. We'll help define a practical technical review scope and determine the appropriate next step.