Sooner or later, someone asks the question: “Do I actually have to make my podcast accessible?” The honest answer is that it depends on who you are, where you are, and who you work for. This article gives you a general map of the territory so you can ask better questions, without pretending to be a substitute for a qualified professional.

Requirements depend on where you are

There is no single worldwide rule for podcast accessibility. Different countries, and sometimes different states or provinces, have their own approaches. Some focus on public bodies, some on businesses that serve the public, some on education or employment, and some on all of these. A few rely on general anti-discrimination principles rather than detailed technical rules, which leaves a lot to interpretation.

That variety is why you can’t safely rely on something you read in a forum or on social media. A claim like “podcasts are exempt” or “everyone must have transcripts” is almost certainly oversimplified. Where you are based, where your audience lives, who funds you and what kind of organization you are can all change the picture.

The practical takeaway: find out which rules apply to your situation before you assume anything, either way.

Legal risk is one reason among several

It’s tempting to treat accessibility as a compliance chore, something you do to avoid trouble. That framing tends to produce minimal, box-ticking work, and it misses most of the value.

Think about the other reasons to do it:

• People. Deaf and hard of hearing listeners can’t use audio on its own. Blind and low vision users need a site and player that work with assistive technology. People with motor or cognitive disabilities need clear, forgiving interfaces. Reaching them is the point.
• Audience. Transcripts and clear pages help more people find and enjoy your show. When This American Life, with more than 520 one-hour episodes, added transcripts, 7.23% of unique visitors viewed at least one, and the show saw a 6.68% increase in search traffic and a 3.89% increase in inbound links.
• Reputation. A show that treats every listener as a guest earns goodwill. One that ignores them can lose it.
• Quality. Accessible work tends to be better organized, easier to maintain and easier to hand over to someone new.

Accessibility that exists only to avoid a complaint is fragile. Accessibility that exists for your listeners lasts.

Standards as a common reference

When laws and policies do mention technical requirements, they often point to a recognized standard rather than inventing their own. The Web Content Accessibility Guidelines, usually shortened to WCAG, are the most widely used reference for web content. You’ll see them mentioned in policies, procurement documents and contracts around the world.

WCAG is organized around four ideas: content should be perceivable, operable, understandable and robust. In practice that translates into concrete things you can check, such as a contrast ratio of at least 4.5:1 for normal-size text, text that can be resized to 200% without breaking the layout, a visible keyboard focus indicator, and text alternatives for non-text content.

For podcasters, the standard is most relevant to your website and your player. Audio-only content raises its own question, which is how to give people who can’t hear it an equivalent. A transcript is the common answer. The standard also describes conformance levels, and which level is expected can depend on the context you work in.

Even if no rule requires you to follow WCAG, it’s a sensible yardstick. It was written by people who study how disabled users actually experience the web, and it gives you a shared vocabulary when you talk to developers, designers or hosts.

Who is more likely to be affected

In general terms, some kinds of creators are more likely to face formal expectations than others. This is a broad pattern, not a rule about any individual case.

• Businesses. A company that publishes a podcast as part of its marketing, customer service or product offering may be held to the same expectations as its other digital content. Branded shows often sit inside the larger company website, which may already have an accessibility policy.
• Education. Universities, colleges and schools often have accessibility policies for course materials. A podcast used for teaching, such as lectures or interviews assigned as listening, may be covered, and students may ask for transcripts as an accommodation.
• Public bodies. Government agencies and publicly funded organizations commonly have specific duties around digital content, which may include audio and video.
• Independent hobbyists. A personal show made in your spare time is, in many places, less likely to face formal obligations. That doesn’t change the benefits, and it doesn’t mean the rules are the same everywhere.

If you produce a podcast for an employer, a client or a funder, ask them early whether an accessibility policy exists. It’s far easier to build in transcripts from episode one than to retrofit a back catalog.

Document your efforts

Whatever your legal position, keeping a record of what you do is smart. It helps your team stay consistent, and if someone ever raises a concern, it shows that you take the subject seriously.

A simple record might include:

1. A short accessibility statement on your site describing what you provide, such as transcripts for each episode, and how to reach you if something doesn’t work.
2. A checklist you follow for every episode, with dates showing it was done.
3. Notes from your own testing, including what you found and what you fixed.
4. A log of feedback from listeners and how you responded.
5. Any decisions about things you can’t yet fix, with a plan and a target date.

Be honest in your statement. Claiming full accessibility when you haven’t verified it can backfire. “We provide transcripts for all episodes from 2018 onward and are working on earlier ones” is accurate and useful.

Final thoughts

You don’t need a law degree to start doing the right thing. Find out which rules might apply to you, and get qualified advice if the stakes are real. Use WCAG as your practical benchmark, publish transcripts, keep your site and player usable, and write down what you do. Treat the law as the floor, not the goal. The goal is a show that people with and without disabilities can enjoy equally.