Pandus Accessibility gives an assistant a free reference of axe-core accessibility rules and WCAG 2.2 criteria, with plain-language fixes for ecommerce…
What you can do
Search accessibility rule cards by keyword, axe rule id or WCAG success criterion
Explain a single axe-core rule: what is wrong, who is affected, how to fix it in code and on Shopify, WooCommerce, PrestaShop or Shoptet, plus the WCAG 2.2 and EN 301 549 clauses
Explain a WCAG 2.2 level A or AA success criterion in plain words, with examples, manual test steps and what automated checks can and cannot catch
When to use it
Useful when someone needs to understand an accessibility issue, map it to WCAG or EN 301 549, or find concrete remediation steps for a storefront platform. The free rule reference works without any account.
Requirements
A remote streamable HTTP endpoint at pandus.online; no local install. The free rule reference needs no token. Site-specific features require an optional Authorization header carrying a Bearer API token from a Pandus Pro or Agency plan.
Before you install
The Authorization header carries a secret API token; keep it out of shared logs and transcripts. Without it only the free rule reference is available. Explanations are guidance, not a substitute for manual accessibility testing or legal compliance review.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/online.pandus%2Faccessibility/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Searches the Pandus library of accessibility rule cards (the axe-core rules Pandus checks, explained for business owners) by words, an axe rule id or a WCAG success criterion such as 1.4.3. Free, no API token needed.
Parametersqueryrequiredlocale
explain_rule
Explain an accessibility rule
Explains one accessibility rule (an axe-core rule id such as image-alt or color-contrast): what is wrong, why it matters for customers, who is affected, how to fix it in code and on Shopify, WooCommerce, PrestaShop or Shoptet, and the WCAG 2.2 / EN 301 549 clauses. Free, no API token needed.
Parametersrulerequiredlocaleplatform
explain_wcag_criterion
Explain a WCAG criterion
Explains a WCAG 2.2 level A or AA success criterion (for example 2.4.7) in plain words: what it asks, examples, how to test it by hand and what automated checks can and cannot find. Free, no API token needed.
Parameterslocalecriterionrequired
Version history
1
v1.0.0LatestOct 20, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.