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: Beyond axe-core: testing the page as people use it

axe-core reads the page as it is. Many WCAG criteria are about what happens when someone uses it: where the keyboard focus goes and whether it can be seen, what a form does when it's sent, whether the page still works zoomed in. So after axe-core's checks, magnacoda uses the page itself, in the same browser. It presses Tab through it, lays it out again zoomed in and with wider text spacing, sends its forms empty and changes their fields, hovers, clicks and presses single keys. Each test reports problems as Fix items under the element, with the change to make, and notes what went right on the element's Check items.

A test tries what it can, not everything a criterion asks, so the third column says what happens when it finds nothing: whether the criterion then counts as passed (with a short follow-up for what's left), or still needs a person.

WCAG criterion What magnacoda tests When it finds nothing
1.2.3, 1.2.5 Audio description whether each video has an audio description track a note for you
1.3.1 Info and Relationships radio buttons and checkboxes whose question has no name axe-core's result stands
1.3.5 Identify Input Purpose fields that look like the visitor's own details but have no autocomplete value notes for you
1.4.4 Resize Text the page at 200% zoom: text cut off passed, with a follow-up
1.4.10 Reflow the page at 320 px wide: elements that make it scroll sideways passed, with a follow-up
1.4.12 Text Spacing WCAG's text spacing: text cut off or spilling out passed, with a follow-up
1.4.13 Content on Hover or Focus tooltips and menus that vanish, can't be hovered, or don't close with Esc still needs a person
2.1.1 Keyboard controls only the mouse can use; custom controls Enter and Space don't work still needs a person
2.1.2 No Keyboard Trap Tab getting stuck passed, with a follow-up
2.1.4 Character Key Shortcuts single keys that do something with nothing focused a note for you
2.2.1 Timing Adjustable a page that moves on to another by itself after a delay (a timed redirect) still needs a person
2.2.2 Pause, Stop, Hide content moving by itself with no pause button still needs a person
2.4.1 Bypass Blocks whether the skip link moves the focus passed, if axe-core agrees
2.4.3 Focus Order where the focus jumps back up the page, and elements you can't see that Tab still reaches (such as a hidden spam-trap field) a note for you
2.4.7 Focus Visible focus that can't be seen passed, with a follow-up
2.4.11 Focus Not Obscured focus hidden under a banner or sticky header passed, with a follow-up
3.2.1 On Focus getting the focus alone loading a page, opening a window or moving the focus passed, with a follow-up
3.2.2 On Input changing a field doing the same passed, with a follow-up
3.3.1 Error Identification forms sent empty: error text missing, or not tied to its field notes for you
3.3.3 Error Suggestion the error messages, shown for you to judge notes for you
3.3.8 Accessible Authentication password fields that refuse pasting, or turn password managers away notes for you
4.1.2 Name, Role, Value expand and collapse buttons whose aria-expanded is missing or wrong still needs a person
4.1.3 Status Messages error messages screen readers aren't told about notes for you

Limits. The tests try typical use rather than everything. They don't fill in forms with real data, explore menus and dialogs once they're open, or see checks that happen on the server. A clean result means none of these problems were seen, so each criterion's follow-up says what's left for you.

Nothing is sent, and nothing changes on the site. While the page is tried, every request it makes is blocked, so a form that sends itself is noticed without being sent. The page changes only in your browser, after axe-core's checks.

Quick scans. Watching for moving content, hovering, clicking and pressing single keys add about 10 seconds a scan. --quick leaves them out, and the checklist then leaves those checks to you.