Questions people actually ask
No sales spin — if the honest answer is "no" or "it depends," that's what you'll get.
Sources: DOJ web accessibility rule fact sheet and FTC accessiBe final order announcement, reviewed September 17, 2026. See also our privacy policy.
Do we actually have to do this?
ADA Title II applies to state and local governments, including public schools and special district governments. Under DOJ's web rule, entities with populations of 50,000 or more, other than special district governments, have an April 26, 2027 compliance date; smaller entities and all special district governments have an April 26, 2028 date. The technical standard is WCAG 2.1 AA, subject to the rule's exceptions. Existing ADA duties, including effective communication, continue before those dates. Check the DOJ guidance for your entity's circumstances.
We already have an accessibility widget installed — doesn't that cover us?
An installed widget does not establish that your site meets WCAG. In 2025, the FTC approved a final consent order requiring accessiBe to pay $1 million and restricting unsupported claims that its automated product could make any website WCAG-compliant. Review the site's actual pages, documents and interactions, including with assistive technology, rather than relying on the presence of a widget.
Does a good score mean we're legally safe?
No — and we'll never tell you otherwise. Taggora runs an automated screening against WCAG 2.1 rules. It catches a meaningful share of real issues quickly, but no automated tool catches everything (things like whether alt text is actually meaningful need a person to judge), and no scan is a certification of compliance. We say this plainly because the alternative — implying a scan is a legal shield — is exactly the claim that got other vendors in trouble.
Do you need a login or access to our website's backend?
No. We only ever look at what's already public — the same pages and documents any visitor could reach. We never ask for CMS credentials, an admin login, or access to anything behind a password.
What happens to the email and information we submit?
We use it to deliver your report and follow up about the findings, including occasional emails about related iCityWork services. You can unsubscribe from those emails. We don't sell your information. Anyone with your scan results link can view the summary; anyone you share the report with can read it. Our privacy policy explains service providers, logs and retention.
How long does a scan take?
Most sites finish within a few minutes. We check up to 30 pages and analyze up to 20 linked documents (PDFs and Word .docx files). Requests are paced to limit load on your hosting; site speed and document size affect how long a scan takes.
What if we don't want to fix everything the report finds?
That's normal, and expected. The report ranks findings by severity so you can tackle the highest-risk issues first — a handful of critical fixes usually matter more than clearing every minor item at once.
Wait, what does "Taggora" even mean?
Fair question. It's built from "tag" — literally what a PDF needs to be accessible: a structure tag a screen reader can actually navigate — plus "-ora," because we wanted something that sounds like a real word instead of two SaaS syllables mashed together. Say it out loud: tag-OR-ah. If it reminds you of Angora, that's on purpose.