3. Working Through Findings
This is where most of your time in the product happens.
3.1 The Fix Queue
Click Fix Queue in the sidebar. You see every open finding on your scanned pages, grouped by page URL. Each finding row shows:
- Severity badge (Critical, Serious, Moderate, Minor)
- Plain-English title (for example, "Heading text is not informative")
- The page where it was found
- Fix type chip (Content Fix, Code Fix, Design Fix, Vendor Fix, Developer needed)
- Estimated time to fix
- Current status (Open, In Progress, etc.)
The list is sorted Critical first, then Serious, then Moderate, then Minor, then by estimated impact within each severity. The intent is that the first thing you click is the most important thing you could fix today.
3.2 The detail panel
Click any finding row. A panel opens on the right with the full detail. Across the top:
- The plain-English title
- The severity, status, and fix-type chips
- A Defer button (when the finding can be deferred, see Section 4)
- A Copy for developer button that copies a structured ticket ready to paste into Jira or ServiceNow
Below that, four tabs:
- Fix Instructions: what to change, in plain language, with code snippets where applicable
- Assignment: assign the finding to a team member (see Section 3.5)
- Evidence: the HTML element, the screenshot, the rule that fired
- Element: the raw HTML and CSS selector for the affected element
The right column also includes a "Why this matters" block (resident impact in human terms) and a "How to fix" block (the action your team takes). Both are written for a non-developer reader. Developers get the same content plus the technical references.
3.3 Quick Wins
On the Compliance Overview view (the executive summary), you may see a "Quick Wins" callout. These are the smallest content fixes you can knock out today without a developer. Usually two or three findings.
Doing the Quick Wins first builds momentum, demonstrates progress to your team, and gets your Readiness Score moving on day one. Quick Wins do not change your legal position by themselves, but they raise the score and show active remediation if you ever have to defend your timeline.
3.4 Marking findings as fixed
Once your team has applied a fix:
- Open the finding's detail panel
- Click the status chip and choose In Progress (while you are working on it) or Ready for rescan (once the fix is deployed)
- The next scan will confirm the fix and move the status to Verified fixed automatically. You do not need to manually mark anything Verified fixed.
If the next scan still finds the issue, the status returns to Open and the panel shows an "Evidence" tab entry explaining what the scanner still sees.
3.5 Assigning findings
Click the Assignment tab in the detail panel. Pick a team member from the dropdown. They will see the finding in their personal list and receive a notification email (notifications are controlled in Settings).
Assignments are not roles. Anyone with Member or Admin access can assign or reassign. The assignment is a hint to your team about who is working on what, not a permission boundary.
3.6 Re-scanning
Two ways to trigger a fresh scan.
- Run New Scan button at the top right of the Compliance Overview view scans your full site.
- The scanner runs automatically each month on every paid plan, including custom plans.
A free 15-page scan usually takes 2 to 5 minutes. Paid scans with hundreds of pages run in the background and can take longer, especially when a site is slow, asks crawlers to wait, links many PDFs, or has login-walled pages. The dashboard shows progress while it runs. You can leave the page; AuditAble will email you when it is done.
If you have just applied a batch of fixes and want immediate verification, use Run New Scan. Otherwise, the scheduled cadence will catch it.