The part of your site your team never touched
A resident pays a utility bill. A student registers for orientation. A visitor books a campground. On many public websites, each of those tasks leaves your pages for a vendor’s portal, an embedded widget, or a hosted form. The address bar may change, or it may not. To the person using it, it is still your website.
Under Title II, that matters. the DOJ interim final rule (91 FR 20902) kept WCAG 2.1 Level AA as the standard and moved the compliance dates to April 26, 2027 for public entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special districts. Content a public entity provides through contractual, licensing, or other arrangements can fall within scope. Whether a specific vendor tool is covered is a question for your counsel. Planning for it is a question for your web team, and it is better answered early.
Why vendor content is easy to miss
Accessibility plans usually start with pages the web team can edit. Vendor content does not show up in that view. It lives in someone else’s codebase, often bought by a department, sometimes years ago, and renewed without a web review.
- Embeds such as calendars, maps, chat widgets, and video players load inside your pages but are controlled by the vendor.
- Hosted forms and portals for payments, permits, applications, and registrations often sit on a vendor domain with your branding.
- Linked platforms such as learning systems, ticketing, and job boards may be the only way to complete a public task.
A scan of your own domains may not reach many of these. Some sit behind a login. Others sit on domains your team does not own.
Start with a task inventory, not a vendor list
A vendor list tells you who you pay. A task inventory tells you what the public needs to do. Start with tasks.
- List the public tasks. Pay, apply, register, request, report, book, and find. Walk each one from the homepage to completion.
- Note every handoff. Record where the task leaves a page your team controls, and which vendor takes over.
- Record ownership. Name the department that bought the tool and the person who manages the contract.
- Check the renewal date. Renewals are when you often have more leverage to ask for fixes.
- Rank by impact. A tool that blocks payment or enrollment comes before a tool that shows a decorative feed.
Test the task, then ask for the evidence
An automated scan can flag some issues inside an embed. It cannot tell you whether a resident can finish the payment with a keyboard or a screen reader. Run a short manual check on each high-impact task:
- Can you complete it with a keyboard alone, with visible focus throughout?
- Do form fields have labels, and do error messages say what went wrong?
- Does it work when zoomed, and on a phone?
- Do timeouts warn the user and allow more time?
Then ask the vendor for an Accessibility Conformance Report based on a current version of their product, and compare it with what you saw. A report that conflicts with a failed keyboard test is a conversation to have before renewal, not after.
Put accessibility into the contract
Procurement is where vendor accessibility gets settled. Language your counsel and purchasing office may want to review includes:

- A stated conformance target of WCAG 2.1 Level AA for the parts of the product the public uses.
- A current conformance report, updated when the product changes significantly.
- A process and timeline for fixing reported barriers.
- Notice before releases that change public-facing screens.
- A named contact for accessibility issues.
Contract language does not make a product accessible. It gives you a documented expectation and a way to act on it.
A hypothetical: the permit portal
Imagine a county whose website is in reasonable shape after a remediation sprint. The permit application, though, runs on a vendor portal bought by the planning department. Nobody in the web office has logged into it. A keyboard test finds that the date picker cannot be operated without a mouse, so the application cannot be submitted that way. The fix sits with the vendor. Because the team found it ahead of the contract renewal, the county can ask for a fix timeline as part of that renewal, and record an interim alternative for residents in the meantime.
Common mistakes
- Scanning only your own domain and treating the result as the whole picture.
- Accepting a conformance report without testing the tasks that matter.
- Waiting for renewal season to start the inventory, when renewals are already signed.
- Leaving it to each department without a shared checklist.
Where KWALL fits
KWALL helps public institutions inventory public tasks, test the vendor handoffs, and fold the findings into a remediation plan. See the KWALL accessibility compliance program for how that work is structured. Legal questions about coverage belong with your counsel.
Questions to ask a vendor before renewal
- When was your conformance report last updated, and which product version does it cover?
- Which known accessibility issues are open, and what is the plan and timeline for each?
- How do public users report a barrier, and who responds?
- Do you test with keyboard and screen reader users, or rely on automated checks alone?
- Will you notify us before releases that change public-facing screens?
The answers do not settle compliance. They tell you how much testing you need to do yourself, and how much leverage to use in the renewal conversation. Keep the answers with the contract, so the next renewal starts from a record rather than from memory.
Frequently asked questions
Is vendor content covered by Title II?
Content provided through contractual, licensing, or other arrangements can be in scope. Ask your counsel how that applies to each tool you use.
What is an Accessibility Conformance Report?
A vendor’s document describing how its product conforms to accessibility standards, often written using the VPAT format. It is a starting point, not a test result.
Which vendor tools should we review first?
Tools that the public must use to complete a task, such as payment, application, and registration, ahead of decorative or optional features.
Can an automated scan check embedded tools?
Partly. Scans may catch some issues inside embeds. Task completion with a keyboard or screen reader needs manual testing.
Did the WCAG standard change with the new dates?
No. The interim final rule moved the dates. The technical standard remains WCAG 2.1 Level AA.