EN 301 549
EAA 2025 is a legal obligation
The European Accessibility Act requires digital products to meet EN 301 549 / WCAG 2.2 AA. Konform components are built with these standards as a first-class requirement — not a marketing claim.
Comparison · April 2026
Konform vs AlignUI
Both are React component libraries aimed at production teams. The key difference: Konform is built around documented EU accessibility compliance (WCAG 2.2 AA, RGAA 4.1.2, EN 301 549). AlignUI claims accessibility without specifying a standard or providing supporting documentation.
Methodology: This page is based on publicly available sources — alignui.com, the AlignUI v1.2 documentation, and the AlignUI GitHub repositories — as of April 2026. All claims about AlignUI are sourced from their public website and docs.
Feature comparison
✅ Confirmed from public sources · ⚠ Partial or inferred · — Not available or not addressed
| Dimension | Konform | AlignUI |
|---|---|---|
| Primary positioning | EU compliance-first: WCAG 2.2 AA + RGAA 4.1.2 + EN 301 549 | Pixel-perfect design system, Figma-first, rapid development |
| WCAG level specified | WCAG 2.2 AA — documented per component | "WCAG-compliant" — level unspecified |
| RGAA 4.1.2 | Documented per component | Not mentioned |
| EN 301 549 | Documented per component | Not mentioned |
| European Accessibility Act (EAA 2025) | Core design requirement | Not addressed |
| Dedicated accessibility documentation | Per-component guidelines with ARIA patterns, keyboard nav, anti-patterns, and test checklists | No dedicated a11y section — code props only |
| Audit trail / compliance reports | Structured component-level evaluation | Not available |
| Assistive technology testing notes | Included in component guidelines (NVDA, JAWS, VoiceOver) | Not documented |
| Stack | React + TypeScript | React + TypeScript + Tailwind CSS + Radix UI |
| Component model | npm package | Copy-paste (shadcn-style) |
| Figma file | Not included | Available (paid, synced with code) |
| Pricing model | Annual subscription — compliance stays current as standards evolve | $299–$399 one-time payment |
| Public sector / government use | Designed for RGAA-required contexts (French public sector, EU administrations) | No specific positioning |
AlignUI data sourced from alignui.com, pro.alignui.com, and github.com/alignui (April 2026). AlignUI's accessibility is noted as claimed but not substantiated with documentation in their public-facing materials.
For EU teams
Compliance isn't optional in Europe
Since June 2025, the European Accessibility Act (EAA) requires digital products to meet EN 301 549 — the harmonised EU standard that references WCAG 2.2 AA. French administrations are additionally required to comply with RGAA 4.1.2. Konform was designed around these constraints from day one.
RGAA 4.1.2
RGAA 4.1.2 for French public sector
French administrations and any organisation delivering public digital services must comply with RGAA 4.1.2. Konform provides per-component RGAA criterion mapping — something no US-first design system offers.
WCAG 2.2 AA
WCAG 2.2 AA documented, not assumed
Every Konform component ships with a WCAG 2.2 AA criterion table, ARIA implementation guide, keyboard navigation spec, and a validation checklist. You know exactly what you're deploying.
What “documented per component” means in practice
Every Konform component ships with a structured accessibility guide covering: applicable WCAG 2.2 criteria, RGAA 4.1.2 criterion mapping, EN 301 549 clause references, correct ARIA roles and attributes, keyboard navigation specification, known failure patterns, and a validation checklist. This is the documentation your accessibility auditor needs.
KonformButton — a11y guide
✓ WCAG 2.2 AA — SC 4.1.2, 2.4.11
✓ RGAA 4.1.2 — C11.1, C11.2
✓ EN 301 549 — 9.4.1.2
✓ role="button" · aria-disabled
✓ Keyboard: Enter / Space
✓ 8 failure patterns listed
Where AlignUI leads
A fair comparison acknowledges genuine strengths on both sides.
- Component volume: AlignUI offers 40+ free components and 180+ PRO components. Konform's catalogue is more focused — prioritising depth of compliance documentation over breadth.
- Figma integration: AlignUI includes a paid Figma library synchronised with the codebase, which bridges designer–developer workflows. Konform does not currently include a Figma file.
- Copy-paste model: AlignUI's copy-paste approach (no npm dependency) gives teams full ownership of component code. Konform ships as an npm package.
- Sectoral templates: AlignUI provides multi-page templates for common verticals (AI, HR, Finance). Konform focuses on individual accessible components rather than pre-built templates.
Summary
Choose Konform if
- You need documented WCAG 2.2 AA / RGAA / EN 301 549 compliance
- You work with French public-sector clients (RGAA required)
- You need to demonstrate EAA 2025 compliance to auditors or procurement
- Compliance must be traceable and up to date as standards evolve
Consider AlignUI if
- You need a large catalogue of components quickly (180+ PRO)
- A designer–developer Figma workflow is central to your process
- You prefer one-time payment over a subscription
- EU regulatory compliance is not a hard requirement for your project
Ready to evaluate
Review pricing and plan your rollout
Konform ships accessible React components with WCAG 2.2 AA and RGAA 4.1.2 documentation. Review the offer, then join early access when you are ready to bring the library into your product workflow.
Related resources
Continue with EU accessibility compliance comparisons
compare Konform vs DSFR for RGAA compliance
See how Konform differs from the French government design system on branding and private-sector fit.
compare Konform vs Radix accessibility documentation
Review the gap between strong accessibility primitives and audit-ready RGAA documentation.
free RGAA audit tools and contrast checker
Run a component checklist and quick contrast checks before your next accessibility review.
EAA 2025 obligations for French e-commerce teams
Understand what private-sector product teams must document and fix now that the EAA is in force.