Mark a false positive
A false positive is a Scan Bug that is not a real problem on your site. The check fired, and the page is still fine for the people who use it.
Plans. Starter, Plus, Business, and Pro, on Scan Bugs.
Mark a false positive so the team does not spend time on it, and so the health score stops counting it.
- Open the Scan Bug.
- Find Not a genuine issue? and press False positive. You can do this for one instance on a page, or for the check as a whole.
- Choose the scope. This page only leaves the check out of that page's health score. The same check on other pages still counts. Every page with this check leaves it out of the health score on every page where the scan found it.
SiteScan tells AccessUX, so a specialist can see whether that check should be quietened for sites like yours. The bug stays on the list, at the end of Backlog, until you press This is a genuine issue. While it is a false positive, you cannot move it on the bug board.
On Plus, Business, and Pro, leaving the bug out of the score makes that page's health score go up by the amount that issue was costing. Other open issues on the page still count. If you mark only one instance, and the same check fails somewhere else on that page, the page still includes the real cases.
Mark a false positive only when you are sure. If you are unsure, leave it open or ask AccessUX from the bug. A real barrier that you hide will make the score look healthier than the site is.