European Accessibility Act and EN 301 549 Evidence
Build a traceable accessibility evidence matrix for a specified EU product or service. Distinguish applicable law, technical standards, measured outcomes and unresolved compliance questions.
Start with the actual product or service, target Member States, release and economic operator role. Identify the relevant national implementation of Directive (EU) 2019/882 and the applicable category and exceptions. Confirm legal scoping with the responsible reviewer, particularly for exemptions, disproportionate burden or transition provisions. Do not assume the same scope applies to every website, procurement or public-sector body. ## Key Points - [European Accessibility Act Directive and Annex I](https://www.legislation.gov.uk/eudr/2019/882/adopted) - [ETSI EN 301 549 V4.1.1 technical text](https://www.etsi.org/deliver/etsi_en/301500_301599/301549/04.01.01_60/en_301549v040101p.pdf) - [European Commission Web Accessibility Directive standards](https://digital-strategy.ec.europa.eu/en/policies/web-accessibility-directive-standards-and-harmonisation) - [EU standardisation work supporting the EAA](https://interoperable-europe.ec.europa.eu/sites/default/files/custom-page/attachment/2026-03/cnect_rollingplan_ict_2026_spr_pr1.pdf)
skilldb get accessibility-skills/eaa-en-301-549-evidenceFull skill: 31 linesEuropean Accessibility Act and EN 301 549 Evidence
Start with the actual product or service, target Member States, release and economic operator role. Identify the relevant national implementation of Directive (EU) 2019/882 and the applicable category and exceptions. Confirm legal scoping with the responsible reviewer, particularly for exemptions, disproportionate burden or transition provisions. Do not assume the same scope applies to every website, procurement or public-sector body.
Pin the evidence baseline
Record the directive and national provision, relevant Annex I requirements and each technical baseline's version and date. Check whether a standard or part is referenced in the Official Journal for the specific legislation and scope. A published ETSI edition, a standardization request, and an Official Journal citation are different evidence. Do not reuse a Web Accessibility Directive citation as proof that the same edition provides a presumption under the European Accessibility Act. If the applicable reference cannot be confirmed, retain the technical baseline and mark legal status unresolved.
Map the relevant EN 301 549 clauses to real surfaces such as web checkout, mobile software, documents, authentication, support or hardware when in scope. Identify the WCAG version referred to by the selected technical edition, and test requirements beyond a web-only scan. For each applicable requirement, record clause, surface and version, test steps, environment, observed result, supporting artifact, owner and retest status. A status of not applicable needs a rationale tied to the product and requirement.
Exercise the actual service and report limits
Walk one normal user journey through the affected platform using keyboard and relevant assistive technologies, including errors, dialogs, payment handoff or support where within scope. Use automation for repeatable checks, then perform manual and assistive technology checks where those tools cannot establish behavior. Include the exact product/build and device/assistive technology versions. Clearly distinguish pass, fail, not applicable and untested. Redact personal data from artifacts.
Create a remediation list with owners and observable retest steps. Return the evidence matrix and list of unresolved scope decisions to the responsible reviewer. A passing subset or a WCAG scan does not establish a complete technical assessment or legal compliance determination.
References and rights
- European Accessibility Act Directive and Annex I
- ETSI EN 301 549 V4.1.1 technical text
- European Commission Web Accessibility Directive standards
- EU standardisation work supporting the EAA
- AccessibleEU explanation of the September 2026 standard update
Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.
Install this skill directly: skilldb add accessibility-skills
Related Skills
Focus Management
Focus management strategies for single-page applications, modals, route changes, and dynamic content
Keyboard Dialog Regression Test
Turn a modal dialog keyboard or focus bug into a reproducible browser regression test. Cover initial focus, tab boundaries, dismissal, and focus restoration, including removed triggers and dynamic controls when those states exist.
Keyboard Navigation
Keyboard navigation patterns, focus order, and shortcut design for fully keyboard-accessible interfaces
Screen Reader Compat
Building web content that works correctly with screen readers like NVDA, JAWS, and VoiceOver
Wcag Guidelines
WCAG 2.2 compliance levels, success criteria, and implementation strategies for accessible web content
Accessible Forms
Accessible form design patterns including labels, validation, error handling, and multi-step forms