Guide
The browser extension
The extension audits the tab you are looking at, on your command, and shows you a fix for each issue. It works on its own with no account at all — connecting one adds history rather than unlocking the scan.
Last reviewed: 8 August 2026
Running an audit
Click the Mend icon in your toolbar to dock the panel beside the page, then Run audit. Mend reads the active tab and checks it against the WCAG rules you have enabled.
Nothing is scanned until you ask. The extension does not audit in the background, does not follow you between tabs, and does not scan pages you have not pointed it at.
Results are grouped by rule and sorted by severity, then by position on the page. Each issue comes with a fix and a button to highlight the offending element in the page, which is usually faster than reading a CSS selector and hunting for it yourself.
Auditing is free and unmetered. Scan the same page fifty times in an afternoon; there is no quota and no account required.
What it can and cannot see
The extension audits the page as rendered, in your browser, in its current state. That is its main advantage over a scanner that fetches a URL: anything you can get on screen can be audited, including pages behind a login, modal dialogs, expanded menus and form error states. Get the page into the state you care about, then run the audit.
It also inherits the honest limit of every automated checker. It finds the issues a machine can find — missing labels, contrast failures, broken landmark structure — and cannot judge whether alt text is accurate or whether a heading actually describes what follows. That boundary is discussed in generating a conformance report, where it matters most.
Connecting it to an account
Audits live in your browser until you send them. Signing in and connecting the extension lets you Save to dashboard, which is what turns a series of one-off scans into a history you can compare.
Connecting is one click on the connect page. Behind it, Mend issues the extension an API key of its own — the same kind of credential a CI job would use — and the extension stores it. There is no code to copy and nothing to paste.
Because it is an ordinary key, you can see it and revoke it on your Account page like any other. Revoking it stops the extension syncing; the extension itself keeps working, and reconnecting issues a new one.
If you run an audit before signing in, that audit is not lost — the connect flow brings it with you, so the scan that made you create an account is the first thing on your dashboard.
Where synced audits go
A saved audit appears on your dashboard, and is identical to one posted from CI or produced by a monitor. Same rows, same per-rule pages, same trend lines — see the dashboard guide.
Storage is the part that counts against your plan, since auditing itself is unmetered. How many audits an account keeps and for how long is covered in plans and limits.
To remove synced audits, or to disconnect entirely, see exporting and deleting your data. Deleting server-side data never touches anything the extension is holding locally.