EAA / RGAA
Directive (UE) 2019/882 ; EN 301 549 ; RGAA 4.1
L'exigence. L'European Accessibility Act s'applique depuis juin 2025 (banque, e-commerce…) ; le RGAA s'impose au secteur public. Les documents générés — pas seulement les sites — doivent être accessibles.
La réponse AWA. La bibliothèque PDF fournit un linter PDF/UA-1 (ISO 14289-1), avec des contrôles PDF/UA-2 provisoires : il contrôle la structure des documents balisés (Tagged PDF) que lisent les technologies d'assistance.
Dossier de preuves relatives à la conformité — synthèse exécutive
EAA-01 proven EN 301 549 §9 / §11 — accessibility support in the software platform
The framework ships accessibility primitives as a first-class module: ARIA live-region announcements (announce, clearAnnouncements), aria-* attribute hygiene (aria, labelledBy, describedBy), role management (setRole, removeRole) and prefersReducedMotion detection. The module's own page states that localised business messages are the application layer's responsibility, not the framework's.
EAA-02 partial EN 301 549 §9 (WCAG 2.1 AA) — the delivered component catalog
The curated template catalog carries accessibility markup broadly: 72 of 79 non-test source files contain aria-, role= or prefers-reduced-motion.
The missing half is conformance itself: presence of ARIA markup is not WCAG conformance. There is no automated accessibility gate, no audit report, and @awacloud/ui-templates is declared awa.maturity: L1. Backlog BL-817.
EAA-03 proven EN 301 549 §10 — non-web documents (PDF accessibility)
A PDF/UA-1 (ISO 14289-1) linter with draft PDF/UA-2 support: catalog checks (/StructTreeRoot required, /MarkInfo /Marked true, /Lang, /ViewerPreferences /DisplayDocTitle true), structure-element checks (Figures need /Alt or /ActualText, top-level /Span discouraged) and the accessible-permission bit. It is a static linter over produced PDFs, not a remediation tool and not an audit.
EAA-04 gap Art. 13 + Annex V — accessibility statement / conformity declaration
Absence claim. No accessibility statement, no WCAG/RGAA audit report and no automated accessibility gate exist in the shipped surface. The standard literals appear only incidentally.
Nothing here is an accessibility statement, and no row in this pack may be read as one. Backlog BL-817 (audit + statement + automated gate).
EAA-05 gap EN 301 549 §9 — the SSG shell shipped to site builders
Absence claim, scoped to the component. The site-kit shell — the markup and semantics a buyer inherits when it builds a site with the package — carries accessibility markers in only 1 of 7 source files.
A buyer building a subject site on this shell inherits little accessibility affordance and must supply it itself. @awacloud/site-kit is declared awa.maturity: L1. Backlog BL-818. This row measures the shipped component only; who else must conform, and under what conditions, is outside this pack's face and is deliberately not addressed here.
Dossier généré le 2026-10-01 · preuves vérifiées le 2026-10-01
Statut AwaCloud
À qualifier · statut au 15/09/2026.