An article is only open to the people who can read it comfortably. For a reader who is blind, who has low vision or dyslexia, or who is still learning the language, a wall of text is a barrier. A listen button is a second way in, but only if the button itself can be used by everyone. That is where accessibility standards come in.
Who a listen button serves
People who are blind or have low vision already have screen readers, and a screen reader will get through an article. A produced narration is a different experience: a natural voice, paced like speech, with names pronounced the way your newsroom says them. People with dyslexia or another reading difficulty can follow by ear what is tiring to follow by eye. So can someone reading in their second language.
Then there is everyone else, at the moments when reading is not possible: driving, cooking, walking the dog. Accessibility work has a habit of helping more people than it was designed for, and audio is a clear case.
What WCAG 2.2 AA asks of a player
The Web Content Accessibility Guidelines, WCAG, are the W3C’s standard for accessible web content. Level AA is the bar most laws and procurement rules point to, and 2.2 is the current version. For an audio player, it comes down to a few plain questions. Can you operate every control without a mouse? Does a screen reader know what each control is and what state it is in? Are the controls big enough to hit? Is there another way to do anything that needs a drag?
How the Everlit player answers
The Everlit player and playlists are built to WCAG 2.2 Level AA. In practice:
- Keyboard: every control is a real button or slider in a logical tab order. The arrow keys seek by five or ten seconds, and Home and End jump to the start and the end.
- Focus: it stays where you left it through play, pause and loading, and it is never trapped.
- Screen readers: every control has a descriptive name, progress is exposed as a slider with the time spoken, and a quiet announcement says when playback starts, pauses or moves to the next story.
- Images: cover art and sponsor logos carry alt text, and decorative icons are hidden from assistive technology.
- Size: the play button is 64 pixels across, and every control clears the 24-pixel minimum.
- Dragging: anything you can do by dragging the progress bar, you can do from the keyboard.
Those map to specific success criteria, among them 2.1.1 Keyboard, 2.1.2 No Keyboard Trap, 2.4.3 Focus Order, 2.5.7 Dragging Movements, 2.5.8 Target Size, 4.1.2 Name, Role, Value and 4.1.3 Status Messages. The player is also mapped to Section 508, ADA Title III and EN 301 549, the European standard.
Why this is on the calendar for public institutions
In the United States, a Department of Justice rule under Title II of the ADA requires state and local governments, which includes public universities and school districts, to bring their web content to WCAG 2.1 Level AA. After a one-year extension in April 2026, the compliance dates are April 26, 2027 for entities serving 50,000 people or more, and April 26, 2028 for smaller ones. In the European Union, the European Accessibility Act has applied since June 28, 2025. This is a summary, not legal advice; check the rule that applies to you.
If you publish for a university, a district or a public agency, every embedded component on your pages is part of that picture. An audio player should not be the piece that fails the audit.
What audio does not do
Adding audio does not make a page accessible on its own. Your headings, alt text, colour contrast and forms still have to meet the standard, and a narration is not a substitute for captions on video. One more thing to watch: the player takes your brand’s colours, so choose ones that keep the text readable against its background.
Inclusive, and good for the numbers
None of this comes at the expense of reach. Publishers see 2–3x longer engagement when readers can listen, and at The Texas Tribune, 84% of listeners finished the articles they started. The audience you open the door for stays.
To try the player with a keyboard and a screen reader, open it on the Features page, or read the accessibility questions in the FAQ.