Unboxing the ADA Title II Digital Compliance Handbook and Toolkit

The idea for these two books didn’t come from a whiteboard session. It came from hearing the same question over and over on client calls: “What do other counties do about this?” Or cities. Or school districts, depending on who was asking.

After enough of those calls, I noticed the honest answer was always the same, regardless of who asked it. Different size agency, different budget, different level of technical know-how. Same roadmap underneath. Same approaches.

So instead of walking a new agency through that process one conversation at a time, I finally sat down and started compiling all the Word docs that I had. That’s the short version of how the ADA Title II Digital Compliance Handbook and its companion Toolkit came to exist.

I’ve gotten enough questions about them since we started talking about them that I wanted to do a straightforward post about what they actually are. What’s inside each one, and how they fit together. I didn’t write this as a sales pitch, but more as an unboxing.

If you’re on the fence about whether either one is worth adding to your compliance library, this should tell you what you need to know either way.

What the ADA Title II Handbook Actually Is

The ADA Title II Digital Compliance Handbook is a 12-phase (month) roadmap for public agencies working toward Title II compliance. Think cities, counties, school districts, libraries, and regional administrators, basically any ADA Title II covered entity. It’s built directly out of real client engagements, not written from theory first and tested later.

The phases, the sequencing, who owns what at each step, none of that was invented for the book. It’s our actual client process, written down so an agency that isn’t working with us directly can still follow it.

Spoiler alert: this takes time. That’s why it’s organized into twelve phases, each one tied to a month:

• Phase 1, Foundation: getting your team and project structure in place before anyone touches a scan tool.
• Phase 2, Digital Inventory: cataloging every website, subdomain, mobile app, and third-party platform you’re responsible for.
• Phase 3, Baseline Audit: your first real accessibility audit.
• Phase 4, Remediation Planning: turning that audit into a prioritized plan instead of a list everyone just stares at.
• Phases 5 & 6, Remediation: fixing web content and documents separately, because PDFs and Word files break in different ways than a webpage does.
• Phase 7, Procurement & Vendors: reviewing third-party platforms, where agencies often get quietly exposed by assuming a vendor’s product was accessible and never checking.
• Phase 8, Training & Culture: building the habits that keep fixes from unraveling.
• Phase 9, Verification & QA: making sure what you fixed actually stayed fixed.
• Phase 10, Policy & Governance: the paperwork that makes the program durable instead of dependent on one person’s memory.
• Phase 11, Final Verification & Documentation: closing out the year with a clean, defensible record.
• Phase 12, Ongoing Monitoring: because Month 12 isn’t a finish line, it’s when the program should be running on its own.

Every phase in the book follows the same structure: what it covers and why it matters, who owns the work, and the specific action items. You’ll also find what you should have when you’re done, the mistakes we see agencies make at that stage, and where Accessiblü fits in when that’s relevant. More on that last part below.

The book also gives you two starting points depending on where you actually are. If you haven’t started yet, there’s a path that takes you through the phases in order. If you’re already mid-project, there’s a path built around scanning the checkpoints for phases you think you’ve already finished.

Oh, and no, it doesn’t have to take a year.

But, yes, you can combine phases or work through them in less than a month. Accessibility compliance is about establishing a process. Not fixing one thing and calling it a day.

What the Toolkit Actually Is

The Toolkit is the companion piece. It’s twenty appendices, A through T, of the actual templates, checklists, and rubrics referenced throughout the Handbook. It’s not supplemental reading, it’s the operational stuff you pull out when you hit the phase that calls for it.

A few examples, because “twenty appendices” doesn’t mean much until you see what’s actually in them:

• A Digital Inventory Template for cataloging everything you’re responsible for in Phase 2, instead of building a spreadsheet from scratch.
• A PDF Remediation Decision Tree for Phase 6 that walks you through whether a document should be remediated, replaced, or archived.
• VPAT request letter templates for Phase 7, so you’re not starting from a blank email every time you need documentation from a vendor.
• An Undue Burden Determination Form, because if you’re going to invoke that provision, you need to document it properly.
• An ACR Evaluation Rubric with a green, yellow, red framework, so evaluating a vendor’s report doesn’t come down to a gut feeling.
• Modular accessibility policy templates by department.
• An accessibility statement template with three conformance status options depending on where your agency actually stands.
• A WCAG 2.2 AA success criteria quick reference.
• A full glossary of terms, because half the confusion in this field comes from people using “audit,” “compliance,” and “conformance” to mean three different things in the same meeting.

Every appendix is mapped to the phase it belongs with. You’re not expected to fill all twenty out on day one. You pull each one when the Handbook tells you you’re at the phase that needs it.

What You Actually Get

When you purchase the ADA Title II Digital Compliance Handbook or Toolkit, you get more than just a digital file.

Selling a PDF for $300 is definitely not cool. Not because I hate PDFs (which I do), but because after years in higher ed, I know buying something called a Handbook or Toolkit should be something you can actually use!

That’s why each purchase delivers a ZIP file with several things you can use:

1. A Word doc version. So you can copy/paste and easily make custom letters, memos, policies, etc. It’s also more compatible with assistive technology.
2. An interactive HTML version. So you can work through it on a computer (no internet required) print/save letters, forms, etc. directly from a web browser. This too is also designed with accessibility and usability in mind. (My favorite actually)
3. PDF version for printing. Some clients want to make their own physical copy they can read and carry around. This version allows you to do that.
4. Free Updates. I’ll send out free updates whenever there is an update or revision.

How They Work Together

Think of the Handbook as the “what and why” and the Toolkit as the “here, use this.” The Handbook explains the reasoning behind each phase, who should own it, and what a good outcome looks like. The Toolkit is the paperwork that turns that explanation into something you actually fill out and file.

You can read the Handbook cover to cover and understand exactly what a compliant program looks like. You need the Toolkit to actually build one without reinventing every form yourself. (That’s why I include a Word doc version and interactive HTML file)

They’re sold as a pair or individually. One without the other still works. But the Handbook without the Toolkit means building your own inventory spreadsheet and VPAT letters from scratch, and the Toolkit without the Handbook means a stack of forms with no roadmap telling you when to use each one.

What They Cost, and Why That Matters to Me

The Handbook is $397. The Toolkit is $297. Together as a bundle, it’s $597.

Here’s something I run into on almost every first call with a public agency: they don’t have a budget for this. Most had never even heard of the ADA Title II rule or its deadlines until about a week before we talked. Nobody set money aside for something nobody knew existed.

Then they start calling around for quotes, and some accessibility companies treat this rule like a cash cow. I’ve seen agencies quoted anywhere from $50,000 to half a million dollars just to “comply.” PDF remediation companies are some of the worst offenders, quoting six figures to touch every page in an archive that, realistically, doesn’t need every page touched.

That’s not a compliance plan. That’s an invoice with a compliance label on it.

My goal with the Handbook and Toolkit is to help public agencies, most of whom are already stretched thin, see exactly what they need to do and what a realistic plan looks like. They shouldn’t have to find tens of thousands of dollars first just to get started.

This isn’t really about compliance for its own sake either. It’s about the people those agencies serve actually having access to the information and services they have a right to access. That is, at the end of the day, the entire point of the rule.

Which Parts Accessiblü Actually Helps With

This is the part I most wanted to be straight about. The Handbook and Toolkit are genuinely built to work for an agency doing this entirely in-house, you do not need to hire us to use either one. But a handful of phases are places where outside expertise makes a real difference, and I’d rather tell you exactly where those are than be vague about it.

Phase 3, the baseline audit, is one of them. Our audit methodology covers automated and manual testing, screen reader testing with JAWS, NVDA, and VoiceOver, and a report that gives you remediation guidance alongside every finding. That’s genuinely hard to replicate in-house unless you already have accessibility specialists on staff.

Phase 5 and Phase 6 are where we help verify code-level fixes and handle document remediation directly, particularly the higher-complexity PDFs that eat up the most staff time for the least return.

Phase 7 is vendor and procurement review. We’ll evaluate ACRs from your existing vendors, flag which ones carry the most risk, and review RFP language before it goes out. Procurement is one of those areas where an outside read on a vendor’s documentation catches things an internal team doing this for the first time tends to miss.

Phase 9 is verification testing: confirming that what got fixed actually works for someone using a screen reader, not just that it looks right in the code.

Phase 10 is policy and governance, and it’s part of our standard engagement scope. We draft the organizational accessibility policy, the department-level addenda, and the public accessibility statement. You provide the facts about where your program stands, we provide language that’s accurate and doesn’t overpromise.

Phase 11 is the final verification audit, using the same methodology as the baseline so the comparison actually means something. It also includes help assembling the conformance documentation package at the end.

Phase 12 is where an ongoing relationship tends to make the most sense, since that’s when the project becomes an operational program. That’s the Managed Accessibility Ops side of what we do: continuous monitoring, recurring testing, and staying on top of the platform updates and content drift that quietly undo a year of remediation work if nobody’s watching for it.

Phases 1, 2, 4, and 8 are largely things an agency can run internally with the Toolkit templates doing most of the heavy lifting. Team assembly, inventory, prioritization planning, and training are exactly the kind of structured work the Handbook and Toolkit are built to make possible without outside help.

Agencies that do end up working with us past the books get a dedicated team and direct access to us for questions, not a salesperson who disappears once the contract is signed. There’s no RFP or RFQ process required, and no six-figure ask to get started. We’d rather be a vested partner in getting this right than another line item you had to fight to get approved.

Why I Wrote It This Way

I should be clear about something. I didn’t build Accessiblü. I took over as CEO in July of 2026, and the company had already been doing this work for years before that.

What’s always been true here, long before I was the one running it, is that Accessiblü is built around relationships and process, not overlays and not automated shortcuts. Accessibility takes real expertise and real work with real people who have real disabilities. That’s not a tagline, it’s just what the work actually requires if you’re doing it honestly.

The Handbook and Toolkit are built the same way. Nobody audits payroll once every few years and calls it done, and digital accessibility doesn’t work that way either. These two books exist to get an agency to a place where accessibility runs like an operational habit instead of a one-time scramble, whether or not we’re ever part of that engagement.

If you’re trying to figure out where your agency actually stands right now, or which phase you should already be working on given the extended deadline, that’s a conversation worth having. It doesn’t matter whether you end up using the books, working with us, or both. Reach out and we can talk through it.