Accessibility Hub: ADA Title II (United States)

Digital accessibility for state and local government websites, mobile apps, and online services

ADA Title II at a glance

The Americans with Disabilities Act (ADA) Title II is a U.S. civil-rights law that requires state and local governments (“public entities”) to provide people with disabilities equal access to their programs, services, and activities—including those delivered through websites, mobile apps, online forms, portals, and digital documents.

In 2024, the U.S. Department of Justice (DOJ) finalized a rule that makes Title II digital accessibility expectations more specific by requiring covered web and mobile content to conform to WCAG 2.1 Level AA (including Level A and AA success criteria and conformance requirements).

Key takeaways (practical view):

Public entities must make web content and mobile apps accessible, including content provided “through contractual, licensing, or other arrangements” (e.g., third-party platforms used to deliver services).
WCAG 2.1 Level AA is the referenced technical standard for Title II web and mobile accessibility requirements.
Deadlines depend on population size, with later dates for smaller entities and special district governments.
Accessibility is ongoing—updates to content, new features, and vendor changes can introduce new barriers over time.

Note: This content is provided for general information only and does not constitute legal advice. If you need a formal interpretation of requirements for your organization, consult qualified legal counsel and your compliance team.

When ADA Title II applies (digital context)

Who Title II covers

Title II applies to public entities, which includes:

Any state or local government
Any department, agency, or instrumentality of state/local government (including special purpose districts)

In practice, this often includes (examples): public education, courts, voting, emergency services, transportation, parks and recreation, social services, licensing, and other government services offered to the public.

What digital content is included

Under DOJ’s Title II web and mobile accessibility requirements, public entities must ensure accessibility for:

Web content they provide or make available

Mobile apps they provide or make available

Including content delivered directly or through third parties (contractual/licensing arrangements)

If a digital channel is how people access a service—apply, register, pay, book, request support, submit forms, download required documents—it should be treated as in-scope.

Scope note (what’s included and what’s not)

Included: public-facing websites, web applications and portals, online forms, posted documents (including PDFs), embedded media, and third-party tools used to deliver services (for example, payment, scheduling, or identity solutions) when provided or made available by the public entity directly or through contractual/licensing arrangements.

Not just “marketing pages”: if people must use a digital channel to access or complete a government service (apply, register, pay, request support), that workflow should be treated as in-scope.

Practical reminder: scanned/untagged PDFs and image-based postings are common sources of accessibility barriers and often require remediation or replacement with accessible formats.

ADA Title II digital accessibility requirements (practical view)

Target standard (what teams build to)

The DOJ rule requires conformance with WCAG 2.1 Level A and Level AA success criteria and conformance requirements for covered web and mobile experiences (i.e., a WCAG 2.1 AA baseline).

Practical recommendation: Even if your organization’s internal policy still references older WCAG versions, aligning delivery practices to WCAG 2.1 AA or 2.2 AA is typically the most defensible and forward-compatible baseline for modern public digital services.

Compliance dates (timelines)

Under the updated DOJ compliance dates:

Beginning April 26, 2027: public entities (other than special district governments) serving a total population of 50,000 or more
Beginning April 26, 2028: public entities serving a total population of less than 50,000 and any special district government

Limited defenses (not “free passes”)

The rule allows limited exceptions where a public entity can demonstrate that compliance would result in:

A fundamental alteration in the nature of a service, program, or activity; or
Undue financial and administrative burdens

Even where an exception is claimed, organizations should expect to still provide accessible access to the service/program in practice (e.g., an alternate way to obtain the same information or complete the same task).

Proof & documentation (what to keep on file)

Assessment evidence: what was tested (sites/apps/documents), sampling approach, tools used, and issue logs mapped to WCAG 2.1 AA.
Remediation tracking: a prioritized backlog/roadmap, owners, timelines, and completion evidence (before/after notes or verification results).
Testing records: results from manual keyboard testing and assistive technology testing (for example, screen readers), plus regression checks for major releases.
Third-party assurance: vendor accessibility commitments and acceptance test results for any externally provided web/app capability used to deliver services.

Procurement & vendor management (third-party services)

Set accessibility requirements up front: require WCAG 2.1 AA conformance for any product/service that will be used to provide or support public services online.
Validate before go-live: include accessibility acceptance criteria in implementation and QA so issues are found before launch.
Contract for accountability: define responsibilities for remediation timelines when accessibility defects are found (including during upgrades or platform changes).
Monitor changes: vendor updates can introduce regressions—build accessibility checks into release management and renewal cycles.

What’s commonly in scope (where risk shows up)

Across state and local government digital services, the highest-risk areas commonly include:

Common WCAG issues (examples):

Missing or incorrect text alternatives for images and icons (alt text).

Incomplete keyboard access and/or a non-visible focus indicator.

Missing form labels, unclear instructions, or inaccessible validation messages.

Poor error identification and recovery (users can’t tell what went wrong or how to fix it).

Insufficient color contrast or relying on color alone to convey meaning.

Missing captions for video and weak structure (headings/reading order) in pages and documents.

Online forms and applications (missing labels, confusing instructions, inaccessible errors, keyboard traps)

PDFs and posted documents (unstructured, untagged, or scanned content that assistive tech cannot reliably read)

Portals and transactional workflows (sign-in, account management, payments, scheduling/booking)

Media and embedded content (videos without captions, inaccessible players, images without text alternatives)

Third-party tools used to deliver services (identity providers, payment vendors, embedded forms, chat, scheduling tools) that still affect end-to-end accessibility

What you may need to do (operational steps)

A practical way to approach Title II digital accessibility is to treat it as both a technical conformance and a delivery lifecycle:

Define scope and priority journeys

Identify the pages and workflows people rely on most to access services (applications, benefits, licensing, payments, support, emergency information).
Assess against WCAG 2.1 AA

Evaluate key templates and end-to-end journeys (including PDFs and forms), then document issues, severity, and remediation recommendations.
Remediate high-impact barriers first

Prioritize issues that block task completion (navigation, labels/instructions, error identification, keyboard access, document structure).
Put governance in place to prevent regression

Accessibility can degrade quickly when content teams publish new PDFs, vendors change UI components, or new workflows launch without checks.

How 4Point can help

If you’re a public entity (or a vendor delivering services to public entities) and need to align digital experiences to Title II expectations, 4Point can help you.

Start with an accessibility audit. 4Point can run a practical audit to establish a baseline, identify the highest-risk barriers, and give you a prioritized remediation roadmap.

Scoping session: confirm which forms are in scope, the number to be reviewed, and the accessibility standard(s) to assess against.
Forms accessibility audit: review an agreed number of forms and document accessibility gaps.
Conformance report and prioritization: provide conformance findings, severity ratings, and a recommended fix order.
Recommendations and remediation plan: share recommendations for addressing identified gaps and provide a statement of work for remediation of the audited forms (remediation is not included in the audit engagement).

Contact 4Point: Request an accessibility audit

Anchor 2