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.
Swipe sideways to see the whole screen.
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">
- now:
- 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.
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
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: Updates and news
Once a day, when you use magnacoda in a terminal, it quietly checks two places in the background: pypi.org, for a newer version of magnacoda (and of any add-ons published there), and news.magnacoda.dev, for news about magnacoda, such as a new feature or a known problem. If there's something new, your first shell of the day says so when it starts. A newer version is mentioned every day until you install it, and news for up to three days. news shows it, numbered: first what's new in a newer version, or in this one, then earlier versions and the news by date. news 2 opens the second item. update installs a newer version for you, showing first what's new in it. When one is waiting, leaving the shell offers it too, once a day.
What is sent: only an ordinary web request for a public file, the same as visiting the page in a browser (which shows your IP address to the site, as any connection does), naming your version of magnacoda (for example magnacoda/1.2.0). Nothing about you, your scans or the pages you scan is sent, and there's no tracking, with no ID and no cookies. Private add-ons are never looked up.
What is counted: how many times news.magnacoda.dev is checked each day, and from which versions. Each copy of magnacoda checks at most once a day, so that's roughly how many people use it that day, and how quickly they move to a new version. Only those daily totals are kept, not IP addresses. Turning the check off (below) leaves you out of the count.
What you'll notice: nothing, unless there's news. The check never delays the shell; if there's no connection, or a site doesn't answer, it silently tries again the next day. The daily check never runs in CI, in scripts, or when output is redirected (news and update check when you run them yourself, except in CI), and news never appears in saved scans.
Turning it off: set check = off under [news] in preferences.ini (see Settings), or set the environment variable MAGNACODA_NEWS=off. news then shows only what's new in this version and earlier ones, and update still checks when you run it, since you asked.
How update works: it shows the versions it found, what's new in them (read from magnacoda's repository on GitHub, the same ordinary request as above), and the exact commands it will run, and asks first. If you installed magnacoda with uv, pipx, or pip in a virtual environment, it runs them, then closes magnacoda so you can start the new version. If you had downloaded Chromium (with setup), it also downloads the one the new version needs, which is quick when nothing changed. On Windows, a running program can't replace itself, so the update opens in a new window and starts once magnacoda has closed. For any other kind of install, it shows the command to run yourself.