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.
Overview
Alerts are set up under Accessibility → Settings → Alerts. Two switches control them: Email me when a publish adds errors, and Weekly summary email. Send to takes one or more addresses separated by commas and starts with the site admin email. Slack webhook is optional and takes an incoming-webhook address from Slack. Send a test alert tries both channels with the saved settings.
Lumtera keeps a fingerprint of the errors on each published post. When a save adds errors that were not there before, it queues one alert right after the save, so the Publish button is never held up. The message names the post, the person who saved it and up to ten of the new errors, with a Fix it now link to the editor. Scheduled page checks send their alerts through the same channels.
The weekly summary goes out by email every Monday at 09:00 site time. It gives the average score and its change since last week, the error and review totals, the five most common issue types and five pages that need attention. The Overview screen also gains a Score history chart built from a daily snapshot, with a Show the data table for anyone who prefers numbers to a line.
Why it matters
On a site with many authors, the person responsible for accessibility is rarely the person publishing. Without alerts, problems are found by visitors — or by a demand letter.
What you get
- Email and/or Slack alerts when a publish adds new errors.
- Errors are fingerprinted, so saving the same post again never re-alerts.
- A weekly summary every Monday with the week's change.
- Daily score snapshots kept for 400 days, shown as a trend chart.
How it works
-
Add recipients
Enter email addresses and, optionally, a Slack incoming webhook.
-
Publish as usual
Lumtera compares each publish with what was already known.
-
Act on what is new
Each alert links to the post that changed, ready to fix.
Who it helps
-
Sites with many authors
The person responsible for accessibility hears about a new problem the day it is published, without reading every post.
-
Agencies on a retainer
Send alerts to a shared inbox or a Slack channel and spot regressions long before the next monthly report.
-
Managers who need a trend
The Monday summary and the Score history chart show whether the site is getting better, with figures you can quote.
Good to know
How it behaves, what it needs, and where its limits are.
- Plans and access
- Included in every Pro plan. Changing alert settings needs an administrator.
- What triggers an alert
- Only errors on published content. Drafts, pending posts, items that need review and tips never alert. A post that goes live counts every error it carries as new. Bulk scans, imports and the first scan after Pro is installed only set the baseline, and when several posts gain errors in one go, such as a bulk publish, you get one summary alert instead of one per post.
- Slack, Teams and other tools
- The Slack field accepts only addresses that start with https://hooks.slack.com/. For Microsoft Teams or your own tools, Accessibility → Settings → Integrations can send the same events to up to ten webhook endpoints.
- Score history
- One snapshot is saved per day and kept for 400 days. The chart shows the last 90 days and appears from the second day. The weekly summary is sent by email only.
- Email delivery
- Email goes through WordPress's own mail function, so it is only as reliable as your site's mail setup. Send a test alert tells you if sending failed.
Questions
Something else on your mind? Contact support
Does Slack need an app?
No — a standard Slack incoming webhook URL is all it needs.
Will editing an old post alert about errors it already had?
No. Only errors that were not in the last scan of the published version count as new. Re-saving a post with known errors sends nothing.
Can different people get different alerts?
Not in this version. Alerts and the weekly summary all go to the same Send to list and Slack channel. Fixes assigned to someone are emailed to that person separately.
Do alerts cover the theme and menus?
Publish alerts cover post content. Scheduled page checks fetch whole pages, theme included, and alert through the same email and Slack settings when a page gains new errors.
More in “Monitor and fix”
-
Pro
Fix tracking
Turn issues into tasks, assign them, and let Lumtera close each task when a re-scan confirms the 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.
-
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.