Public entities serving 50,000 or more
The effective date is close enough that inventory, remediation, document work, vendor coordination and retesting should be treated as an active project, not a final-quarter task.
Title II web accessibility
The federal standard is set. The work needs a record.
State and local government websites and mobile apps are subject to a DOJ technical standard: WCAG 2.1 Level AA. ADAReadyWeb assesses against WCAG 2.2 Level AA and produces a scoped, dated record of what was tested, what was found, what changed, and what was retested.
Call 302-688-0233
Deaf, hard of hearing and speech-disabled callers can reach this number through 711 relay.
01 / Who must comply
Two dates. One technical standard.
The Title II rule applies to state and local governments, including cities, counties, public school districts, public universities, transit authorities, library authorities and special district governments. The rule names WCAG 2.1 Level AA as the technical standard for covered web content and mobile apps.
Fewer than 50,000 + special districts
The additional year does not reduce the scope. Large document archives and decentralized publishing workflows can require substantial lead time.
02 / What you receive
An audit package, not a score.
The record is designed to be usable by counsel, procurement, IT and the people doing the remediation. It identifies the scope, the standard, the evidence and the status of each finding.
Documented scope
Which properties, templates and page types were tested, and which were not.
Standard and date
The WCAG version and conformance level assessed, with the assessment date.
Methodology
The automated tools and manual test methods used during the engagement.
Criterion-mapped findings
Each finding tied to a specific WCAG success criterion and observable condition.
Remediation log
A working record that tracks each finding through correction and closure.
Retest evidence
Post-remediation testing that records whether the original finding was resolved.
Accessibility statement
A public statement the entity can publish and maintain as its accessibility program evolves.
Monitoring plan
A practical cadence for checking new releases and content because conformance can decay after launch.
-
Signature block
Assessments are signed /s/ David S. Neal, Managing Partner, Knowledge Transfer LLC.
03 / How we test
Automated scanning finds patterns. Manual testing finds behavior.
Automated tools are useful, but they do not determine conformance by themselves. Every engagement combines machine-detectable checks with human testing of interaction, structure, content and assistive-technology behavior.
Assessment standard: WCAG 2.2 Level AA.
W3C describes WCAG 2.2 as backwards compatible with WCAG 2.1: content that conforms to WCAG 2.2 also conforms to WCAG 2.1. WCAG 2.2 adds newer success criteria while the Title II regulatory baseline remains WCAG 2.1 Level AA.
01
Keyboard-only operation
Navigation, menus, dialogs, controls, focus visibility and focus order without a pointing device.
02
Screen reader passes
Names, roles, states, reading order, announcements, relationships and control behavior.
03
Contrast measurement
Text, user-interface components, focus indicators and meaningful non-text graphics.
04
Headings and landmarks
Document hierarchy, regions, bypass mechanisms and programmatic page structure.
05
Forms and errors
Labels, instructions, required states, validation, error identification and correction.
06
Media and focus management
Captions, transcripts, playback controls, dynamic updates and focus movement after interface changes.
04 / Web content means more than pages
Documents and video are in scope.
PDFs, office documents, recorded video and other content delivered through the website are part of the accessibility review. They are not treated as an afterthought.
For many public entities, board minutes, budgets, agendas, forms and meeting packets create the largest remediation workload because years of documents accumulate outside the main site templates.
PDFs and office documentsStructure + reading order
Board minutes and agendasRecurring content
Budgets and reportsTables + tagged data
Recorded videoCaptions + transcripts
Forms and applicationsLabels + error handling
05 / How findings are reported
Conformance language procurement teams recognize.
Findings use ACR/VPAT-style response vocabulary: Supports, Partially Supports, Does Not Support and Not Applicable. The status never stands alone; it is tied to a named success criterion and supporting evidence.
| WCAG success criterion | Finding | Conformance response | Evidence note |
|---|---|---|---|
| 1.1.1 Non-text Content | Informative image has an equivalent text alternative. | Supports | Accessible name communicates the same purpose. |
| 1.4.3 Contrast (Minimum) | Most text passes; one secondary control does not. | Partially Supports | Measured ratio is recorded with the affected selector. |
| 2.1.1 Keyboard | Menu action cannot be completed from the keyboard. | Does Not Support | Reproduction steps identify the blocked interaction. |
| 1.2.4 Captions (Live) | No live synchronized media exists within the assessed scope. | Not Applicable | Scope record documents why the criterion is not applicable. |
This example shows reporting structure only. Actual findings are based on the tested property, documented scope and evidence collected during the engagement.
06 / Secondary practice area
For private businesses
Title III of the ADA applies to covered private businesses and places of public accommodation. Unlike the Title II web rule, DOJ has not adopted a generally applicable regulation that names a specific website technical standard for private businesses.
WCAG is nevertheless the technical benchmark commonly used in accessibility programs, litigation, consent decrees and settlement agreements. A private-business engagement is framed as a scoped WCAG conformance assessment, not as compliance with a nonexistent DOJ web deadline.
07 / Who performs the assessment
Knowledge Transfer LLC
Assessments are performed by Knowledge Transfer LLC through the ADAReadyWeb platform. The deliverable identifies the tested scope, standard, date, methodology, findings, remediation status and retest evidence.
There is no badge or blanket certification. The record says what was actually assessed.
/s/ David S. Neal
David S. Neal
Managing Partner
Knowledge Transfer LLC
08 / FAQ
Direct answers.
The engagement begins by defining what is in scope. The rest follows from that boundary.
Can you certify us as ADA compliant?
No. There is no government-issued website certification that converts an entire organization into a permanently compliant state. What we provide is a defensible, scoped and dated conformance record: what was assessed, against which standard, how it was tested, what was found, what was remediated and what was retested.
What does an engagement cost?
Cost depends on scope: number of properties, templates, application states, documents, media and remediation cycles. Every engagement begins with a scoping call so the work can be defined before a proposal is prepared. Call 302-688-0233.
Do automated scanners cover the assessment?
No. Automated scanning is one input. Manual keyboard testing, screen reader testing, contrast measurement, structural review, form testing, media review and focus-management testing are part of the assessment because many accessibility failures depend on context and behavior.
Why assess against WCAG 2.2 if Title II names WCAG 2.1?
WCAG 2.2 is designed to be backwards compatible with WCAG 2.1. W3C states that content conforming to WCAG 2.2 also conforms to WCAG 2.1. WCAG 2.2 adds newer criteria, while the Title II regulatory baseline remains WCAG 2.1 Level AA.
What happens after remediation?
The affected findings are retested. The remediation log records closure status and the final package preserves the post-remediation evidence. Ongoing monitoring is then scoped around the entity’s release and publishing cadence.
ADAReadyWeb accessibility statement
This site is built to be usable without a mouse and with assistive technology.
ADAReadyWeb maintains this site against WCAG 2.2 Level AA. If you encounter an accessibility barrier on this site, call 302-688-0233. Deaf, hard of hearing and speech-disabled callers can reach that number through 711 relay. We will use the report to investigate and correct the issue.