Short answerThe European Accessibility Act, Directive (EU) 2019/882, has applied since 28 June 2025 to e-commerce services and many consumer products. Online shops must meet accessibility requirements generally assessed against EN 301 549, whose current reference version incorporates WCAG 2.1 AA. Product content teams own a large share of that work: alt text, accessible documents, video captions and clear product information.
Key takeaways
- The European Accessibility Act has applied since 28 June 2025 and covers e-commerce services offered to consumers in the EU, with an exemption for microenterprises providing services.
- EN 301 549 is the reference standard for websites and apps; version 3.2.1 maps to WCAG 2.1 AA, and version 4.1.1 of September 2026 moves to WCAG 2.2 pending citation.
- Images, PDFs and videos supplied from DAM and PIM typically make up most of the content on a product detail page, so accessibility metadata belongs in those systems.
The EAA makes product content an accessibility obligation
The European Accessibility Act (EAA), Directive (EU) 2019/882, has applied since 28 June 2025 through national transposition laws in each member state. It covers e-commerce services, banking, transport ticketing, e-books and a set of products such as computers, smartphones, terminals and e-readers. Online shops selling to EU consumers must make their services perceivable, operable, understandable and compatible with assistive technologies for people with disabilities. Front-end developers fix templates, but the product data and assets that fill those templates come from PIM and DAM, so accessibility depends on content operations too.
WCAG 2.1 AA via EN 301 549 sets the practical bar
EN 301 549 is the European standard used to demonstrate conformity, and version 3.2.1 incorporates WCAG 2.1 level AA in its web and app chapters. Version 4.1.1, published in September 2026 under a Commission standardisation request linked to the EAA, adopts WCAG 2.2, which adds criteria on focus visibility and target size. It gives a presumption of conformity only once cited in the Official Journal. As of October 2026 no version had been cited under the EAA (version 3.2.1 is cited under the Web Accessibility Directive), and Ireland's National Disability Authority expects citation of version 4.1.1 around 16 December 2026, so WCAG 2.2 AA is the safer target now. Market surveillance authorities in each member state enforce the rules, with penalties set nationally.
The Act includes transition provisions: services may continue to use products they relied on before 28 June 2025 until the end of their economically useful life, up to 2030, and self-service terminals can stay in use for up to 20 years. Microenterprises providing services, those with fewer than 10 staff and annual turnover or balance sheet not above 2 million euro, are exempt. Content published after the application date carries no such grace period.
Product content requirements map to specific WCAG criteria
Several WCAG success criteria fall directly on content owned by product data and creative teams.
| Content element | Relevant WCAG criterion | Owner system |
|---|---|---|
| Product images | 1.1.1 Non-text content (text alternatives) | DAM, with context from PIM |
| Product videos | 1.2.2 Captions, 1.2.5 Audio description | DAM |
| Spec sheets, manuals, safety PDFs | Document accessibility (PDF/UA, tagged structure) | DAM or document management |
| Colour swatches and variants | 1.4.1 Use of colour | PIM (colour name attribute) |
| Descriptions and specifications | 1.3.1 Info and relationships, 3.1 Readable | PIM |
| Language of content | 3.1.2 Language of parts | PIM (locale tags) |
Annex I of the EAA also requires that information about the accessibility of the service, and of products sold, be provided where it is available from the economic operator responsible. Accessibility features of a product, such as a hearing aid compatible handset or a tactile control, therefore become product attributes in their own right.
DAM and PIM need accessibility metadata fields
Accessibility becomes manageable when it is a governed attribute with completeness rules. The core additions are modest.
- Image alt text per locale: short, descriptive, written for the purpose of the image; decorative images flagged as such so the front end renders an empty alt attribute. Guidance on fields sits in DAM metadata and taxonomy.
- Long description: for charts, dimension drawings and infographics that alt text cannot cover.
- Video captions and transcripts: caption files (WebVTT or SRT) per language stored as renditions linked to the master asset.
- Document accessibility status: tagged PDF, PDF/UA conformance, reading order checked, with an HTML alternative where possible.
- Product accessibility features: structured attributes describing how the product supports users with disabilities.
AI auto-tagging can draft alt text at scale, as covered in AI auto-tagging in DAM, but drafts need human review for hero and safety-relevant images. Contextual alt text often depends on product attributes, so generation works best when the PIM passes product name, colour and variant to the DAM, following the patterns in DAM and PIM integration.
Prioritise by traffic and document risk
A realistic remediation plan concentrates effort where users and authorities will look first.
- Audit the top product detail page templates and the 10 to 20% of SKUs that generate most traffic.
- Make alt text and caption fields mandatory in DAM upload workflows for all new assets.
- Remediate or replace PDFs for safety information, manuals and declarations, which overlap with GPSR obligations described in GPSR product safety data.
- Add accessibility completeness to channel readiness scores.
Backlog remediation of a large image library typically takes an estimated 3 to 12 months, depending on volume and review depth. Teams assessing whether their DAM supports per-locale alt text and caption renditions can compare platforms in the DAM vendors overview.
Frequently asked questions
Does the European Accessibility Act apply to online shops?
Yes. E-commerce services offered to consumers in the EU have been in scope since 28 June 2025, including websites and mobile apps. Microenterprises providing services, with fewer than 10 employees and turnover or balance sheet not above 2 million euro, are exempt. Non-EU businesses selling to EU consumers are also covered.
Which standard shows compliance with the EAA?
EN 301 549 is the European standard for information and communication technology accessibility. Version 3.2.1 incorporates the WCAG 2.1 level AA success criteria, and version 4.1.1, published in September 2026, moves to WCAG 2.2. As of October 2026 it had not been cited in the Official Journal; citation is expected around December 2026. Once cited, meeting it gives a presumption of conformity with the relevant EAA requirements for websites and apps.
Who should write alt text for product images?
Product content teams should own alt text, with the DAM storing it per locale and per asset. AI tools can draft alt text at scale using product attributes from the PIM, but human reviewers should approve hero images, safety-relevant visuals and images where context changes the meaning.