Skip to main content
Published · 2026-07-16

Accessibility verification and compliance readiness for Title II.

Independent audits and remediation for government and business — scoped to your compliance deadline, defensible under audit.

Book a Readiness CallDownload capability statement
Two accessibility specialists reviewing an audit dashboard together.

A Trusted Tester–certified practice, testing to WCAG 2.1 AA and Section 508 standards, with 10 years of accessibility compliance work across federal, state, and local government.

TRACE-002STATUS: VERIFIEDAI-assisted Human-verified.
Regulatory map · ADA Title II compliance deadlines

When does this apply to your entity?

Compliance dates differ by population served — find your entity's date below.

  1. Due in ~7 months
    50,000+ residents

    Larger public entities

    April 26, 2027
  2. Due in ~19 months
    Under 50,000 residents

    Smaller entities · Special districts

    April 26, 2028
01Overview · What follows
Scale → Engagement → Reality → Services → Methodology
Engagement Model · 6 phases

How a Title II readiness engagement runs.

  1. 1

    Scope

    Inventory digital assets. Prioritize critical paths.

  2. 2

    Test

    Automated + native screen-reader behavioral evidence.

  3. 3

    Prioritize

    Risk-based roadmap for legal and procurement.

  4. 4

    Remediate

    Execution support for code and document repair.

  5. 5

    Verify

    Independent re-test confirming WCAG 2.1 AA.

  6. 6

    Govern

    Policy and procurement integration for the long term.

Deadline Reality

The deadline is not optional, and the backlog is bigger than it looks.

Most public entities are sitting on backlogs of public-facing PDFs that often run into the thousands, plus web content and mobile apps that were never audited against WCAG 2.1 AA. The runway to April 2027 is shorter than it reads on the calendar.

Last reviewed: 2026-07-16 · Informational, not legal advice.
Source: ADA.gov / DOJ (per brief §6A)
Standard
AA

WCAG 2.1 · mandatory baseline for all digital assets.

Runway
9 mo

From today to the Phase 1 deadline of April 26, 2027.

Coverage
Web · App · PDF

Third-party content and vendor platforms included.

Evidence
Behavioral

Native screen-reader verification, not scanner-only.

Services · 4 primary + 2 Phase 2

Six services scoped for public-sector accessibility work.

All services →
TRACE-11STATUS: ACTIVE
S-01

Title II Readiness Sprint

Turn the DOJ rule into a real operating plan. 4-week baseline plus prioritized backlog.

TRACE-12STATUS: PENDING
S-02

Section 508 / WCAG Website & App Audits

Manual, standards-based audits with behavioral evidence — not just automated scans.

TRACE-13STATUS: VERIFIED
S-03

PDF & Document Remediation

Backlog triage and remediation. PDF/UA-1 aligned before publication.

TRACE-14STATUS: VERIFIED
S-04

Post-Remediation Verification

Independent proof the change reached assistive technology, not just the code.

Phase 2 — Upcoming
Phase 2
TRACE-21STATUS: PENDING
S-05

Governance & Operations

Policy, procurement intake, and accessibility runbooks so compliance holds after launch.

Phase 2
TRACE-22STATUS: PENDING
S-06

User Validation

Recruitment, consent, and AT coverage with real users. Compensation and privacy handled.

Methodology Preview

Behavioral Verification.

We tell you what's exposed to assistive technology — not just what's inside the document. Static analysis and automated scanners are valuable first steps; behavioral verification covers what they are not designed to detect.

Tags
  • H1
    Heading
  • P
    Text
  • BUTTON
    no name
  • IMG
    no alt
  • DIV
    ignored
Discrepancy zone
Exposed to the screen reader
Two-layer diagram contrasting a document's tag structure with what a screen reader actually exposes. The top layer shows document tags (H1, P, BUTTON, IMG, DIV). The bottom layer shows the assistive technology accessibility tree (Heading, Text, — no name —, Image without alt, and an ignored group). A shaded band between the two layers marks the discrepancy — the gap where behavioral verification lives.
Excerpt from a verification finding record — F-2027-0142CONFIRMED
NVDAFirefoxWin 11
element
button#submit-form
issue
accessible name absent
wcag
2.1 · 4.1.2 Name, Role, Value (A)
scanner
axe: pass · lighthouse: pass
behavior
NVDA announces "button" — no name reaches AT
evidence
screen-reader-log/f-2027-0142.txt
status
confirmed · defensible
Operations · Capability Statement

The infrastructure behind the audits.

Methodology
Evidence-backed

Traceable, reproducible findings with scoped non-conclusions.

Client Upload
Coming soon

A secure document intake channel for regulated materials. Not yet open — send nothing there today.

Government-ready
Procurement-fluent

Capability Statement and standard contract vehicles.

Book a Readiness Call

Get a defensible Title II readiness roadmap.

No silent passes. No hidden uncertainty. A scoped read of what's exposed today and what has to change before April 2027.

Book a Readiness CallDownload Capability Statement