Radix UI vs Konform
Accessible components with RGAA 4 docs
Radix UI is genuinely accessible. But it has zero RGAA 4.1.2 documentation, no audit-ready reports, and no EU compliance framing. For teams facing EAA 2025 or RGAA audits, that gap is critical.
Methodology: This page is based on publicly available sources — radix-ui.com, ui.shadcn.com, and their GitHub repositories — as of April 2026. All claims about Radix UI and shadcn/ui are sourced from their public websites and docs.
Feature comparison
✅ Confirmed from public sources · ❌ Not available or not addressed
| Dimension | Konform | Radix / shadcn |
|---|---|---|
| WCAG 2.2 AA implementation | Strong — documented per component | Strong — excellent WAI-ARIA primitives |
| RGAA 4.1.2 documentation per component | Included — criterion mapping per component | None — no RGAA documentation whatsoever |
| Audit-ready compliance reports | Per component — structured for auditors | None — no audit documentation |
| EAA 2025 framing | EU compliance-focused from the ground up | None — no EU regulatory context |
| EN 301 549 references | Included — v3.2.1 clause mapping per component | None — not referenced |
| French public sector ready | Designed for RGAA-required contexts | Not addressed — no French regulatory context |
| Pricing | €149/year — compliance docs stay current as standards evolve | Free / open source |
Radix UI / shadcn data sourced from radix-ui.com and ui.shadcn.com (April 2026). Radix UI is WCAG-compliant — this comparison is about compliance documentation and EU regulatory framing, not implementation quality.
What's missing from Radix for RGAA compliance
Radix UI delivers excellent accessibility primitives. The gap is not in what it implements — it's in what it documents. For EU teams facing audits, the documentation is the deliverable.
No RGAA criterion numbers in documentation
Radix docs explain ARIA patterns clearly, but never reference RGAA 4.1.2 criteria (e.g. Critère 11.1, 11.2). Auditors need these mappings explicitly.
No per-criterion testing guidelines in French
RGAA audits require testing against French-language criteria. There are no French testing guidelines for Radix components in any official or community resource.
No audit statement templates
RGAA compliance requires a formal Déclaration d'Accessibilité. Radix provides no templates or starting points for this mandatory document.
No EN 301 549 v3.2.1 mapping
The European Accessibility Act references EN 301 549. Radix has no documented mapping between its components and EN 301 549 clauses.
No French regulatory context
There is no guidance in Radix or shadcn docs about which French laws apply, which organisations are required to comply, or what the EAA 2025 timeline means in practice.
When you should use Radix / shadcn
Radix UI is genuinely excellent at accessibility primitives — WAI-ARIA patterns, keyboard navigation, focus management. shadcn/ui built on top of it is an outstanding developer experience. These tools are the right choice in many contexts.
- Teams building products without French or EU regulatory requirements
- Products targeting the US market primarily
- Open source projects where WCAG compliance is sufficient
- Teams who want to own their component code (shadcn copy-paste model)
When you should use Konform
Konform is designed for teams that need to demonstrate compliance — not just implement it. If your product will be audited against RGAA 4.1.2 or EAA 2025, the documentation layer is as important as the implementation.
- Teams in France or the EU subject to RGAA 4.1.2 or EAA 2025 obligations
- Agencies doing RGAA audits for clients who need documented component-level evidence
- Companies with €250M+ annual revenue in France (EAA mandatory from June 2025)
- Public sector teams and any organisation delivering digital public services
Ready to evaluate
RGAA compliance documentation included
Konform ships accessible React components with WCAG 2.2 AA, RGAA 4.1.2, and EN 301 549 documentation per component. Or start with the free RGAA component checklist.
Related resources
Continue your accessibility component research
compare Konform vs AlignUI for EAA 2025 compliance
See how a design-first React kit compares when EU regulatory documentation becomes mandatory.
compare Konform vs DSFR for RGAA compliance
Review the French public-sector benchmark for teams evaluating RGAA requirements.
free RGAA audit tools and contrast checker
Use the free RGAA checklist to catch missing documentation and component-level issues early.
RGAA 4 guide for React components and ARIA patterns
Go deeper on the React implementation details that matter during French accessibility audits.