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: A full example with an AI agent

AI can work with magnacoda in both directions. Your AI coding agent can run magnacoda, and magnacoda can use AI itself for what the rule checks can't judge. Here is one round of work on a page, using both, with you deciding at the end.

  1. Your agent changes a page, such as a sign-up form, while your site runs on your own computer at localhost:3000.

  2. The agent scans the page with AI on.

    magnacoda scan localhost:3000 --ai semantic --yes --fail-on none -o -
    

    magnacoda tests the page, then asks the AI whether the alt text describes each image, whether each link's text makes sense on its own, and whether the headings outline the page. --yes gives your consent in advance, since the agent can't answer the question. -o - prints the results as JSON for the agent to read (a lone - means the screen rather than a file), and the scan's last lines say which folder it was saved in.

  3. The agent fixes what it can. Findings marked "source": "claude-semantic" came from the AI. They're suggestions, so a careful agent weighs them rather than taking each one as fact.

  4. The agent rechecks. magnacoda recheck with the scan's folder tests those problems again, in seconds, and ticks the confirmed fixes in the checklist. It leaves the AI's suggestions for you. With no person at the keyboard, each scan can be rechecked three times, so an agent can't go round in circles.

  5. You review. magnacoda review opens the checklist in your browser. There you see what the agent fixed, the AI's suggestions to accept or dismiss, and the checks only a person can make, such as whether the focus order makes sense.

  6. CI keeps it that way. CI scans run without AI unless you ask for it, so a build fails only on what the rule checks find (see GitLab CI and GitHub Actions).

To make this a habit, add these lines to your agent's instructions file (CLAUDE.md, AGENTS.md or similar):

After changing a page, run magnacoda scan localhost:3000 --ai semantic --yes --fail-on none -o - and fix what it finds. Then run magnacoda recheck with the scan's folder. Make at most two rounds of fixes. Then stop and tell me what's still failing, and what the scan says a person needs to check.

Each scan with --ai semantic makes two requests to the AI, which count toward your API key or your subscription (see Two ways to run the AI tiers). On a low-end device, such a scan of a one-page site takes about two minutes. Rechecks don't call the AI.