Accessibility, right on time
Ship accessible UI at the speed of AI coding.
Malimbe plugs into your agentic coding tool to help it build accessible components, review your work before it's hosted, and govern a design system โ measured against WCAG 2.2 Level A and AA.
Start the 30-day evaluation See what it doesBuilt by a 15-year accessibility practitioner ยท Works with Claude Code, Codex, Cursor, GitHub Copilot in VS Code ยท Assists and gates โ never claims to guarantee compliance.
What it does
Three jobs, one tool.
Malimbe is an MCP server plus encoded expertise. It rides inside the coding agent you already use, so accessibility happens where the code is written โ not in a scan after the fact.
Build
Describe a component in plain words. Malimbe maps it to the correct ARIA pattern and writes a prompt carrying the full keyboard and focus contract โ the parts agents usually get wrong.
Review
Audit a live site, an internal URL, a repo, or code that isn't hosted yet โ served locally and scanned for real. Findings ranked by how badly they block a user, not raw counts. Each audit also names what the site is built on, so your team knows where fixes belong.
Govern
A release gate with enforced provenance, a component manifest that remembers verdicts and expires exceptions, and consistency checks across a whole design system.
New in 0.5.0: know where each fix goes
A list of failures only helps if you know whose code to change. Malimbe now tells you what a site is built on โ its content platform, framework, component libraries, and common accessibility overlays โ and shows the evidence for each. Then it tells you where each fix has to happen:
- In your own markup, when your team wrote it.
- In a platform template, when a platform like SharePoint or Liferay generates the code.
- In a custom component, when a third-party widget, such as a carousel, needs replacing.
- With the vendor, when an embedded tool controls it.
When a failure comes from a specific widget or platform control, Malimbe points to it. When it can't tell, it says so instead of guessing. It also warns you about known platforms past their end of support, such as SharePoint Server 2016 and 2019.
New in 0.6.0: install from the directories you already use
Malimbe now installs from npm, as a Claude Code plugin, and as a Claude Desktop bundle. The 30-day trial starts the first time it runs. After the trial, Malimbe needs a paid validation code to run. The Skills now come from the Malimbe server itself, so your agent always reads the version that matches your install.
How it fits
One line in your editor config.
Malimbe is model- and platform-agnostic. The same package serves every agentic surface through the standard MCP protocol โ no lock-in to one assistant.
- Ships pre-built. Install from npm, as a Claude Code plugin, or as a Claude Desktop bundle
- Finds your installed Chrome or Edge automatically; no forced downloads, no mysterious hangs
malimbeba doctorhands you your exact, ready-to-paste editor config โ no path-guessing- Static checks always work, even with no browser present
Install where you already work
- Claude Code:
/plugin marketplace add beyond-a11y/malimbeba-releases, then/plugin install malimbe@beyond-a11y - Claude Desktop: download
malimbeba-0.6.0.mcpbfrom the 0.6.0 beta release and double-click it - VS Code, Cursor and other MCP clients: run
npx -y malimbeba@0.6.0as a stdio MCP server. It needs Node.js 18.17 or later - Prefer a global install?
npm install -g malimbeba, thenmalimbeba doctorprints your MCP config with the correct path already filled in
Why Malimbe
Honest about what a machine can and can't verify.
Most accessibility tooling either flags defects after the fact or overpromises "one-click compliance." Malimbe does neither. It works where code is generated, enforces evidence, and is candid about its limits.
Automated checks are necessary, not sufficient. Malimbe tells you what it verified, what it couldn't, and what still needs a human.
The provenance gate
Every release verdict is tied to a named, auditable artifact โ a deployed URL, a package version, a build SHA. Pasted or unverifiable code can't pass the automated gate. It's a direct, enforced answer to the fair question "can I trust an AI to judge accessibility?"
Bring accessibility into your agentic workflow.
Start a free 30-day evaluation. Install from npm, GitHub or your editor's directory, with no account and no card. The 30 days start the first time Malimbe runs. To keep going after that, buy a validation code and activate it before the 30 days end.
Start the 30-day evaluation Ask about a licenseNo coding agent? Run malimbeba-ui after installing for a browser-only interface โ no AI agent or MCP client required.