Explain to me in simple terms the European Accessibility Act and its impact for designers

What it says, simply - The European Accessibility Act (EAA) requires many products and services placed on the EU market to be accessible to people with disabilities. For digital content and many ICT products, the EAA expects designers and providers to follow recognized technical standards and good practices so accessibility is consistent, testable and enforceable. Key standards designers should use - WCAG 2.1 / 2.2 (Web Content Accessibility Guidelines): the primary standard for websites, web apps and many digital documents. It covers perceivable, operable, understandable and robust principles (e.g., text alternatives, keyboard access, contrast, clear navigation). - EN and ISO standards referenced by the EAA: depending on the product or service, the EAA points to European harmonized standards (EN) and international standards (ISO) that provide specific techniques and test methods — for example standards for ATMs, e‑commerce, ticketing machines, and software interfaces. - Other technical specifications: the EAA may reference specialized specs (e.g., PDF/UA for accessible PDFs, platform accessibility APIs, or national technical guidelines) where relevant. What designers must do, practically - Adopt WCAG success criteria appropriate to the content (WCAG 2.1 or 2.2). Apply relevant levels (typically A and AA are used as legal baselines in practice). - Use recognized techniques and testing methods from WCAG, EN/ISO standards or other referenced documents so compliance can be demonstrated and verified. - Design accessibly from the start (inclusive design) — not as an afterthought — and test with assistive technologies and real users with disabilities. - Keep documentation: explain which standards were followed, test results, and how accessibility will be maintained (updates, bug fixes). Impact for designers - More predictable requirements: following standards gives clear guidance and legal cover. - Design process changes: include accessibility in requirements, prototypes, code, QA and content workflows. - Increased testing burden: automated checks plus manual and user testing required to meet technical criteria. - Broader audience and better usability for all users as a positive side effect. Where to read more - WCAG 2.1 and 2.2: W3C Web Accessibility Initiative (WAI) — https://www.w3.org/WAI/standards-guidelines/wcag/ - European Accessibility Act: European Commission — https://ec.europa.eu/social/main.jsp?catId=1202 References - European Accessibility Act, Directive (EU) 2019/882. - W3C Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2.