2. Your Readiness Dashboard
After you sign in, the dashboard is what you land on. The left sidebar is your navigation; the main area shows whichever view you have selected.
2.1 The sidebar
From top to bottom:
- Your Readiness Score in a card at the top, with a colored bar showing where you stand
- Compliance Overview: a high-level summary view (currently called "Executive Summary")
- Fix Queue: the working list of every open finding, grouped by page
- Criteria Coverage: the per-scan WCAG criterion ledger (what was tested automatically) and the Manual Testing Checklist (what a person still needs to test), stacked as two sections of one page
- Deferred Findings: issues your team has set aside, with the reason documented (see Section 4)
Three more views round out the sidebar: Media & Documents (a manual-review list of PDFs, Office files, and media discovered during your scan), the Compliance Packet Builder, and My Reports.
Near the bottom, next to Help & User Guide: Settings (Profile, Team, Billing, Organization, Security, see Section 7 and Section 8), the AuditAble Assist for your browser link, and your account menu.
2.2 The Readiness Score
A number from 0 to 100 that summarizes how ready your site is for the Title II rule. It is a single roll-up of every open finding on every scanned page, weighted by severity. Higher is better.
What it is:
- A planning and tracking number. Good for prioritization and for showing progress over time.
- Calibrated so that resolving Critical and Serious findings moves the number the most, because those are the ones that actually block residents.
- Recalculated every time a scan completes.
What it is not:
- A legal grade. Not a measure of "compliance." A score of 100 does not mean your site is "ADA compliant." A low score does not mean you will be sued.
- A complete measurement. The score is built from criteria the scan actually tested: 28 of the 50 WCAG 2.1 AA criteria today, 33 when AI-assisted evaluation is enabled. Criteria that were not tested are reported as Not Evaluated and are never counted as passed.
Click the small ? next to "Readiness Score" in the sidebar for the same explanation in popover form.
2.3 The letter grade
A through F, derived from the Readiness Score. Used on the PDF cover so a council member can see the headline without parsing the formula.
| Score | Grade |
|---|---|
| 95+ | A |
| 85-94 | B |
| 65-84 | C |
| 40-64 | D |
| < 40 | F |
Same caveats as the score apply: this is a progress indicator, not a legal determination.
2.4 Severity levels
Every finding is classified into one of four severities. The severity drives both how the finding is sorted in your list and how heavily it weighs on the Readiness Score.
- Critical: a barrier that blocks people from using a page at all. Examples: a keyboard trap that prevents a keyboard-only user from leaving a section, a form with no labels at all. Fix these first. They are the strongest evidence a DOJ complaint or a plaintiff attorney will point to.
- Serious: a barrier that makes a page very hard to use, even if not totally impossible. Examples: missing alt text on a key informational image, color contrast so low that someone with low vision has to squint and guess. Most users with disabilities will hit these and give up. Title II requires "effective communication," and serious findings are where that gets tested in court.
- Moderate: friction with workarounds. Examples: a heading skipped from H2 to H4, or a list visually styled with
<div>instead of real<ul>markup. A screen-reader user can get through, but it feels broken. Less common in DOJ complaints, but accumulates. - Minor: polish issues. Redundant alt text, unused ARIA attributes, or a viewport zoom lock on mobile. These do not block anyone, but a clean record helps if your accessibility posture is ever reviewed.
2.5 Fix types
Every finding is also classified by what kind of work it will take to resolve.
- Content Fix: your communications or web team can do it in the CMS, no developer required. Writing better alt text, fixing link text, updating headings. Roughly 30 to 40 percent of typical findings and usually the fastest path to a higher score.
- Code Fix: a developer needs to change the HTML, CSS, or JavaScript. Adding labels to form fields, fixing focus order, repairing a modal that traps keyboard users.
- Design Fix: a design or brand decision has to happen first. Most often this is color contrast: the brand palette has to change before the developer can update the stylesheet. Tracked separately so your dashboard does not count design-blocked work as developer work.
- Vendor Fix: the page comes from a CMS template or third-party widget (CivicPlus, Granicus, Bang the Table, Tyler Tech, etc.) that you cannot edit. The fix has to go to the vendor. The dashboard records this so you can show your council that you are blocked on an outside party.
2.6 Status
Every finding moves through a small status machine.
- Open: not yet addressed. The starting state.
- In Progress: your team has picked it up. Useful for assigning work and tracking active fixes.
- Ready for rescan: the fix has been applied and you are waiting for the next scan to confirm. AuditAble will move it to Verified fixed automatically once the next scan no longer finds the issue.
- Verified fixed: confirmed fixed by a re-scan. The finding stays in your audit trail and stops affecting your score.
If a fix regresses (a future scan re-detects the same issue), the finding flips back to Open and your score adjusts.
2.7 The "?" help icons
Throughout the dashboard you will see small ? icons next to labels like "Readiness Score," "Critical," and "Deferred Findings." Click one and it opens a short popover explaining that term in plain language.
Every one follows the same structure:
- What it is: a one-sentence definition
- Why it matters: the human impact in plain language
- Under Title II: what the term means in the context of the DOJ rule
- Technical reference: the formal citation, for readers who want it (this part is optional and sits below a divider)
These are written to teach, not just to translate jargon, so a reader with no accessibility training can follow them. The full glossary, in alphabetical order, is in Section 11 of this guide.