React Native A11y vs Axcess — Design Accessibility Evaluation
React Native A11y is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
React Native A11y is a plugin bundle for AI coding tools published by Artur Kalach. No marketplace we read lists it any more. Axcess — Design Accessibility Evaluation is an MCP server published by sicxz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace arturkalach/rn-a11y-skill | Removed on 2026-10-15 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | React Native A11yno longer listed · | Axcess — Design Accessibility Evaluation |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (axcess-mcp-server.fly.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/arturkalach/rn-a11y-skill | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of React Native A11y
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
WCAG 2.2 accessibility audit and fix for React, Next.js, Vue, Angular, Svelte, and HTML. Static scanner detecting 20+ violation types, contrast checker with suggest mode…
-
Design, implement, and verify accessible experiences against WCAG 2.1 and 2.2, including runtime keyboard and focus validation, accessible Markdown authoring, and accessibility…
-
WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design
-
WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design
-
React Native performance, Metro bundler optimization, FlatList/ScrollView guidance, Expo vs bare workflow decision matrix, and React Navigation patterns for Claude Code.
-
Use this agent when you need expert assistance with React Native development tasks including code...
What each says it does
React Native A11y
Diagnose and fix React Native accessibility (a11y / WCAG) problems and integrate the react-native-a11y package family.
Axcess — Design Accessibility Evaluation
Evaluates UI designs for WCAG accessibility issues automated scanners miss. Paid via x402 on Base.
How to run each
React Native A11y
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Axcess — Design Accessibility Evaluation As a remote MCP server
claude mcp add --transport http axcess https://axcess-mcp-server.fly.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Axcess — Design Accessibility Evaluation has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: React Native A11y · What it can do: Axcess — Design Accessibility Evaluation · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.