Accessibility statement
WeLaunch.dev — European Accessibility Act (Directive (EU) 2019/882) Article 13 surface. Last updated 2026-05-22.
Conformance status
This website strives for conformance with EN 301 549 v3.2.1 Chapter 9 (Web), which incorporates WCAG 2.1 Level AA, in accordance with the European Accessibility Act (Directive (EU) 2019/882, Article 13, binding since 28 June 2025).
Conformance status: partially conformant. Some content does not yet fully conform to EN 301 549 v3.2.1 Chapter 9; see Known limitations below.
Known limitations and planned remediation
The table below enumerates known accessibility limitations with planned remediation. The canonical source is docs/accessibility/known-limitations.md in the repository; this page mirrors the table at publication time and is refreshed at every quarterly review.
| Limitation | Impact | WCAG criterion | Planned remediation | Target date |
|---|---|---|---|---|
| Workflow map list-mode fallback — ARIA tree enhancements pending. The list-mode (mobile + reduced-motion) renders nodes as a flat list rather than a navigable ARIA tree. | Screen-reader users on mobile cannot perceive map hierarchy. | 2.4.3 Focus Order; 1.3.1 Info and Relationships | Promote the list-mode to a proper role="tree" with expand/collapse semantics. Tracked via Story 5.3 follow-up. | 2026-08-15 |
| Manual screen-reader pass scheduling — quarterly cadence pending consultant booking. The docs/accessibility/screen-reader-pass.md procedure is published; a quarterly external pass has not yet been booked. | Manual SR-pass coverage is internal-only at V1. | EN 301 549 §11.7 (Documentation) | Engage an external accessibility consultant for the quarterly NVDA + VoiceOver pass; integrate findings into this statement. Tracked via the Story 5.7 integration-debt entry. | 2026-09-30 |
| Mobile-mode focus-order polish — composer-to-disclosure focus handoff is not fully optimised on iOS Safari. | Mobile users may experience an unexpected focus jump when invoking the AI Act disclosure sheet. | 2.4.3 Focus Order | Audit the <MobileAIActSheet /> focus-trap and align with the desktop <AIActFooter /> behaviour. | 2026-08-31 |
Feedback and contact
If you find an accessibility barrier, email accessibility@welaunch.dev or use the accessibility feedback form. We aim to respond within 5 business days.
Enforcement
WeLaunch (operator: a Delaware limited liability company per /terms) has no EU establishment. For Irish residents, the primary EAA Art. 13 enforcement contact is the National Disability Authority (NDA), 25 Clyde Road, Dublin 4, Ireland (https://www.nda.ie). If you reside in another EU member state, please contact the equivalent national accessibility authority in your country; a directory is maintained by the European Commission.
Statement metadata
Last updated:
Next review due:
Methodology
Verified via axe-core CI on every pull request (covering /, the authenticated workspace, and the AE call-prep surface; 0 critical violations enforced per Story 5.7), manual screen-reader pass (NVDA + VoiceOver) once before launch and quarterly thereafter per docs/accessibility/screen-reader-pass.md, and reduced-motion smoke tests on every release.
The /accessibility-statement page itself is included in the axe-core CI route set (Story 7.11) — the page that asserts a WCAG 2.1 AA conformance claim must pass its own automated check.