Scan for web accessibility issues.
Learn to fix them.

magnacoda

Welcome

magnacoda™ is an accessibility scanner for WCAG, the Web Content Accessibility Guidelines, that you run from your terminal. It's built for developers and content managers who want to understand and fix accessibility problems, not just list them.

These are screens from magnacoda, from a scan of a sample page.

Menu

magnacoda » menu

magnacoda accessibility scanner - type a command, or exit to leave.
Commands: wizard · scan · help · setup · review · update · about · menu
Add-on commands: favorites

    Tip: Type menu any time to see the commands, or clear
    for a fresh page.

magnacoda »

The menu, from magnacoda in a terminal.

Scan

magnacoda » scan https://unrealbakeshop.example/

Ctrl+C or q cancels at any time.

The defaults: WCAG 2.2 AA, a desktop screen, light and dark mode, no AI.
You can type: options (such as --option), defaults, help. Enter cancels.
Options » defaults

 Scanning https://unrealbakeshop.example/ - 5 s so far

A scan of the sample page, from magnacoda in a terminal.

Results

magnacoda » scan https://unrealbakeshop.example/

Ctrl+C or q cancels at any time.

The defaults: WCAG 2.2 AA, a desktop screen, light and dark mode, no AI.
You can type: options (such as --option), defaults, help. Enter cancels.
Options » defaults


Tested on desktop, in light mode (the page looks the same in dark mode).
Found 12 problems on 12 elements (2 critical, 9 serious, 1 moderate), and
49 items to check.
The scan took 19 s.
Saved in ~/Documents/magnacoda-scans/unrealbakeshop.example_20261119-105414.

Type review to see them in your browser, and recheck once
you've fixed some.

magnacoda »

The scan's results, from magnacoda in a terminal.

Review

9. input ("Your email")

  • Fix 1.3.5 Identify Input Purpose (opens in a new tab) (AA) - It looks like it asks for the visitor's own email address, but has no autocomplete value, so browsers can't fill it in and assistive tools can't show what it's for (moderate; rule magnacoda/missing-autocomplete)
    • now: <input type="email" placeholder="Your email">
    • fix: Add autocomplete="email", if the field asks for the visitor's own details (for someone else's, such as a gift's recipient, leave it out).
    • e.g. <input type="email" placeholder="Your email" autocomplete="email">
  • Checked: tick when you've looked at everything below that needs a person
  • Check 3.3.1 Error Identification (opens in a new tab) (A) - Submit invalid or empty input: errors must be shown in text and identify the field in error.
  • Check 3.3.3 Error Suggestion (opens in a new tab) (AA) - When an input error is detected and a fix is known, the message should suggest it.
  • Check 4.1.3 Status Messages (opens in a new tab) (AA) - Status messages (success, errors, result counts) must be announced via role=status/alert or live regions without moving focus.

One finding from the scan of the sample page, on the review page in your browser.

See the full review

Help

magnacoda - Help

magnacoda is a WCAG 2 accessibility scanner for developers and content
managers comfortable in a terminal. It explains what it finds and how to fix
it, so you can act on the results right away and learn as you go.

- Open a terminal and run magnacoda with no arguments to start an
  interactive shell. Let the wizard ask a few plain-language questions and
  build the scan for you. To learn how to open a terminal on your computer,
  type docs starting.
- Or scan a page directly from the command line with magnacoda scan URL
  [OPTIONS]. The URL can be short, such as example.com or localhost:3000:
  magnacoda fills in the rest.
- To use the AI tiers you can provide your own Anthropic API key (setup
  can save one for you), or use Claude Code if it is installed and logged
  into your Claude subscription.
- AI works with magnacoda both ways: your AI coding agent can run it, and
  it can use AI itself. To see both in one round of work on a page, type

1/14 overview | g go | o open | c colors | ← back | → next | Esc quit
Scroll: ↑ ↓ | lines 1-16 of 25

The help, from magnacoda in a terminal. You can read all of it in Read the docs.

Setup

magnacoda » setup

Ctrl+C or q cancels at any time.
Chromium is already installed.

A shortcut opens magnacoda in a terminal window, from your app menu or
desktop.
Add a magnacoda shortcut to (menu, desktop, both, skip) [skip] »


AI tiers (optional; magnacoda works fine without them):

Claude Code is installed, so the AI tiers can use your Claude plan (such as
Pro or Max) instead of an Anthropic API key, which the API bills per use.
Use your Claude plan for the AI tiers? [Y/n] »

Setup, from magnacoda in a terminal.

magnacoda docs

Manual: Scan options

Every option for scan, with more than help scan has room for. Type them after the address: scan example.com --screen both in the shell, or magnacoda scan example.com --screen both from the command line. The rarely needed ones are in Advanced scan options.

With only an address, or none. scan on its own asks for the page, and you can type options after it, as in example.com --screen mobile. At that first question, type recent (or fav, with the favorites add-on) to pick an earlier scan by number, wizard to choose step by step, or help for the options. A group of more than 12 entries isn't printed; type view to read it in the viewer, then its number. Enter cancels. With only a page, typed there or as scan example.com, it shows the defaults and asks for options. Type them, or defaults, or press Enter to cancel, so nothing runs until you answer. If you've scanned the page before with other settings, it says so, and recent or fav lists that page's saved scans to pick by number. q, clear or Ctrl+C cancels at any question. There's no question when you give an option, with -y, or in scripts and CI; to turn it off, set confirm = off under [scan] in preferences.ini.

The address can be short, such as example.com or localhost:3000; see URL rules.

What to check

  • --level [A|AA|AAA]: the WCAG conformance level. Default: AA, the one most laws and organizations ask for.
  • --wcag-version [2.0|2.1|2.2]: the WCAG version to test against. Default: 2.2. Some laws and contracts still name 2.1.
  • --screen [desktop|mobile|both]: scan as a desktop (the default) or as a phone. Mobile uses a Pixel 8 Pro profile: small screen, touch, mobile user-agent. both scans desktop, then mobile, into one scan, marking problems found on only one; see Mobile and desktop. Dark mode is checked on every scan, in seconds; see Light and dark mode.
  • --quick, --thorough: --quick leaves out the slowest tests that use the page (watching for moving content, hovering, clicking, single keys), about 10 seconds a scan, and the checklist leaves those checks to you. --thorough runs them. Default: the quick setting under [scan] in preferences.ini (off).

AI reasoning

The AI tiers need your own Anthropic API key, or Claude Code logged in to your Claude subscription; see AI tiers.

  • --ai [off|explain|semantic]: off, no AI (axe-core and magnacoda's own tests, with offline fix suggestions). explain, plain-language explanations and AI-written fixes for the top 10 findings. semantic, the same, and the AI also reads the page's alt text, headings and link text to judge whether they make sense, which rule checks can't. Default: off.
  • -y, --yes: accept the AI data-sharing question in advance, for scripts.

Output and CI

Every scan is saved in its own folder in magnacoda-scans: the checklist (checklist.md), the results file (results.json) and the page's images; see Saving scans. A scan ends with a short summary; the findings are on the review page (review).

  • --show-findings: also show the full findings in the terminal.
  • -o, --output PATH: also write the full results as JSON to this file, for CI; an existing file is replaced. -o - prints the JSON, for a program to read.
  • --fail-on [none|minor|moderate|serious|critical]: exit with code 1 if the scan finds a problem at or above this severity, so a CI build can fail on it. Errors (a page that won't load, a bad option) exit with code 2, and Ctrl+C with 130. Default: serious. See How do I use it with CI, scripts and AI agents?
  • -v, --verbose: more detail; repeat for more.

Colors are turned off by the standard NO_COLOR environment variable.

Pages behind a login

  • --storage-state PATH: start from a saved Playwright login session (a storage-state JSON file).
  • --cookie NAME=VALUE: set a cookie before loading the page. Repeat for several.
  • --extra-http-header KEY=VALUE: send an extra HTTP header with every request. Repeat for several.

Cookie and header values are never stored. With either one, magnacoda doesn't fall back to http://, so they never cross the network unencrypted.

Pages that need help to load

  • --wait-for-selector TEXT: wait until this CSS selector appears before scanning, for apps that load their content late.
  • --ignore-https-errors: continue past invalid or self-signed HTTPS certificates, for local development servers.

For a page that's just slow, see --wait in Advanced scan options.