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: Saving scans

What do the results show?

A saved scan opens in your browser, where you can work through it and recheck what you've fixed. The sections after that cover the fix suggestions, what still needs a person, and how much of WCAG a scan can cover.

Every scan is saved in its own folder, named after the site and the time, inside magnacoda-scans in your Documents folder, wherever you start magnacoda:

magnacoda-scans/example.com_20261010-153012/
    checklist.md     the Markdown checklist
    results.json     everything the scan found, as JSON
    images/          screenshots of the page's images, shown in the checklist

A scan of both screens, and the dark-mode check, are part of the same checklist and results file. After a scan, magnacoda says briefly what it found, where it saved it, and what to type next; the full findings are on the review page (add --show-findings to see them in the terminal too). To save every scan somewhere else, set folder = under [scan] in preferences.ini; for one scan, add --scans-dir PATH. -o FILE writes a copy of the results at a name of your own, such as for CI.

Screenshots of images. A scan also photographs the page's images (up to 30), including SVG and canvas drawings, so you can compare each picture with its text alternative in the checklist. The screenshots stay on your computer and are never sent to the AI tiers.

When magnacoda creates the scans folder it also puts a .gitignore containing * inside it, so any git project ignores your saved scans without you editing its own .gitignore (a folder that already existed is left exactly as it was). Saved scans can include snippets and screenshots of the scanned pages, including pages behind a login if you scanned with --cookie, so keep them out of version control unless you mean to share them.