← ADA Title II Website Accessibility Evidence Report
Two different shapes: accessiBe installs an ongoing widget and audit subscription on your live government website. This page formats an axe-core scan you already ran into a dated, portable WCAG 2.1 AA evidence record for ADA Title II, free and local — no widget, no installation, nothing shipped to residents.
accessiBe sells accessWidget, a JavaScript widget installed on a live site that applies automated interface adjustments and AI-driven remediation aimed at WCAG conformance every time a visitor loads the page, alongside audits, a generated accessibility statement, and ongoing monitoring — described on accessiBe's own site as a paid, ongoing subscription product marketed to government and education customers preparing for ADA Title II and Section 508. It is built for an entity that wants an installed layer running on the site itself, plus a vendor relationship for audits and monitoring over time. accessiBe's own current pricing and contract terms are not repeated here, since this session cannot verify today's figures against accessiBe's site; only its well-documented product shape — an installed widget plus an audit/monitoring subscription — is described.
This tool does none of what accessWidget does. It installs nothing on a site, changes nothing a resident sees, and has no ongoing subscription. It takes the axe-core JSON export you already generated somewhere else — the axe DevTools browser extension, the axe-core CLI, or a similar tool — and formats it into a dated, readable evidence record split into WCAG 2.1 AA required findings and best-practice extras, plus a link to look up which Title II deadline (April 2027 or April 2028) applies to your entity. It runs entirely in your browser, needs no account and no site access, and uploads nothing you paste.
| Question | Where to answer it |
|---|---|
| I want an installed layer that adjusts my live government website's interface for residents, on every page load, without a developer fixing the templates. | accessiBe — that is the installed-widget job accessWidget is built for. |
| I already ran an axe-core scan and want a dated, readable Title II evidence record of what it found, to file or hand to a developer. | This tool — paste the JSON, get the record, free and instant, nothing installed. |
| I want an ongoing vendor relationship: recurring audits, a generated accessibility statement, and monitoring over time. | accessiBe or a comparable subscription service — this page has no memory between visits and no ongoing service. |
| I want to know exactly what my own axe-core scan found, split into what Title II's WCAG 2.1 AA standard actually requires versus best-practice extras. | This tool — it reports only what the scan you supply contains, split the way the deadline lookup and evidence record describe. |
| I don't yet know whether my entity's Title II deadline is April 2027 or April 2028. | The deadline lookup on this same free tool. |
| Do I need to install anything on my site, or give the tool access to it, to use it? | This tool: no. accessWidget is installed directly on the site by design. |
An entity can reasonably want both: an installed widget and audit subscription like accessiBe's for the live site experience, and a free local tool like this one for turning a specific axe-core run into a dated record that outlives any single dashboard. This page does not evaluate accessWidget's effectiveness and makes no claim about whether an installed overlay satisfies ADA Title II or any other legal obligation — it only describes accessiBe's documented product shape and states what this tool does differently. Automated testing, with or without an overlay installed, typically finds a minority of WCAG issues; neither this tool nor an installed widget determines legal compliance on its own.
This tool needs no account and no sign-in: it is a static page, the formatting runs in your browser, and once it has loaded it keeps working with the connection off.
Installing accessiBe's accessWidget does not by itself prove compliance with ADA Title II's WCAG 2.1 AA standard, and this page makes no claim about accessWidget's effectiveness either way. accessWidget is a JavaScript widget, described on accessiBe's own site as an ongoing paid subscription, that applies automated interface adjustments and AI-driven remediation on a live site. Title II asks whether your web content and mobile apps actually conform to WCAG 2.1 AA, which is a question about the underlying page, not about which vendor's script is installed on top of it. This tool does not install anything or touch your live site at all — it takes an axe-core JSON export you already generated and turns it into a dated, readable evidence record split into what WCAG 2.1 AA requires and what goes beyond it, for your own compliance file.
They are different shapes of product, and a government entity preparing for the April 2027/2028 Title II dates may reasonably use both. accessiBe sells accessWidget, an ongoing paid subscription installed on a live site, plus audits, a generated accessibility statement, and monitoring, marketed to government and education customers. This page has no widget, installs nothing, and changes nothing a resident sees. It takes an axe-core JSON export — from the axe DevTools browser extension, the axe-core CLI, or a similar automated tool — and formats it into a dated WCAG 2.1 AA evidence record you can file or hand to a developer, in your browser, free, with no account and nothing uploaded. An entity wanting an installed layer and an ongoing vendor relationship is buying a different product than one wanting a free, private, dated record of what one automated scan actually found.
No. This site is not affiliated with, endorsed by, or sponsored by accessiBe, Inc. accessiBe and accessWidget are trademarks of accessiBe, Inc., named here only to describe what this tool is and is not, based on accessiBe's own public site.
Open the evidence report to format your own scan, or the deadline lookup to find your entity's Title II date.