10. FAQ
Why isn't my Readiness Score moving?
The stored Readiness Score moves when a scan completes and re-checks your pages. If you have marked findings as fixed, or deferred them, but a re-scan has not run yet, the score will not change until the scan re-checks the page. Run a manual re-scan from the Compliance Overview view to force an update.
If the scan ran and the score still did not move, the most common reason is that the fix did not actually land on the page. Open the finding's Evidence tab; the scanner shows you what it currently sees. Compare that to what your team thought was deployed.
How much of WCAG does the scan really cover?
WCAG 2.1 A/AA has 50 success criteria. AuditAble only counts a criterion as tested when an automated rule for it actually ran during your scan. Today that is 28 of the 50 criteria (33 when AI-assisted evaluation is enabled). The scanner also screens collected media and interaction evidence and flags likely issues on more criteria, but a review flag never counts as a tested or passed criterion. Every report shows the actual criteria count for that scan, and every criterion the scan did not test is reported as Not Evaluated. The remaining criteria still require a human reviewer using assistive technology. We do not mark untested criteria as passed.
In practical terms: AuditAble catches the issues that show up the most in DOJ complaints and plaintiff lawsuits. It does not replace a manual accessibility audit if you want full Level AA coverage; it complements one.
Can AuditAble certify that our site is ADA compliant?
No. No automated tool can. "ADA compliant" is a legal determination, made by your counsel or, in a dispute, by a court. Tools produce findings; lawyers and courts produce determinations.
We will never put "WCAG compliant," "ADA compliant," "508 certified," or any equivalent phrase on a report. If you see one of those phrases used by another vendor, that is a marketing claim, not a legal one.
What AuditAble produces is a Readiness Score and a defensible audit trail showing the remediation work your team has done. That is what helps you in a complaint, an audit, or a budget request.
What happens after the DOJ deadline?
April 26, 2027 (for governments with 50,000+ residents) and April 26, 2028 (for smaller governments) are the dates after which the DOJ rule is enforceable. After those dates, residents and advocacy groups can file complaints and lawsuits if your site does not meet the technical standard.
Most cases will not go to court. They will be settled through the DOJ's complaint process. What helps you in that process is showing you have a remediation program, you have prioritized findings, and you have a documented timeline. That is the same audit trail AuditAble produces.
How often should we re-scan?
The automatic cadence is monthly on Starter and Professional. That is enough for most sites.
Manual re-scans are useful right after your team has deployed a batch of fixes, or when you launch a new section of the site. Each re-scan refreshes your dashboard, but the underlying counts do not change unless your site changes, so re-scanning every day will not produce different numbers.
We have a vendor-built site. How do we get them to fix things?
Open any finding tied to a vendor template. Use the Copy for developer button at the top of the detail panel; the copied ticket includes the rule, the page, the element, and the fix instructions. Send that to your vendor.
If your vendor is unresponsive, defer the finding with the Vendor or contractor must fix reason category, add a note (vendor name, ticket number, date contacted). On every report, that exception will appear in the appendix with the explanation. It does not erase the issue; it documents that the issue is outside your unilateral control. That is exactly what a council member or an auditor wants to see.
Can we use AuditAble for our staging site before launch?
Yes. Add the staging URL as an additional domain in Settings. If the staging URL is behind a basic-auth wall, add the credentials in the domain settings (we use them only at scan time and never store them in logs).
For Title II purposes, your production site is what matters legally, but scanning staging is the right way to catch regressions before they reach residents.
What about PDFs and documents? Are those covered?
Currently the dashboard covers your web pages. Document accessibility (PDFs of council minutes, agendas, budgets) is on the roadmap and we are working on a Document Remediator feature. If you have a large PDF library, email support so we can put you on the early-access list.
How do we handle a complaint that mentions our site?
Two things, in this order:
- Talk to your legal counsel. AuditAble is not legal advice.
- Email support for a current readiness report (see Section 12). The report shows your Readiness Score, the work in flight, the exceptions (with reasons), and the timeline. That report is the artifact your counsel will use to respond.