Accessibility Badge for Your Website, Compared

A badge on a website is a small mark that says something about the site behind it. Badges differ in what they say, and the difference matters. Some badges show that a site is monitored on a schedule, with dated reports behind the mark. Some badges show only that a scan ran once, on one date, on one page. Some badges are simply images a site owner adds by hand, with nothing behind them at all. Before displaying any badge, ask what it stands for, what backs it, and what happens when the site changes.

What a monitoring badge stands for

A monitoring badge is tied to an ongoing plan. The site is scanned on a schedule, problems are fixed, and the badge reflects the current state of that work, not a single good day. Axeazy's paid plans include a badge: Starter includes a badge for one site, and the Agency tier includes a white label portal, reports and badge, bulk scanning, and per client risk scoring for up to ten client sites. The badge sits beside a dated record: every scan and fix is recorded with a date and time, and reports can be exported as a PDF. A visitor who asks what the badge means can be shown a report with dates, not only a mark.

A monitoring badge is only as honest as its monitoring. Ask which pages the plan covers, how often checks run, and what happens to the badge when new problems appear. A badge that stays up while a checkout form breaks is worse than no badge, because it tells visitors the site is looked after when it is not. A good monitoring badge is backed by weekly checks, a named owner for alerts, and a report a visitor or a client can read.

What a scan badge stands for

A scan badge shows that a check ran, usually once, on a set of pages, on a stated date. It is a snapshot, not a promise about tomorrow. A scan badge has value when it names its scope and date: which pages were scanned, against what standard, and when. Axeazy's scan runs 98 automated checks against WCAG 2.2 AA, grouped into 14 categories. A badge that says a scan ran, with that scope and date behind it, is a fair statement. A badge that says more than the scan showed is not.

Free checkers illustrate the point well. WAVE, the free suite from WebAIM, reports problems on a page and does not fix code, and it gives no approval or certification badges. Its own guidance says a clean report does not mean a page is accessible, and only a person can determine true accessibility. That honesty is the standard to hold any badge to: a badge should say what was checked, and no more.

Badges that say nothing

A badge added by hand, with no scan, no monitoring, and no report behind it, says nothing, however good it looks. It can also mislead a visitor who takes it as a statement about the site. Do not display a badge you cannot back with a dated report. If a vendor offers a badge with no monitoring plan behind it, ask what the badge is tied to, and what happens when the site changes. If the answer is nothing, leave the badge off and spend the effort on a scan and a fix list instead.

How to display a badge honestly

Put the badge where a visitor can find the story behind it: link it to a page that names the standard tested, the pages covered, the date of the last scan, and a way to report a problem. Keep the badge current: if monitoring stops, take the badge down until it resumes. If a template changes, rescan before the badge goes back up. For agencies, a white label badge on a client site should carry the same discipline: the client reads the badge as a statement about their site, so the agency should be able to show the client the dated reports behind it. The details of Axeazy's agency plan sit on Axeazy's agency page, and the plan figures sit on Axeazy's pricing page: Agency at about $199 a month or $1,799 a year, with paid prices shown at checkout.

Never use a badge to imply a result it does not show. A badge does not say a site is free of barriers, and it does not say a site will stay as it is after the next update. Say what the badge shows: a site that is scanned, fixed, and monitored on a schedule, with dated reports behind the mark. That statement is checkable, and a checkable statement is worth more than a grand one.

Related reading

For the monitoring plan behind a badge, read what to look for in accessibility monitoring, and for weekly reports, read weekly accessibility reports for your site. For the buyer checklist, read accessibility tool buyer checklist.

• how to add an accessibility statement to your site

FAQ

Should a small site display a badge?

Only if monitoring is running and reports are dated. A badge with no monitoring behind it adds risk without adding value. A badge backed by weekly scans and dated reports is a fair signal to visitors and clients.

Does a badge help with a demand letter?

A badge alone does not. A dated record of scans, fixes, and rescans does, because it shows work over time. Keep the badge and the record together, and treat the record as the important half.

What should a badge link to?

A page that names the standard tested, the pages covered, the date of the last scan, and a way to report a problem. A badge that links nowhere asks visitors to trust a mark with no story behind it.

Last checked: October 31, 2026 Sources: W3C WCAG 2.2; WAVE tools page; Axeazy capabilities, pricing, and agency pages.

Start with Axeazy's free scan to see a dated report, then decide whether a badge backed by that kind of record fits your site.