auditmysitev2.0.2

CASOON Open Source

Accessibility audits of the rendered page.

auditmysite loads each page in Chrome, reads Chrome's own accessibility tree over the DevTools Protocol and checks it against WCAG 2.2 AA. One binary, JSON for automation, PDF reports in German and English.

curl -fsSL https://raw.githubusercontent.com/casoon/auditmysite/main/install.sh | bash
cargo install auditmysite
MITJSON + PDFWCAG 2.2 AAmacOS · Linux · Windows
auditmysite 1.7.0 on casoon.de
$ auditmysite https://www.casoon.de/ \
> --format table --no-sitemap-suggest \
> --lang en --request-mode browser

    _             _ _ _   __  __       ____  _ _
   / \  _   _  __| (_) |_|  \/  |_   _/ ___|(_) |_ ___
  / _ \| | | |/ _` | | __| |\/| | | | \___ \| | __/ _ \
 / ___ \ |_| | (_| | | |_| |  | | |_| |___) | | ||  __/
/_/   \_\__,_|\__,_|_|\__|_|  |_|\__, |____/|_|\__\___|
                                 |___/

  AuditMySite v1.7.0 - WCAG 2.2 AA Accessibility Checker

Checking: https://www.casoon.de/
Auditing: https://www.casoon.de/
✔ Website Health Report

  Accessibility: 100
  Combined technical: 93
  Grade: A
  Certificate: EXCELLENT
  Violations: 0
  Duration: 9561ms

PASS
WCAG 2.2 A/AA success criteria in scope
55
of them covered by automated checks
30
listed for manual review, never silently passed
25
prebuilt release targets (macOS arm64, Linux x64/arm64, Windows x64)
4

What it does

Three ways to a report

Common flags

What to audit

  • Sitemap, as one batch report-s<sitemap-url>
  • URL list from a file-u<file>
  • Same-domain crawl from the URL--crawl
  • Cap the number of pages-m<num>

What to check

  • Add performance, SEO, security, mobile--full
  • WCAG level (AAA is incomplete)-lA|AA|AAA

What to write

  • Report format-fjson|pdf|table
  • Output file-o<file>
  • Report language (default en)--langen|de
  • One JSON per page plus findings.jsonl--per-page-reports-fjson

Quickstart

Install the binary, make sure a Chrome is available, point it at a URL. The documentation covers batch modes, reports and CI.

  1. Install with the installer script, cargo install auditmysite or a release binary.
  2. Run auditmysite browser detect. Without a system Chrome, auditmysite browser install fetches Chrome for Testing.
  3. Run auditmysite <url> for a report, or -f json for automation.
shellShell
# check which browser auditmysite will use
auditmysite browser detect

# full single-page audit: a table in the terminal, nothing written
auditmysite https://example.com

# machine-readable, for CI
auditmysite https://example.com -f json -o report.json --quiet

# domain-wide, aggregated
auditmysite --sitemap https://example.com/sitemap.xml --max-pages 20

Results from real audits

RankingLab: start page with public accessibility rankings
rankinglab.casoon.dev: public rankings produced with auditmysite, of publicly reachable pages. Captured on 2026-09-16.

What an automated audit does not do

Automated checking covers part of accessibility. The rest needs human judgement, and the report says so.

Not every criterion can be automated
Keyboard traps, timed content and captions cannot be verified reliably by machine. They are flagged not_testable in the JSON and listed in the report's audit scope, never silently passed.
No accessibility statement
The EN 301 549 appendix is a technical building block for a statement written by people. It is not a statement, not legal advice and not a confirmation of conformity under BFSG or BITV 2.0.
Heuristic modules are tendencies
Experimental indicators such as UX or AI visibility are off by default; they are estimates, not measurements, and no statement of conformity.
AAA is not fully implemented
-l AAA exists, but coverage of level AAA is still incomplete.
A browser has to be present
Without Chrome or Chromium the run stops with an error. A browser is only downloaded on request, with auditmysite browser install.
Linked PDF documents are not checked
Rendered web pages are audited. Linked or embedded PDF files are a documented non-goal.

New in v2.0.2

Changelog →

Frequently asked questions

Does auditmysite download or install a browser automatically?

No. It requires Chrome, Chromium, or a managed browser to already be present and exits with an error if none is found. auditmysite browser install fetches Chrome for Testing, but only when you run it yourself.

Is the PDF report an accessibility statement I can publish?

No. The EN 301 549 appendix and the JSON findings are a technical building block for a statement a person writes; the report explicitly does not claim conformance under BFSG or BITV 2.0.

Does 100% automated pass mean the page is fully WCAG 2.2 AA compliant?

No. Of the 55 WCAG 2.2 A/AA success criteria, only 29 are counted as automated, and a criterion counts there only if a rule can actually report a violation. The other 26 are listed as requiring manual review, never silently marked as passed.

Where do the WCAG rule ids and checks come from?

From the barrierlab crates (a11y-rules, a11y-dom, accname, html-conform, and related crates), a shared Rust monorepo also used by astro-post-audit and LiveAudit, so the same rule id means the same thing across all three tools. Rule ids stay stable across auditmysite releases, with renames documented when a collision is fixed.

Can it audit more than one page at a time?

Yes. Point it at a sitemap, a URL file, or a seed URL with --crawl, and it writes one aggregated batch report with averages, ranking, and recurring issues across pages. --per-page-reports -f json switches that same batch run to one JSON file per page plus a flat findings.jsonl instead.