EAA / RGAA
Directive (EU) 2019/882; EN 301 549; RGAA 4.1
The requirement. The European Accessibility Act has applied since June 2025 (banking, e-commerce…); the RGAA is mandatory for the public sector. Generated documents — not just websites — must be accessible.
The AWA answer. The PDF library provides a PDF/UA-1 linter (ISO 14289-1), with draft PDF/UA-2 checks: it checks the structure of tagged documents (Tagged PDF) that assistive technologies read.
Compliance evidence pack — executive summary
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.
| Pack generated | Evidence verified |
|---|---|
| 2026-10-01 | 2026-10-01 |
AwaCloud status
To be qualified · status as of 2026-09-15.