Skip to main content

How to manage checks and issues

Once your first scan is done, here's how to work through your checks and issues with your team. These steps work the same way in every Monitoring module.

New to checks, issues and potential issues? Start with Understanding checks and issues.

Set a check owner

The Owner of a check gets alerted when that check starts failing again. Why? Fixing everything once isn't enough. When someone publishes a new page that breaks a check, the owner hears about it right away.

  1. Go to Monitor → Accessibility/Content/SEO.

  2. Click the check you want to assign.

  3. Click Owner and choose a team member.

To see only the checks assigned to one person, use the All owners filter.

Use Responsibility to pick the right owner

Each check has a Responsibility tag. It shows which role is usually best placed to fix it. Use it to send each check to the right person. For example:

  • Assign "Images must have alt text" to your content team.

  • Assign structural checks, like page landmarks, to a developer.

  • Assign "Text contrast must meet accessibility standards (AA)" to your designer.

The Responsibility column is hidden by default. To show it, click Display at the top of the checks table and turn on Responsibility.

Ignore a check or an issue

You can ignore a whole check or a single issue. When you do:

  • It moves to the Ignored tab, so you can find it later.

  • It no longer counts toward your score, so your score goes up right away.

  • It won't come back in future scans.

Only ignore things that don't need fixing. Ignoring a real problem makes your score look better, but the problem is still there for the people using your website.

When to ignore a whole check

Ignore a whole check when it doesn't apply to your website. For example, a best practice check your team has decided it doesn't need.

  1. Click the check to open it.

  2. Open the menu at the top right of the check.

  3. Click Ignore.

When to ignore a single issue

Ignore a single issue when that one element is fine, but the check still applies elsewhere. For example, an issue inside an iframe whose content you don't control.

  1. Click the check to open it.

  2. Click the issue.

  3. Click Ignore.

Resolve a potential issue

Potential issues are the only issues you can mark as resolved yourself. Why? The scanner can't tell whether they pass, so it needs you to decide. See Understanding checks and issues.

  1. Open the potential issue.

  2. Check the screenshot and the live page.

  3. If it's fine, or you've fixed it, click the green Mark as resolved button.

Your score goes up straight away. The issue stays resolved, even when you scan again.

For failing issues, you have two options: fix the problem and rescan, or ignore the issue. You can't mark a failing issue as resolved.

Rescan after a fix

After you fix something, rescan to check the fix worked. You don't need to wait for your next scheduled scan.

  • One issue: open the issue and click Rescan.

  • One page: go to Monitor → Pages and click Rescan next to the page.

  • Every page: click Rescan website on the Overview page, or Rescan all pages on the Pages page.

If the issue is gone, it moves to the Resolved tab. When a check has no issues left, it moves to Passing.

When your score updates

  • After a full website scan: your score updates. This includes scheduled scans and Rescan website.

  • When you ignore an issue or mark a potential issue as resolved: your score goes up right away.

  • After you rescan one page or one issue: your score shows a simulated value until your next full website scan.

When your score is simulated, the latest bar in your score history is dashed and marked Pending audit. Click Rescan website to get an accurate score.

Single page and issue rescans don't appear on the Scans page. It only lists full website scans.

Find the element on your website

Each issue gives you what you need to find the problem:

  • A screenshot with the element highlighted.

  • A link to the page where it appears.

  • The element's Selector and HTML, with a copy button for each.

  • The number of occurrences and pages affected.

If a screenshot doesn't show the right thing, click Report screenshot to let us know.

Send an issue to your issue tracker

If your team works in an issue tracker, send issues there instead of tracking them in two places. Monitoring uses the same integration as your project's feedback, so there's nothing extra to set up.

If your project has an integration connected, the issue panel shows a button named after it, like Send to Jira.

  1. Open the issue.

  2. Click Send to followed by your tool's name, like Send to Jira.

  3. Choose the Issue type.

  4. Check the Summary and Description. They're filled in for you with the problem, the recommended fix and the element details.

  5. Click Show all fields to fill in any other fields your tracker needs.

  6. Click Send.

A screenshot is attached automatically. Once sent, the issue panel shows the item's status from your tracker, and it stays in sync.

If your project doesn't have an integration yet, you'll see Add integration instead. Connect one from your project's integration settings.

Next steps

Want to show your progress to a client or your team? Turn your monitoring data into a report with your own branding. See Create reports with the Marker.io MCP server.

Need Help?

If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.

Did this answer your question?