Web Accessibility for Media and Publishing: Compliance Guide

The Media Publishing Accessibility Profile

Media and publishing sites have a distinct set of accessibility challenges compared to ecommerce or lead-generation sites. The content is primarily text and media — articles, videos, podcasts, galleries — rather than transactional flows. The accessibility failures cluster around content types rather than checkout forms.

This distinction matters for scoping accessibility work. A media publisher’s highest-risk areas are video captions, audio transcripts, and the dynamic content loading patterns used to serve high volumes of articles. The technology choices — infinite scroll, auto-playing video, dynamic ad slots — create specific accessibility obstacles.

Video and Audio Captions

WCAG 1.2.2 (Captions, Pre-recorded, Level AA) requires captions for all pre-recorded video content that includes synchronized audio. This applies to every video on your site — not just dedicated video sections. An article with an embedded video clip, a product demonstration embedded in a review, or a talking-head interview all require captions.

What counts as compliant captions: accurate text of spoken dialogue, identification of speakers when context requires it, and descriptions of meaningful non-speech audio (sound effects, music that conveys meaning).

What does not count: auto-generated captions that have not been reviewed for accuracy. YouTube’s auto-captions are frequently incorrect, particularly for technical vocabulary, proper names, and accented speech. Publishing uncorrected auto-captions may be better than nothing but does not meet WCAG’s accuracy standard.

Auto-Playing Media

WCAG 1.4.2 (Audio Control, Level A) requires that automatically playing audio can be paused, stopped, or muted by the user. WCAG 2.2.2 (Pause, Stop, Hide, Level A) extends this to visual content.

Auto-playing video with sound is the most common violation — a user navigating with a screen reader who suddenly has audio from a video competing with their screen reader cannot function. Even auto-playing video without sound can violate 2.2.2 if it cannot be paused.

Default to non-playing. Provide visible, keyboard-accessible play/pause controls on every video embed.

Infinite Scroll and Keyboard Navigation

Infinite scroll creates a navigation dead end for keyboard users. As content loads indefinitely below, the page footer becomes unreachable. Browser functionality that depends on reaching the end of a page does not work. Screen reader users navigating by heading cannot quickly scan the entire article list.

The accessible implementation: provide a “Load more” button that keyboard users can activate deliberately, while optionally keeping scroll-triggered loading for mouse users. Ensure that when a user activates “Load more,” focus either stays on the button (which moves down as content loads) or moves to the first new item loaded.

Scanning Media Sites

A11yProof’s scanning covers the structural accessibility of media sites: missing alt text on article images, form label issues in comment boxes and subscription flows, contrast violations in typography, and missing page language declarations. For ongoing monitoring at $29/month, it catches violations introduced when templates are updated, new widgets are installed, or CMS components are changed.

What requires manual review: caption accuracy (cannot be automated), reading order in complex multi-column article layouts, and the keyboard behavior of custom media players and gallery components.

Integrate accessibility scanning into your content and development workflows — not as a one-time audit, but as an ongoing check that keeps compliance current as the site evolves.