The browser extension
Running an audit on the page you are looking at, what the panel can see that a URL scanner cannot, and how connecting an account syncs results to your dashboard without putting the scan itself behind a plan.
Guides
Docs
How every part of Mend works, and plain-language accessibility documentation written to be useful rather than alarming. No scare tactics, no compliance theatre — just what the terms mean, what the product actually does, and what is really being asked of you.
Available guides
Reading your dashboard
What a pile of audits tells you that one audit does not — filtering by page and severity, sharing a filtered view as a link, reading the trend honestly, and why the per-rule pages are the ones to work from.
Monitoring a page over time
How a monitor works: choosing how often it runs, why the run time moves, auditing several pages in one flow, running on demand, pausing without losing history, and what a failed run does and does not mean.
Monitoring a page behind a login
How Mend signs in before it audits — what a sign-in flow is, recording one instead of writing it, how stored credentials are encrypted and write-only, and what Mend refuses to do with them, including never storing an audit of your login page.
Email alerts
When a broken monitor emails you, why a one-off timeout is deliberately allowed to pass in silence, the three per-monitor settings, and how to send alerts to a team address that has no Mend account of its own.
Slack notifications
Posting every run into a channel: adding an incoming webhook, all ten fields the message can carry and which five appear only when something failed, what happens when a post fails, and how to disconnect.
Sending audits from CI
How to post accessibility results to your dashboard from a build or a script — creating and revoking API keys, the one endpoint that accepts them, every field it takes, the caps and rate limits, and what each response code means.
Generating a conformance report
Turning the audits you already have into a downloadable ACR: which run of each page is used, how every WCAG 2.2 A/AA row is decided, and why “Supports” in a generated report means less than it looks like it does.
VPATs and ACRs
What a VPAT document and an Accessibility Conformance Report actually are, who asks you for one, how to read one you have been sent, and what producing one honestly involves.
Accessibility laws and legal compliance
A plain-language tour of the rules that reference web accessibility — the ADA, Section 508, the European Accessibility Act, EN 301 549, and the UK's Equality Act — and how they relate to WCAG. Not legal advice.
Plans and limits
What Free and Pro actually differ on — stored audits, history, API keys, ingest rate and authenticated monitoring — what happens when you reach a limit, and what changes if you cancel.
Exporting and deleting your data
Downloading everything stored for your account as JSON, deleting your synced audits while keeping the account, and closing the account entirely — including what each one cannot undo.
What these guides will not tell you
No automated tool — Mend included — can make a site accessible or certify it as compliant. Automated checks catch a meaningful slice of issues quickly and repeatably; the rest needs a person. Anywhere these guides describe conformance, they say plainly which part a scanner can answer and which part it cannot.