Monitor and fix Pro
Ignore everywhere
Ignore a finding across the whole site in one step — such as markup your theme repeats on every page — with a reason, an optional expiry and a log.
Overview
Ignore rules live under Accessibility → Settings → Ignore rules, right after Checks. Each rule names one check and says which of its findings to hide on every post and page, in content checks and page checks alike. Hidden findings count as dismissed, so they leave scores and totals the way a dismissal does. In the editor they sit with the post's dismissed items, marked Ignored site-wide with who added the rule, when, and the reason.
A rule matches in one of two ways. Exact markup hides findings whose markup is the same as the snippet shown under Markup on the finding; differences in spacing and typography do not matter. Pattern hides findings on elements that look alike: an optional tag followed by .class and #id parts, such as a.social-link, footer#colophon or .cookie-banner. Each part only has to appear somewhere in the element's class or id, so a.social also matches a link with the class footer-social-link. Keep patterns as specific as you can.
Every rule needs a reason, and it can have an expiry date, after which it stops applying at the end of that day, site time. Adding or removing a rule queues the pages it may affect for a background re-check, and the screen says how many are still waiting. The Ignore rules table lists each rule's Check, Matches, Reason, who Added it and when, and Expires, with a Remove button. Recent changes shows the last 20 additions and removals.
Why it matters
A footer link or a plugin's widget can raise the same finding on hundreds of pages. Dismissing it one post at a time is busywork, and leaving it buries the findings that matter.
What you get
- Match the exact markup of a finding, or a simple pattern such as a tag with a class.
- Every rule needs a reason and records who added it and when; an expiry date is optional.
- Ignored findings leave scores and totals the same way a dismissal does.
- A log of rules added and removed, also sent to the activity log and webhooks.
How it works
-
Pick the finding
Use "Ignore everywhere…" on it in the editor sidebar, or add a rule under Accessibility → Settings → Ignore rules.
-
Say why
Add the reason, and an expiry if the fix is on its way.
-
Review the list
Remove a rule at any time; affected content is re-checked in the background and the findings come back.
Who it helps
-
Theme and plugin markup you cannot change
A footer link or a cookie banner that raises the same finding on every page is hidden once, with a reason such as "Reported to the theme author".
-
Decisions made once
When a person has reviewed a repeated item and decided it is not a barrier, that decision and its reason are recorded in one place instead of on every post.
-
Fixes on their way
Set the expiry to the date a theme update is due. If the fix does not arrive, the findings come back as pages are checked again, without anyone having to remember.
Good to know
How it behaves, what it needs, and where its limits are.
- Plans and access
- Included in every Pro plan. Only administrators can add and remove rules. Rules need an active license: without one they hide nothing, and they apply again once the license is active.
- From the editor
- In the block editor's Accessibility sidebar, Ignore everywhere… appears on findings that point at markup. Choose This exact markup or Elements like this one (pattern), give the reason and an optional expiry, and click Ignore everywhere. Manage ignore rules opens the settings screen.
- One check at a time
- A rule hides findings of the check you chose and nothing else. The same markup is still reported by any other check that flags it.
- Errors stay visible
- A rule made in the editor from an item that needs review never hides an error of the same check, for example after that check has been raised to an error.
- Limits
- Up to 500 rules. Markup or a pattern can be up to 1,000 characters and a reason up to 500. A pattern must name a tag, class or id, so a single rule can never hide every finding of a check.
Questions
Something else on your mind? Contact support
How is this different from dismissing?
Dismissing, which is free, hides one finding on one post. An ignore rule hides every matching finding of that check on every post and page.
Does an ignored finding stop being a barrier?
No. The markup is still there for visitors. Use rules only for what is genuinely not a barrier, or for markup you cannot change and have reported to its maker.
What happens if I restore an ignored finding in the editor?
Administrators see Restore next to it. Restoring removes the whole rule, so the finding comes back on every page that has it once the background re-check reaches them.
What happens to a rule when it expires?
It stops hiding findings and stays in the list, marked Expired with its date, until someone removes it. Its findings come back the next time each page is checked.
More in “Monitor and fix”
-
Pro
Email and Slack alerts
Hear about it when a publish introduces new errors — never twice for the same one — plus a Monday summary and a score history.
-
Pro
Fix tracking
Turn issues into tasks, assign them, and let Lumtera close each task when a re-scan confirms the fix.
-
Pro
Issue trackers: GitHub, GitLab, Jira and Linear
Send tracked fixes to the tool your developers already use, by hand or automatically for every new task.
Start with the free plugin today
All 64 checks, the editor sidebar, Elementor panel and site report — free, with no account and no page limits.