European Accessibility Act (EAA) Video Requirements

A full written version of everything spoken and heard in the video. Useful for screen readers and users who prefer to scan or search content.

Where: Add under the video in the description or link to a downloadable text file.

Transcript Best Practice:

• Manually type or review transcripts to ensure correct spelling, speaker labels, and punctuation
• Avoid relying solely on auto-generated transcripts, they often miss industry terms, names, and nuance
• Format for clarity: Use timestamps, paragraph breaks, and speaker names where helpful

Why it matters: Accurate transcripts improve accessibility for deaf users, screen reader users, non-native speakers, and also boost SEO

Audio descriptions are narrated explanations of key visual information, describing actions, settings, facial expressions, or on-screen text for blind or low-vision viewers.

Audio Description Best Practice:

• Create a dedicated audio track that includes descriptions timed to fit natural pauses in dialogue
• Use a professional narrator with a clear, neutral tone to avoid distracting from the main audio
• Keep descriptions concise and relevant to what’s essential for understanding the story

Where it’s supported:

• YouTube: Not natively: workaround is to upload a second version of the video with audio descriptions included
• Vimeo: Supports audio description tracks via third-party plugins or alternate uploads
• Broadcast & streaming platforms: BBC iPlayer, Netflix, Disney+, and Amazon Prime all support AD through audio settings
• Social platforms: Instagram, LinkedIn, and TikTok currently do not support alternate audio tracks, use described video versions instead

Audio Description Workarounds:

• Create a version with AD baked in for platforms that don’t support alternate tracks
• Use captions to support visual-only content, but don’t rely on them alone — they don’t help blind users
• Label your described videos clearly in titles or descriptions (e.g. “with Audio Description”) so users know what to expect

Why it matters: Audio descriptions give blind and partially sighted users equal access to visual stories, and are a legal requirement for public sector and many commercial videos under accessibility guidelines.

Real-time subtitles during live broadcasts and events, helping all viewers follow along in noisy settings or without sound.

Where: Enabled during livestream setup; toggled by viewers via “CC”.

Best Practice: Use a live human captioner or a reliable captioning API to reduce delays and improve accuracy.

When Live Captions Are Necessary

• Public sector live streams (e.g. government announcements, council meetings)
• Educational content delivered live (e.g. webinars, university lectures)
• Live events where information is essential for public understanding (e.g. health updates, safety briefings)
• Online services in scope of the EAA (e.g. banking, ecommerce, transport) if offering live video content

Legal basis: Under EAA and in some countries (e.g. UK’s Equality Act), not providing captions may count as discrimination if no alternative is offered.

When Live Captions are Recommended

• Corporate webinars, product launches, or training
• Events targeting international or noisy environments, where users might prefer to read
• When targeting viewers with hearing loss or neurodiverse audiences

When Live Captions are Optional

• Internal team meetings or small-scale webinars not aimed at the public
• Informal social media livestreams where no significant information is conveyed

A visible interpreter using British Sign Language (BSL) or other relevant format for viewers who communicate visually.

Where: Displayed in a corner of the video or as a picture-in-picture overlay.

Best Practice: Ensure the interpreter is well-lit, clearly framed, and not obscured by other visuals or overlays.

When Sign Language is Necessary

• Public-facing video content from government or public bodies
• Critical information such as:
  • Health and safety updates
  • Legal rights and policy changes
  • Emergency broadcasts
• When targeting audiences that rely on sign language (e.g. Deaf community events)

Legal basis: In many EU countries, national accessibility laws require sign language for official government communications or essential services.

When Sign Language is Recommended

• High-visibility public events or campaigns
• Content aimed at inclusion, accessibility, or diversity
• Events where live interaction is available in BSL (e.g. Q&A sessions)

When Sign Language is Optional

• Content already well supported with captions and transcripts, and not essential to the public
• Audiences where sign language is not a known requirement
• Budget or space limitations, provided other accessible formats are available

Essential controls for people using screen readers, keyboards, or custom settings (e.g. font size, contrast, playback speed).

Where: Built into accessible players like YouTube’s native interface or third-party compliant players.

Best Practice: Choose players that support keyboard navigation, ARIA labels, and customisation for captions and controls.

What Is Keyboard Navigation?

Keyboard navigation means users can control the video player using only their keyboard — without needing a mouse.

This is essential for:

• People with mobility impairments
• Blind users relying on screen readers
• Anyone using assistive technology or keyboard-only setups

Common functions include:

• Tab to move between buttons (e.g. play, pause, volume)
• Enter or Space to activate buttons
• Shortcuts like K for play/pause, F for fullscreen, C for captions (on platforms like YouTube)

What Are ARIA Labels?

ARIA labels (Accessible Rich Internet Applications) are bits of hidden code that tell screen readers what each control does.

They help blind and low-vision users by:

• Announcing the purpose of buttons (e.g. “Play”, “Mute”, “Turn captions on”)
• Describing interactive elements like sliders, menus and toggle switches
• Giving context to custom controls that might otherwise be invisible to assistive tech

Without ARIA labels, a screen reader might just say “button” with no clue what it actually does.