Accessibility tools and overlays: evaluate the outcome

A tool is not the outcome

Some website products add controls or modify a page through scripts. Their capabilities and limitations depend on the product, configuration, content, and user task. This reference does not endorse or condemn every product as a class, and does not publish unverified user-behavior statistics.

Evaluate the delivered content

The Title II web rule requires covered web content and apps to meet WCAG 2.1 AA, subject to its specific provisions. Installing a product is not itself the requirement. Check the actual delivered experience and applicable conformance requirements. Read the regulation.

Ask for testable evidence

Suggested review questions: Can users complete tasks with a keyboard and assistive technology? Are names, roles, structure, contrast, focus, and reflow correct? What happens before the script loads or if it fails? What data does the product process? Which versions and tasks does the vendor’s evidence cover?

Automated evaluation tools cannot determine accessibility on their own. W3C’s guidance on selecting evaluation tools explains their role and limitations.

Avoid unsupported guarantees

Request current evidence, test representative tasks, record unresolved barriers, and correct the responsible content or component. Do not equate a badge, score, contract phrase, or marketing claim with a complete legal or technical conformance determination.