Verify Fix
Last updated: November 7, 2026
Verify Fix checks whether a resolved, verified, or closed issue is fixed on the page. OverlayQA reruns a check matched to the issue and shows the result with before and after evidence. Your team decides what happens next: a check never closes or reopens an issue by itself.
Verify One Issue
- Open a resolved, verified, or closed issue in the dashboard or the extension.
- In the extension, open the page the issue is on first, because the check captures the page you have open.
- Click Verify fix. A check usually takes about 30 seconds.
- Read the result, then choose what to do with the issue.
Where the Check Runs
| Page | Where the check runs |
|---|---|
| A public page, from the dashboard | OverlayQA's server opens the page at the issue's original viewport. |
| A local or private page, or one behind a login | The Chrome extension checks it in your own browser session. |
Verify Fix does not run in Team Review.
What Each Issue Type Checks
| Issue type | The check |
|---|---|
| Accessibility | Reruns the axe-core rule that flagged the issue. |
| Design token | Remeasures the CSS property that was captured. |
| Bug and Mismatch | Compares the original screenshot with a fresh one, using AI. |
| General and Improvement | Cannot be verified against the page. |
Reading the Result
| Result | What it means | What you can do |
|---|---|---|
| Fix verified | The check passed. | Mark as verified, or Reopen. |
| Passed (with caveat) | The check passed with something worth a look. | Mark verified, or Reopen. |
| Fix failed | The problem is still on the page. | Reopen as regressed, or Retry. |
| Inconclusive | The check could not decide. | Mark as verified, Reopen, or Retry. |
| Couldn't verify | The check did not finish. | Try again, or Skip verification. |
Inconclusive and Couldn't verify do not mean the fix passed. OverlayQA never changes an issue's status on its own.
Verify Several Fixes
Select resolved issues on the dashboard Issues page and choose Verify fixes. OverlayQA groups them by page, and the Chrome extension checks each page in turn, including staging and pages behind a login. In the extension, Verify all N resolved on the issue list starts the same check from the list you are looking at.
Results Stay on the Issue
Saved results stay on the issue, so they are still there when you reopen it. A share link shows the proof as pictures: when an issue's status is Verified and its latest decisive check passed, its card shows Before and After ยท fix verified with the date of the check.
Limits
Every plan includes a monthly allowance of verifications for each project.
Frequently Asked Questions
Does Verify Fix close or reopen issues automatically?
No. It shows the result and your team decides, with Mark as verified, Reopen, or Reopen as regressed.
Can it check a page behind a login?
Yes, in the Chrome extension, which checks the page in your own browser session. OverlayQA's server can only open public pages.
Can an AI coding agent verify a fix?
Yes, for public pages. Through the MCP server, verify_issue checks a resolved issue and returns the saved verdict. It never changes the issue's status.