# A website overlay does not meet Title II

Title II asks whether people with disabilities can use the public pages and public documents. A toolbar that sits on top of the browser is not that method. Keep the widget or drop it this month. You still need a dated file of the content plus tickets the website vendor can run.

## Who this is for

A clerk whose website vendor installed a toolbar, or whose council was told a widget “covers ADA.” Title II asks whether people with disabilities can use the public website and public documents themselves.

## What the rule looks at

28 CFR 35.200 looks at the content — pages, forms, and public documents — against WCAG 2.1 AA. A toolbar that sits on top of the page is not that method. We do not sell an overlay.

Public small-entity overlay quotes we have on file sit in the $2,500–$4,650 per domain band. Price is not the test. The test is whether a resident can use licenses, packets, and payments without the toolbar.

## What to do with the widget

Keep it or drop it. That is a city call. Either way, you still need a dated file of the content and tickets the website vendor can run so the pages get closer to the standard.

Automated checks cover some WCAG criteria, not all. See [Method](/method). A widget does not fill the rest.

## The short page

[Overlay](/overlay) is the one-screen answer. This note is for the search that starts with the product name of a toolbar.

## This month

Keep or drop the widget this month. You still need a dated file of the public pages and public PDFs, plus tickets the website vendor can run. We do not sell a widget. We do not certify that the site meets the federal standard.