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.
Overview
Fix tracking turns a finding into a task. A Track fix link appears on each issue in the block editor's Accessibility sidebar and in the Content report. Choose who the fix is assigned to and the task is saved against that post. From then on the issue shows the task's status and assignee instead of the link, so everyone working on the post can see it is being handled.
The Fixes screen under Accessibility shows four counts: Open, In progress, Fixed in the last 30 days and Assigned to me. Below them you can filter by status and by Assigned to, then change a task's assignee or status straight from the table. History opens the full log for a task: who created it, who it was assigned to, each status change and what each re-scan found.
Verification runs after every scan of the post. If the issue is gone, the task becomes Fixed and the history says the fix was confirmed. If it comes back, the task reopens. If the markup changed but the same kind of problem is still on the post, the task follows the new finding and stays open. Dismissing the issue closes its task as Won't fix.
Why it matters
Remediation stalls in spreadsheets: nobody knows who owns what, and "fixed" tickets quietly come back. You need tasks that know whether the problem is really gone.
What you get
- Statuses: open, in progress, fixed, won't fix — with assignees who get an email.
- Tasks close themselves when a re-scan no longer finds the issue, and reopen if it returns.
- Tasks follow an issue even when the surrounding markup changes.
- A full audit trail of every change.
How it works
-
Create tasks from issues
From the report, turn findings into tasks.
-
Assign and work
Assignees get an email. Editors and administrators manage every task under Fixes; authors see their own under My fixes.
-
Verified automatically
The next scan marks the task fixed — or reopens it.
Who it helps
-
Editorial teams
An editor assigns heading and image problems to the authors who wrote the posts, and each author gets an email with a link to the page.
-
Agencies showing progress
Fixed in the last 30 days counts only fixes confirmed by a re-scan, so the number you show a client is backed by the checks.
-
Remediation projects
Work through a backlog with the Open and in progress filter, narrow it by person, and see at a glance what is left.
Good to know
How it behaves, what it needs, and where its limits are.
- Plans and access
- Included in every Pro plan. Editors and administrators see every task under Fixes. Authors and contributors get My fixes instead: the tasks assigned to them or on their own posts. Anyone can track issues on posts they can edit.
- Who can assign
- Editors can assign anyone who can edit that post, and the assignee gets an email. Authors can only take a fix themselves. Closing an error as Won't fix needs the same permission as dismissing it.
- Content findings only
- Tasks track findings in post content. Findings from Page checks and from the Documents screen cannot be turned into tasks.
- Deleted posts
- Deleting a post permanently also deletes its tasks and their history.
- Activity and integrations
- Task changes also appear under Accessibility → Activity, and can be sent to Slack, Microsoft Teams or your own tools from Settings → Integrations.
Questions
Something else on your mind? Contact support
What happens when an issue is dismissed?
Its task is marked won't fix, and the change is recorded in the task history.
Can an author who is assigned a fix see it outside the editor?
Yes. Authors and contributors get a My fixes screen under Accessibility with the tasks assigned to them or on their own posts, as well as the assignment email and the task's status on the issue in the editor sidebar. The full Fixes screen stays with editors and administrators.
Can I mark a task Fixed by hand?
Yes. It shows as Marked fixed (not yet verified) until the next scan of the post. If the issue is gone, the fix is confirmed; if it is still there, the task reopens and the history records why. Only confirmed fixes count towards Fixed in the last 30 days.
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
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.