Picture a listener with a broken wrist who wants to play your latest episode. Their mouse is out of reach, so they press Tab and hope. If your site responds sensibly, they are listening in seconds. If it does not, they give up and go elsewhere. Keyboard access is the quiet foundation of web accessibility, and podcast sites, packed with players, menus, subscribe buttons and pop-ups, are easy places to break it.

Who actually uses a keyboard

Some people never use a mouse. Blind listeners who rely on screen readers navigate by keyboard. So do people with tremors, limited hand mobility or repetitive strain injuries, and people who use switch devices or voice control that mimic key presses. Others are only temporarily affected: a sprained thumb, a trackpad that has died, a laptop balanced on a train tray table. Plenty of fast typists simply prefer the keyboard.

The good news is that one fix helps all of them. If everything works with a keyboard, it will almost always work with assistive technology too.

Get the tab order right

Pressing Tab moves focus from one interactive element to the next. By default the order follows the order of your HTML, which normally matches the visual layout. Problems appear when design tricks pull the two apart, such as a sidebar that is visually on the right but comes first in the code, or a hover menu built from elements that cannot receive focus at all.

A sensible order on an episode page looks like this:

1. Skip link
2. Site navigation
3. Episode title area and the player
4. Show notes and transcript
5. Subscribe and sharing options
6. Footer

Use real buttons and real links wherever you can. A native button gets focus, responds to Enter and Space, and announces itself to screen readers without any extra work. A clickable div gets none of that.

If it can be clicked, it must be reachable and operable from the keyboard.

Make focus visible

Keyboard users need to see where they are. Browsers draw a focus outline by default, and one of the most common accessibility mistakes is removing it with a style rule because a designer found it ugly. If you remove it, you must replace it with something at least as clear.

• Use a thick outline or a two-tone ring that stands out against both light and dark backgrounds.
• Apply it to every interactive element: links, buttons, form fields, sliders and custom controls.
• Make sure sticky headers or cookie banners do not cover the focused element as the page scrolls.

Add a skip link

Without a shortcut, a keyboard user has to tab through your entire navigation menu on every page before reaching the episode. Twelve links might not sound like much, but multiply that by every visit.

A skip link is a link placed first on the page, with text such as “Skip to main content”. It can stay hidden until it receives focus, then appear in a clear spot at the top. Activating it moves focus to the main content area, which should have a matching target. If your episode list is long, consider a second skip link that jumps past the filters straight to the results.

Avoid keyboard traps

A keyboard trap is a place where focus enters and cannot leave. They tend to hide in embedded content: an old-style player, a newsletter sign-up widget, a video from another site, or a modal dialog that never lets go.

If you use a dialog, such as a subscribe pop-up, it needs a predictable pattern:

• When it opens, move focus into it, usually to the heading or the first control.
• While it is open, keep Tab cycling within it, since the page behind is inactive.
• Escape closes it, and so does a clearly labelled close button.
• When it closes, return focus to the button that opened it.

Better still, ask whether you need the pop-up at all. A plain section of the page with a sign-up form never traps anyone.

Custom controls need extra care

Podcast sites love custom widgets: speed selectors, episode filters, accordions for show notes, tabbed panels for chapters and transcripts. Each one brings expectations for how keys should behave. Tabs usually respond to arrow keys. Menus open with Enter or Space and close with Escape. Sliders respond to arrow keys, and Home and End jump to the extremes.

If you build these from scratch, you also have to tell assistive technology what they are, using the right roles, names and states. That is a lot of detail to get right, which is why the simplest approach is often best. A set of ordinary buttons or a native select element does the job and carries fewer risks. Reach for a custom widget only when it earns its place.

Hover is a related trap. Anything that appears only on mouse hover, like a dropdown of episode seasons or a tooltip with a guest bio, must also appear on keyboard focus.

How to test with your own keyboard

You do not need special software. Put the mouse aside, or unplug it, and work through your site with these keys:

• Tab moves forward through interactive elements.
• Shift+Tab moves backward.
• Enter activates links and buttons.
• Space activates buttons, toggles checkboxes and scrolls the page.
• Escape closes menus, dialogs and pop-ups.
• Arrow keys operate sliders, tabs, radio groups and menus.

Now run a short script. Load an episode page, then try to do what a listener would do: skip to the content, start playback, pause, change speed, open the transcript, find the subscribe options, and leave a comment if you allow them. Watch for these red flags as you go:

1. You cannot tell where focus is.
2. Focus jumps somewhere unexpected or vanishes.
3. A control works with a mouse but ignores Enter or Space.
4. Something opens and you cannot close it.
5. The order feels random compared with what you see on screen.

Write down every failure with the page address and the step where it happened. Fix traps and unreachable controls first, since they block people completely. Poor focus visibility comes next, then smaller order issues.

Final thoughts

Keyboard accessibility is not a special feature for a small group. It is the baseline that screen reader use, voice control, switch access and a good deal of everyday convenience all depend on. Start by testing your most important page, the episode page, for ten minutes. Fix the visible focus, add a skip link, and make sure the player works without a mouse. Those three changes will make your show noticeably easier to reach for many of the people who want to hear it.