The Automated Scan Findings section holds the detail your developers need. This is how to use it.
Finding the page you want
Each scanned page is its own block, showing its address, whether it was tested successfully, and how many issues it has. Pages with no issues are listed last. Use Search by URL to jump to one page, and the expand and collapse buttons to open or close everything at once.
To see every page affected by one issue, click that issue in Unique Issues Found further up. The list filters to matching pages, and Clear Filter puts it back.
What each issue shows
- Its impact level and a short title saying what is wrong.
- The WCAG requirements it relates to.
- A documentation link with a full explanation of the rule and examples of how to fix it.
- Affected Elements. Every place on the page where the issue occurs.
Reading an affected element
Each element shows three things:
- A selector. A precise address for the element in the page's code, which a developer can paste into their browser's tools to find it immediately.
- A code snippet. The element's HTML, so you can often recognise it at a glance.
- What to fix. A short list of the conditions the element fails. Any one of them being fixed is usually enough.
For contrast problems you also get the measured contrast ratio against the required one, the two colours with swatches, and a preview of how the text looks.
Handing it over
Copy All on an issue copies every affected element's details at once, ready to paste into a ticket. A useful habit is one ticket per unique issue, not per page, since the fix is usually shared.
Pages that failed to load
A page marked as failed was not tested, so it shows no issues. That is not a clean result. Check the page loads for an ordinary visitor, then include it in your next scan.