Why are there differences between Report and Audit results?
Possible reasons for discrepancies
Differences between the results of a Report and an Audit usually occur due to technical or display-related deviations during the scan.
The most common reason is that the website is in a different state during the server-side scan (Report) than during the manual Audit in the browser.
The following factors may play a role:
Different viewports
Reports are scanned with a default resolution of 1920 × 1080.
In contrast, the Audit depends on the current browser window being used.
Dynamic content and interactions
Elements such as cookie banners, login states, or information banners may behave differently or not appear at all depending on user interaction or the time of testing.
Time- or context-dependent elements
Some content is displayed only temporarily or depending on the server environment. Examples include:
-
A/B testing variants
-
Dynamically integrated tracking elements
-
Seasonal banners
Technical scan differences
All scans are performed using a current Chromium browser with realistic user-agent settings.
However, minor differences may still occur in rendering compared to a local Chrome browser.
In such cases, it can be helpful to check the screenshot in the dashboard to understand the state of the page during the scan.
Check filter settings
Another possible reason for differing results lies in the filter settings used in the Audit.
Ensure that the following options are configured consistently:
-
WCAG conformance level (e.g., AA or AAA)
-
Activated best-practice checks
-
Critical issue filters
In the Audit tool, it is also possible to hide entire categories of issues (e.g., design or code) in the settings.
Please also review the settings page for active or inactive configurations.
Only if these settings match can the results from the Report and the Audit be compared in a meaningful way.