Audio Articles, Accessibility and the European Accessibility Act

An audio version of your articles lets people listen instead of read. That helps readers with low vision, dyslexia or low literacy, older readers, and anyone whose eyes and hands are busy. The European Accessibility Act (EAA), which applies to covered products and services from 28 June 2025, raises the stakes for accessibility in the EU. But be clear on one point: adding audio is a useful improvement, and it does not on its own make a website compliant with the EAA or with WCAG.

This article explains who benefits from audio articles, what the EAA is and who it covers, what compliance actually involves, and how to add audio in a way that genuinely helps.

Who benefits from audio versions of written content

Reading a long page of text is harder for many people than we tend to assume. A clearly labelled Listen button gives them another way in.

• People with low vision. Many blind users already rely on a screen reader, but plenty of people with partial sight do not use one. For them, zooming and squinting through a long article is tiring, and pressing play is much easier.
• People with dyslexia and other reading difficulties. Hearing the text, especially with the words highlighted as they are spoken, can make long content easier to follow and understand.
• People with low literacy or reading in a second language. Listening can make content understandable to people who struggle with dense written text, and it helps with pronunciation of unfamiliar words.
• Older readers. Eyesight changes with age, and small type on a phone screen is a real barrier. Audio takes that barrier away.
• People with tired eyes or temporary impairments. A migraine, an eye operation or a long day at a screen can make reading hard for anyone.
• Multitaskers. Commuters, parents, people cooking or exercising can finish an article they would otherwise have saved for later and never opened again.

That last group is a reminder that accessibility features tend to help everyone, not only the people they were designed for.

What is the European Accessibility Act?

The European Accessibility Act is an EU directive, Directive (EU) 2019/882 (opens in a new tab). Its goal is to make key products and services accessible to people with disabilities and to replace the patchwork of different national rules with common requirements across the EU. Each member state must write it into its own national law, and those laws are what businesses must follow and what national authorities enforce.

According to the EU's Your Europe guidance for businesses (opens in a new tab), the requirements apply to products placed on the market, and services provided to consumers, after 28 June 2025.

Which products and services does the EAA cover?

The EAA does not cover every website. It covers specific products and services, including:

• Computers, operating systems, smartphones and tablets
• ATMs, ticketing and check-in machines, and card payment terminals
• E-books and e-readers
• Digital TV equipment and access to audiovisual media services
• Electronic communications services, such as telephone services
• Passenger transport services by air, bus, rail and water, including their websites, mobile apps, e-tickets and real-time travel information (for urban, suburban and regional transport, only self-service terminals are covered)
• Consumer banking services
• E-commerce, meaning online shops and other services that sell to consumers online

If your business sells to consumers in the EU online, the e-commerce category is the one to look at closely. This can include businesses based outside the EU that sell to EU customers.

Exemptions and exceptions

• Microenterprises that provide services are exempt from the service requirements. The directive defines these as businesses with fewer than 10 employees and an annual turnover or annual balance sheet total of no more than €2 million. The exemption does not apply to products in the same way.
• Disproportionate burden. A business can rely on this exception only after it assesses and documents the burden against the criteria set out in the directive, and it must usually inform the national authority. Service providers must renew that assessment when the service changes, when an authority asks, and at least every five years.
• Transition periods. Service providers may keep using products they already used before 28 June 2025 until 28 June 2030, service contracts agreed before that date can run until they expire (for up to five years), and member states may let existing self-service terminals stay in use for up to 20 years.

A personal blog, or a business site that informs but does not sell to consumers, may fall outside the Act. Whether your site is covered depends on what you offer and where, so check your national rules or ask a legal adviser rather than guessing.

Does adding audio make a site EAA or WCAG compliant?

No. This is the most important point in this article, and it is worth being direct about it.

Accessibility compliance is measured against detailed technical criteria. In practice that means the Web Content Accessibility Guidelines (opens in a new tab) (WCAG 2.1 or 2.2 at level AA) and the European standard EN 301 549, whose web requirements build on WCAG. The version currently used as the legal reference, v3.2.1, is based on WCAG 2.1 AA; a new version, v4.1.1, published in September 2026, moves to WCAG 2.2 but is not yet the legal reference. Those criteria cover things an audio player cannot fix, such as:

• Text alternatives for images and other non-text content
• Captions and transcripts for video and audio
• Full keyboard access, with a visible focus indicator
• Sufficient color contrast and text that can be resized
• Clear labels and error messages on forms, including checkout
• A logical heading structure and page language

A site can offer a beautiful audio version of every article and still fail on any of these. The honest path is a proper accessibility audit against WCAG 2.1 or 2.2 AA and EN 301 549, done by someone qualified, followed by fixing what it finds. Be wary of any tool, including an audio player, that promises compliance with one click.

What audio does do is make your written content easier to take in for a large group of people. It is a genuine improvement to the experience, and it fits well alongside the work an audit asks for.

How to offer audio versions that actually help

An audio feature can itself create barriers if it is added carelessly. A few habits make the difference:

1. Make the player accessible. The Listen button should work with a keyboard, have a clear label that screen readers announce, and have enough contrast to be seen.
2. Never autoplay. Audio that starts on its own interferes with screen readers and surprises everyone else. WCAG requires a way to pause or stop audio that plays automatically for more than three seconds, or to control its volume separately from the system volume, and the simplest answer is not to autoplay at all.
3. Put it where people look. Place the button near the top of the article, so readers find it before they give up.
4. Read the right content. Skip menus, sidebars, cookie banners and code, so listeners hear the article, not the page furniture.
5. Fix pronunciation. Abbreviations, product names and numbers are often read wrongly. Correct the ones your audience will hear most.
6. Let listeners control it. Pause, resume and speed controls matter, and highlighting the words being read helps readers who follow along.
7. Keep the voice consistent. A generated audio file sounds the same on every device, while browser voices vary from phone to phone.

Adding audio articles with AtlasVoice

AtlasVoice adds a Listen button to your content in two ways:

• On WordPress, the free plugin adds the button to the post types you choose, with read-along highlighting, pronunciation fixes and a player you can style to match your site. Follow our step-by-step guide, how to add text to speech to WordPress posts (opens in a new tab).
• On any other platform, such as Shopify, Wix, Webflow, Squarespace or your own app, the AtlasVoice API (opens in a new tab) turns your text into MP3 audio you store with your content. The free plan includes 100,000 characters a month.

Either way, treat audio as one part of your accessibility work, not the whole of it.

Next step

If the EAA may apply to your business, start with an accessibility audit against WCAG 2.1 or 2.2 AA and EN 301 549, and plan the fixes. Then give your readers the option to listen: install the free AtlasVoice plugin (opens in a new tab) on WordPress, or get a free key for the AtlasVoice API (opens in a new tab) for any other site.