Bugs & feature requests
A rule that fired wrongly, a fix that didn't apply, a check you wish existed. False positives are the reports we most want — send one and it goes straight to the people who wrote the rule.
Send a bug reportHelp
Most questions are answered on this page. The ones that aren't reach a person — there is no ticket queue to get lost in. Pick the route that fits.
A rule that fired wrongly, a fix that didn't apply, a check you wish existed. False positives are the reports we most want — send one and it goes straight to the people who wrote the rule.
Send a bug reportInvoices, card changes, cancelling, exporting everything stored for you, deleting the account outright — all of it is self-serve on your account page, no message required.
Go to your accountPermissions, WCAG levels, what the dashboard stores, what Pro adds. Most of it is answered below, and the longer explanations live in the docs.
Read the FAQNo support tiers. Free accounts, Pro accounts and people who never signed up all get answered by the same people, in the same queue. Paying buys history and monitoring, not priority.
Send us a message and Pip will take a look. Bug reports, billing questions and feature requests all land in the same inbox.
Accessibility bugs are usually about one element on one page. The more precisely you can point at it, the faster it gets fixed.
color-contrast.A screenshot helps for layout and focus-order problems. It doesn't replace the selector.
**Rule:** color-contrast **URL:** https://example.com/pricing **Selector:** main > section:nth-child(2) .plan__per **Version:** Mend 1.4.2 · Chrome 128 · macOS **Expected:** pass — the text is #6c6555 on #ffffff **Actual:** flagged as serious, ratio reported 3.1:1 **Notes:**
Security issue instead? Please don't post details anywhere public — send it through the form above with “Security” as the first word of the message, and we'll take it from there.
Not until you connect it. The analysis runs inside your browser, your preferences stay on your device, and there is no analytics or telemetry in the extension at all. Audits leave your machine only after two deliberate steps — creating an account and pasting an account key into the extension's settings — and then only for the runs you choose to save. The privacy policy sets out both halves separately.
It uses Chrome's activeTab model, so it can read a page only on a tab where you've actively invoked it — it has no standing access to any site. If an audit says it needs permission, click the Mend icon in your toolbar on that tab, then run it again.
Mend runs the axe-core rule engine against WCAG 2.0, 2.1 and 2.2 at level A, AA or AAA, and reports each failure with the fix first. Like every automated tool it finds a subset of accessibility problems — roughly a third of the success criteria can be tested automatically at all. It cannot tell you a page is accessible, and nothing it produces is a conformance claim. The guide to VPATs and ACRs goes into what that means in practice.
It means nothing automatable failed, which is not the same thing. The criteria that matter most — whether alt text is meaningful, whether focus order makes sense, whether an interaction works with a screen reader — still need a person. Mend is deliberately built not to imply otherwise: a run with no failures is reported as a run with no detected failures.
You can generate a VPAT 2.5-format report covering WCAG 2.2 Level A and AA from your stored audits, on demand, from the VPAT page. It is framed throughout as an automated assessment, because that is what it is — a credible ACR needs manual evaluation as well, and the report says so rather than letting a reader assume otherwise.
Two ways. Generate an account key on your account page, paste it into the extension's settings under “Save audits to my dashboard”, and each run you save lands here. Or set up a monitor, and Mend audits the page on a schedule without you being at the keyboard.
Yes, on Pro. You give a monitor an ordered sign-in flow — go to, type, click, wait — either by building the steps by hand or by recording them once in a live browser, and Mend replays it before each scan. Credentials go into a per-account vault that is write-only: Mend can use a stored secret but can never show it back to you or to us. If a flow lands back on a sign-in page, or if a credential turns up anywhere in a scan's output, the run is thrown away rather than saved. The full explanation is in monitoring a page behind a login.
The extension is free, with no account and no limits. A free account adds a dashboard with 30 days of history and up to 200 saved audits. Pro raises that to two years and 50,000 audits, and is what unlocks monitoring pages behind a login. Full detail is on the pricing page.
Your account page will download everything stored for you as JSON, on any plan. The same page deletes all synced audits, or the whole account, immediately and permanently. What we hold and why is set out in the privacy policy.
From the billing portal, linked on your account page — invoices, card changes and cancellation all live there. Cancelling leaves Pro active until the end of the period you've already paid for, then the account returns to Free.