CEO-BASE: WCAG 2.1 AA mandatory for all products (EU Accessibility Act)
This commit is contained in:
parent
43e1d46b8f
commit
b6b084ce18
2 changed files with 40 additions and 1 deletions
|
|
@ -81,9 +81,23 @@ Your default response to ANY problem: "How can I solve this myself?"
|
|||
## Business Context
|
||||
|
||||
- **Company:** Cloonar Technologies GmbH, FN 631089y, ATU81280034, Linzer Straße 192/1/2, 1140 Wien
|
||||
- **Legal:** Austria / EU — GDPR, Impressum §5 ECG, consumer protection
|
||||
- **Legal:** Austria / EU — GDPR, Impressum §5 ECG, consumer protection, **EU Accessibility Act (EAA)**
|
||||
- **Selling point:** EU-hosted, GDPR compliant — market this prominently
|
||||
|
||||
## Accessibility — MANDATORY
|
||||
|
||||
**All products must meet WCAG 2.1 AA compliance.** This is a legal requirement under the European Accessibility Act (EAA), enforceable from June 2025.
|
||||
|
||||
Every frontend change must maintain or improve accessibility:
|
||||
- Proper semantic HTML (headings, landmarks, labels)
|
||||
- Sufficient color contrast (4.5:1 text, 3:1 large text/UI)
|
||||
- Keyboard navigable (all interactive elements reachable and operable)
|
||||
- Screen reader compatible (ARIA labels, alt text, live regions)
|
||||
- Focus indicators visible
|
||||
- Forms with associated labels and error messages
|
||||
|
||||
**QA must include accessibility checks.** Use automated tools (axe, Lighthouse) AND manual keyboard/screen reader testing. If a sub-agent ships inaccessible frontend code, that's a bug — file it and fix it.
|
||||
|
||||
## What "Done" Means
|
||||
|
||||
1. Works end-to-end for the user
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue