Get ready for ADA Title II digital accessibility requirements.

Title2Ready helps organizations identify, triage, and remediate digital assets (primarily documents - PDFs, DOCX, PPT, etc.) to align with WCAG 2.1 Level AA technical standards. We’re currently working closely with universities and colleges, and plan to expand to state and local organizations and others affected by ADA digital compliance expectations.
WCAG 2.1 AA technical standard alignment Practical remediation workflows Designed for higher ed first Expandable to public sector

 

Three Dimensions of ADA Title II Readiness

Title2Ready views ADA Title II compliance as an ongoing governance function, not a one-time remediation sprint. Our solution is designed to help public entities organize, execute, and defend accessibility readiness as a repeatable program.

1. Risk Management

Governance, oversight, and defensible audit posture

ADA Title II is an accountability regime. In practice, that accountability shows up through audits and, potentially, lawsuits, both of which center on two questions: whether the organization is meeting accessibility requirements and whether it can demonstrate sustained, good-faith “best effort” activity over time.

Title2Ready supports that reality by establishing a centralized program structure: compliance monitoring and measuring, coordination of remediation activities through common workflows, visibility into digital asset status across teams, and persistent audit trails that document activity, decisions, and progress.

This transforms accessibility remediation from fragmented, silo’d efforts into a structured, organization-wide program that improves readiness before key deadlines and enables ongoing sustainment afterward.

2. Remediation Management

Operational workflow and structured execution

At the execution level, Title2Ready bridges the gaps between subject matter expertise (for example, faculty who know the course content) and the technical requirements needed to make digital assets conformant. It does this through a guided, interactive interview workflow that translates easy-to-answer questions into structured remediation requirements, scope definition, and documentation.

Because no organization remediates everything at once, Title2Ready begins by supporting triage. The workflow helps teams identify what is in scope versus out of scope, then prioritize what matters most first. For example, a syllabus needed on day one carries different urgency and impact than an optional reading assigned late in the term. This triage step creates clarity and momentum, and it reduces the risk of spending effort on low-impact assets while high-impact assets lag behind.

From there, remediation becomes a standardized production workflow. Each course or content area is evaluated for its list of digital assets; each digital asset is then routed through a consistent remediation process that includes automated and manual steps. Every step is documented, progress is updated immediately, and activity is traceable at both the user and asset level.

This is where the heavy lifting happens for first-time remediation. It is the heart of the “update the digital asset” effort: disciplined execution, consistent documentation, and measurable completion.

3. Compliance Improvement

End-user review, institution-specific scoring, and proof of outcome

Once remediation work is completed, teams still need a practical way to review results from the end-user experience perspective. Title2Ready provides that verification layer through Screen2Text (S2T), a proprietary tool that loads a digital asset and generates a text transcript approximating what a screen reader would announce when interpreting a web page. This gives content owners and remediation teams a straightforward “sanity check” that is easy to review and useful for quality control. (Screen2Text will later extend this same approach to PDFs.)

Compliance Improvement also includes a Title2Ready scoring rubric that organizations can tailor to their own definitions, goals, and risk tolerances. This supports consistent decision-making across teams and provides a common language for progress reporting, escalation, and exception handling.

Many organizations already use industry tools such as Ally as part of their accessibility efforts. Those tools can be helpful for technical indicators and broad accessibility support, but they are not a guarantee of WCAG conformance. Some checks are outside their scope, and some findings do not map cleanly to WCAG success criteria. Title2Ready is explicitly WCAG-centric and is designed to help teams validate results, document outcomes, and demonstrate best-effort activity in ways that stand up under audit or legal scrutiny.

Strategic Positioning

ADA Title II compliance is both imminent and long term.

ADA Title II guidance emphasizes organizational accountability. Individual best efforts are rarely persuasive without centralized oversight, consistent workflows, and defensible documentation.

Title2Ready solutions operationalize that accountability by converting accessibility remediation from scattered activity into structured governance, measurable execution, and end-user-oriented verification.

More importantly, the T2R solutions provide immediate relief for impending deadlines while simulatenously building the long term sustainment infrastructure. The efforts applied today to meet the new compliance requirements is the same effort which will ensure long-term compliance and sustainability.


 

Why this matters now

Many organizations face an approaching compliance deadline and are still carrying large volumes of public-facing digital content and service interfaces (e.g., backlogs of PDFs, web pages, course content, and other digital assets.) Title2Ready is built to provide a comprehensive, structured document remediation workflow for organizations seeking guidance and repeatable, role-based remediation processes.
 
Under 28 CFR § 35.104 (definitions), a public entity means:
  1. Any State or local government
  2. Any department, agency, special purpose district, or instrumentality of a State or local government
  3. Certain commuter authorities (e.g., Amtrak-like authorities created by governments)
There are, in fact, two compliance dates based on the public entity’s served population. "Population served" means the number of residents in the governmental jurisdiction responsible for the public entity — not employees, enrollment, website users, program participation, or account holders. If a public entity is created by state statute (e.g., a state university authority), the served population is the population of the creating government — typically the entire state — not the surrounding city.

What "served population" means for the compliance deadline

For the Title II web and mobile accessibility rule, the compliance date is based on the population of the governmental jurisdiction the public entity serves. It is not based on the number of employees, students, website visitors, or account holders.

Organization type (what they call themselves) What population is counted (served population) Example (what to use)
State agency / department Residents of the state State DOT, State Health Department - use state population
County government / county agency Residents of the county County Health Department - use county population
City / town government Residents of the city/town City Hall / city services site - use city population
Public university / state college Residents of the governing jurisdiction (often the state) Public university - do not use enrollment; use state population (or the creating government)
Community college system Residents of the governing jurisdiction (state/local) State-run system - use state population
K-12 public school district Residents within district boundaries School district - use district population, not student count
Public library system Residents of the jurisdiction funding/operating it City or county library - use city/county population
Transit authority / public transportation entity Residents of the establishing jurisdiction or district Metro transit authority - use metro/district population
Special-purpose district (water/sewer/utility district) Residents within district boundaries Water district - use service/district area population (jurisdictional boundary)

Common misconceptions (what "served population" is NOT)

Misconception Why it is incorrect
Number of employees That relates to ADA Title I (employment). Title II deadlines are jurisdiction-based.
Number of students / enrollment Enrollment is not the population measure. Public entities are classified by the jurisdiction they serve.
Website visitors / traffic volume The rule applies regardless of site traffic. The compliance date is not usage-based.
Number of user accounts Accounts represent one service. They do not define the public entity's served population.
Number of constituents served (program usage) Program participation is not the metric; the metric is the population of the governmental jurisdiction.

 
Here is a general guide to evaluate what category a given organization falls under and how the ADA refers to them (as well as their more common references).
What they often call themselves What ADA / DOJ calls them (Title II) Compliance deadline (population 50,000+) Compliance deadline (population under 50,000)
State government (e.g., Commonwealth/State of X) Public entity (State government) April 24, 2026 April 26, 2027
County / Parish / Borough Public entity (local government) April 24, 2026 April 26, 2027
City / Town / Township / Municipality Public entity (local government) April 24, 2026 April 26, 2027
Department / Agency / Office / Commission (e.g., Police Dept, Library) Public entity (department/agency/instrumentality of a State/local government) April 24, 2026 April 26, 2027
Public university / community college / state college Public entity (instrumentality of a State/local government) April 24, 2026 April 26, 2027
K-12 school district (city/county/independent) Public entity (school district; NOT a “special district government” for this rule) April 24, 2026 April 26, 2027
Special-purpose district (e.g., water/sewer, transit authority, utility district) Special district government (a type of public entity) (Special districts always use the later date: April 26, 2027) April 26, 2027

Notes:
  • The DOJ web and mobile accessibility rule requires public entities (State and Local entitiews) to provide digital services and content (e.g., websites, electronic documents, mobile apps, and interactive services) in conformance with the WCAG 2.1 Level AA technical standard.
  • Compliance dates are based on population (with special district governments using the later date). Also, Special district governments use the later compliance date regardless of population size.

Projects in development

Asset Triage Workflow

Identify high-risk content, categorize by type, and assign role-based remediation tasks.

Alpha

PDF Accessibility Helper

Support for remediation steps such as tags, reading order, titles, and alternative text workflows.

Coming soon

Web Content Checklist

Actionable checks aligned to WCAG 2.1 AA technical standard for common university website patterns.

Coming soon

View all projects