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: Fix suggestions
Every finding gets a fix suggestion. Without AI, they come from offline templates, one per rule, so every finding has one. With --ai explain or --ai semantic, the top 10 findings get context-specific, Claude-written corrected snippets instead, bundled into the same AI call at no extra cost; the rest keep the offline ones.
Findings that need the exact same fix (several elements sharing one CSS class, for example) are combined into one entry rather than repeated for each element.
Where the CSS is set. For problems a CSS property causes (a link's underline removed, a text color with too little contrast, the focus outline removed, text clipped by a fixed height, a small target), the checklist, the review page and the terminal also say which rule sets it, as the Styles panel of Chrome's DevTools would, for example "set by .entry a { text-decoration: none } in /css/site.css, line 12." When the stylesheet has a source map, as is usual on local development servers, it also names the file you edit ("from src/_links.scss, line 5, by its source map"). A rule in a <style> element, in the element's own style attribute, added by a script, or that is a single class on the element (perhaps a utility class, as in Tailwind) is named as such. This needs Chromium, the default browser; with Firefox the fixes are shown without it. The CSS found is saved with the scan, like the HTML snippets, and isn't sent to the AI tiers.
A rule without a template of its own gets axe-core's description of the rule and two places to read more: the rule's page at Deque University ("axe-core rule") and the W3C's Understanding page for each WCAG criterion it's about.
Top-10 ranking
The 10 findings that get explanations (and, with AI, fixes written for them) are picked in a fixed order:
- Severity:
critical > serious > moderate > minor - WCAG level: A before AA
- How many elements it affects, most first
- Where it first appears on the page, as the final tiebreak
Findings from the semantic tier carry a severity and level too, so they're ranked the same way as axe-core's.