Every Monitoring module is built from the same pieces. Marker.io runs checks on your pages, and anything that fails becomes an issue to fix. Once you know how these fit together, you can read the results in any module.
From checks to issues
Marker.io tests every monitored page against a list of checks. A check is one rule, like "Images must have alt text".
When part of a page fails a check, that's an issue. Each issue is one specific element, like one image with no alt text.
The same issue can appear more than once. Each time it appears is an occurrence. For example, if the logo in your navigation has no alt text, that's one issue, with an occurrence on every page that shows your navigation.
On each check, Pages shows how many of your monitored pages have at least one of its issues.
Severity levels
Every check has a severity. It tells you how much the problem affects people using your website, so you know what to fix first.
Critical: blocks people from completing core tasks or using key features. Fix these first.
Serious: creates major barriers that make key features hard to use.
Medium: causes noticeable friction, but doesn't block access to key content or features.
Low: a minor issue or a best-practice convention, not a hard barrier.
Each module explains what these levels look like for its own checks. For accessibility, see Understanding your accessibility score and checks.
What each field means
Every check has the same set of fields. You'll see them as columns in the checks table, and at the top of each check's page. If a column is missing, click Display at the top of the table and turn it on.
Owner: the person alerted when this check starts failing again.
Severity: how much the problem affects people using your website.
Category: the type of element the check looks at.
Responsibility: the role usually best placed to fix it.
Issues: the number of issues found for this check.
Pages: the number of monitored pages with at least one issue for this check.
Impact on score: the total points your score goes up once this check passes.
Pass rate: how much of this check passes across your monitored pages.
Some modules add fields of their own. For example, accessibility checks also show the WCAG criterion and level.
Check and issue states
Checks and issues move through different states as you work on them.
A check is always in one of three states:
Failing: at least one issue was found for this check.
Passing: no issues were found for this check.
Ignored: you chose to ignore this check. It no longer counts toward your score.
On each check's page, its issues are sorted into four tabs:
Issues: open issues found in the latest scan.
Potential issues: issues the scanner can't judge on its own. See the next section.
Resolved: issues a later scan no longer found, or potential issues you marked as resolved.
Ignored: issues you chose to ignore. They won't come back in future scans.
Marking a potential issue as resolved raises your score right away. Ignoring a check or an issue raises it too, because ignored items no longer count toward your score.
That's why ignoring is for things that don't need fixing: a check that doesn't apply to your website, or an issue you've checked and confirmed is fine. Ignoring a real problem makes your score look better, but the problem is still there for the people using your website. Everything you ignore stays in the Ignored tab, so your team can review it at any time.
Potential issues
Sometimes the scanner finds something it can't judge on its own. These are listed under Potential issues, with a Needs manual review badge. For example, the scanner can't measure text contrast when there's an image behind the text, so the problem reads Contrast ratio unknown · image behind text.
A person needs to check these. A rescan won't resolve them on its own. Open the issue, look at the screenshot and the live page, then:
If it's fine, or once you've fixed it, click Mark as resolved. It stays resolved, even when you scan again.
If it doesn't apply to your website, ignore it.
Next steps
Now that you know how checks work, see what's specific to accessibility, including how your score is calculated. See Understanding your accessibility score and checks.
Related articles
How to manage checks and issues: set owners, ignore or resolve issues, and rescan after a fix.
Need Help?
If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.