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: Reviewing and rechecking

review lists the scans in your scans folder (or review FOLDER for another one), newest first, with how far along each checklist is. Pick one by number and it opens in your browser, in one tab:

  • The findings, open at the start: what the scan found, counts by severity, the failing rules and where they are, the top 10 explained and the suggested fixes, with severity colors.
  • The checklist, below them, with each page element's screenshot and a real checkbox to tick. Ticking saves straight into the scan's checklist.md, so the same ticks show up in a Markdown editor, and the other way round.
  • For a scan with several variants, links at the top switch between them (Desktop · light, Mobile · dark and so on); each has its own ticks.

Besides problems, the review page also lists Passed checks (rules axe-core evaluated that found no violation, ordered by WCAG success criterion) and Needs manual review (what axe-core couldn't decide, with the element and the reason, such as text over a background image), and ends with how many rules did not apply. The results file has them too (passed, needs_review, inapplicable_count), and --show-findings prints them in the terminal.

Press the page's Done button when you've finished (or Ctrl+C in the terminal). Where there's no browser (over SSH, for example), or with review --no-browser, the checklist opens in the help viewer instead. There you can read it but not tick items; for that, use the review page or a Markdown editor (see Ticking items off, below).

How the review page stays private: it is served by a small web server that magnacoda runs on your own computer only while you review (Python's built-in one, so nothing extra is installed). It listens only on 127.0.0.1, every address includes a new random secret, and requests from other websites are refused, so nothing else can read your scan or tick boxes in your files. The page itself passes magnacoda's own scan at Level AAA, in light and dark.

Rechecking your fixes. Once you've fixed some problems, recheck (or the Recheck fixes button on the review page) tests just the scan's Fix items again, on the same page with the same settings, in a few seconds, so there's no need to wait for a whole new scan. The saved checklist is updated in place, with confirmed fixes ticked and problems still there unticked, each with a dated note, and it ends with a summary such as "4 of 6 problems fixed; 2 still fail." A recheck doesn't look for new problems, so scan the page again before release. It also leaves the AI's suggestions (from --ai semantic) as they are, for you to judge. Behind a login, it uses the scan's saved login file (--storage-state), or the --cookie or --extra-http-header you give it.

To recheck one scan without choosing, give its folder: recheck magnacoda-scans/example.com_20261101-0930. A scan ends by saying where it was saved. A script or an AI agent must name the scan this way, since there's no one to pick from the list. It can also recheck each scan only three times, so an agent can't keep going round in circles; after that, it's told to stop and report to you. Your own rechecks aren't limited. To change the number, edit limit under [recheck] in preferences.ini (0 turns the limit off). A new scan of the page starts the count again.

Ticking items off works in the review page or in any Markdown editor (Typora, VS Code, Obsidian and so on), since checklist.md is the record. A checklist also pastes straight into a GitLab or GitHub issue, where the boxes stay tickable. A repeat scan keeps your work. When you save a new scan of the same page, what a person had checked in the previous scan comes already ticked, marked with that scan's date, while problems found again start unticked.