Get a Free Consultation →
The regulatory landscape in 2026
Five major jurisdictions, each with their own accessibility framework that ultimately converges on WCAG 2.1 AA as the baseline for digital content including video.
United States
Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, FCC closed captioning rules for broadcast and online video. Federal contractors require WCAG 2.1 AA conformance across digital services. State-level frameworks (California Unruh Act, others) extend reach to private-sector consumer-facing content.
United Kingdom
Equality Act 2010, Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018. WCAG 2.1 AA is the public-sector standard and the procurement baseline for vendors selling into government bodies. Private-sector consumer services increasingly held to similar bars under accessibility case law.
European Union
European Accessibility Act (EAA) enforcement began June 2025, requiring WCAG 2.1 AA across a broad set of private-sector services including financial services, e-commerce, transport ticketing, and audiovisual media. Web Accessibility Directive covers public sector. By 2027, EAA is expected to expand further into enterprise digital content.
Australia
Disability Discrimination Act 1992, Digital Service Standard for federal government. WCAG 2.1 AA is the public-sector baseline. State and federal procurement standards apply WCAG 2.1 AA to vendor digital deliverables. Private-sector consumer services are increasingly subject to similar bars through case law.
Canada
Accessible Canada Act, AODA (Accessibility for Ontarians with Disabilities Act), federal procurement standards. WCAG 2.1 AA is the baseline across federal and Ontario provincial procurement. Other provinces are moving toward the same standard.
How accessibility gets baked into the workflow
Three operating moves that make accessibility a default rather than a retrofit.
1. Captions as the production default
Every video produced in the Shootsta workflow gets auto-generated captions reviewed by a human editor for terminology accuracy. Delivered as SRT, VTT and burned-in versions. Customer does not need to request captions on each project; they are part of the deliverable. This is the single biggest leverage point: making captions a default rather than an add-on cuts accessibility cost by roughly 60% versus retrofitting them per piece.
2. Transcripts and audio description added by use case
Transcripts are added by default for any video over 90 seconds and any video destined for public web search. Audio description is scoped per project for content destined for regulated audiences (government, education, healthcare) or where the visual layer carries information the audio does not. The decision happens at brief stage so the audio description script is built into the video rather than retrofitted after delivery.
3. Multilingual scoping at the program level, not per-project
Languages are agreed during onboarding based on audience footprint. A program serving APAC enterprise customers typically scopes Mandarin, Bahasa, Vietnamese, Thai, Japanese and Korean as available languages from day one. Subtitles in those languages are produced on every relevant piece without a separate procurement event per project. Voiceover replacement is added selectively for L&D and executive content where reading subtitles undermines the format.
What auditable accessibility delivery looks like
For regulated customers and public-sector procurement, the accessibility deliverable has to be documented and defensible at audit. Four things every program should produce.
Per-video conformance documentation. Which WCAG criteria the piece meets, evidenced by the captions, transcripts, audio description and color contrast checks performed during production. Output as a one-page conformance note attached to each finished video.
Standardized SRT/VTT formats following platform-native requirements. Different distribution platforms (YouTube, LinkedIn, internal LMS, Brightcove, Wistia) have slightly different caption format expectations. Standardising on industry formats prevents platform-specific rework.
Auditable change history on the caption and transcript files. Who edited the caption for accuracy, when, and what change was made. Compliance teams want this trail for any video that goes into formal accessibility audit.
Quarterly accessibility QBR with the customer. Review of conformance rate, any accessibility complaints received from end users, and the roadmap for any new layer additions. Keeps the accessibility commitment visible at program-management level rather than buried in production detail.
The cost framing that lands with finance
Accessibility framed as a retrofit cost looks expensive: $50 to $200 per video for captions, transcripts and audio description added after delivery. Accessibility framed as a workflow default looks cheap: the marginal cost is roughly $20 to $50 per video because captions and transcripts come from the same transcription source-of-truth used for production search and asset tagging.
For a 48-video annual program, that is a difference of approximately $1,500 vs $7,500 per year on accessibility delivery. For a 200-video program, $6,000 vs $30,000+. The framing matters when accessibility budget is being scoped: built-in is significantly cheaper than bolted-on.
What this means for in-house teams handling some video themselves
The accessibility default has to apply to in-house-produced video too, not just to partner-produced video. Three practical moves for in-house teams.
Use the same caption and transcript tools the production partner uses, so the output format is consistent across in-house and partner-produced video. Most enterprise transcription tools now offer enterprise SLAs that make this straightforward.
Train internal video producers on the four-layer model so they brief in accessibility requirements from day one rather than discovering them at delivery. Most accessibility retrofits happen because the original brief did not mention accessibility.
Centralize the conformance documentation. Whether the video is produced in-house or by a partner, the conformance note attaches to the asset in the same library. Audit becomes one query, not a multi-vendor reconciliation exercise.
Frequently asked questions
Are auto-generated captions WCAG-compliant?
Auto-generated captions on their own usually do not meet WCAG 2.1 AA because accuracy is the test, not just presence. The current bar is roughly 95%+ accuracy across content, which auto-transcription achieves on clean audio but not consistently on noisy audio, multilingual content, or content with technical terminology. Human review of auto-generated captions is the practical standard.
What is the difference between captions and subtitles?
Closed captions include non-speech information (speaker identification, sound effects, music cues) and are designed for deaf and hard-of-hearing viewers. Subtitles assume the viewer can hear and are designed primarily for translation. Both are produced from the same transcript source but with different annotation layers. WCAG references captions specifically; subtitles are an inclusion feature beyond strict WCAG.
How does WCAG 2.2 affect video?
WCAG 2.2 (October 2023) is an extension of WCAG 2.1 - all 2.1 success criteria still apply, with nine new criteria added that are mostly UI-focused rather than video-specific. For practical purposes, an enterprise program that meets WCAG 2.1 AA also meets the video-relevant portion of WCAG 2.2. Procurement standards are slowly updating to reference WCAG 2.2.
Do we need audio description on every video?
No. Audio description is required where the visual layer carries information that is not in the audio (slides with key data, visual demonstrations of products, on-screen text that is not spoken). For talking-head video where the audio describes everything visible, audio description adds little. The brief stage is when to decide whether audio description is needed.
How fast can captions be delivered?
For standard subscription production, captions deliver with the finished video on the standard 48-hour cadence. For rush production (24-hour or same-day), captions also deliver inside the rush window. No separate delivery timeline; captions are part of the standard deliverable.
What if our customers are in a language not covered by your standard multilingual list?
Niche languages are scoped per project through trusted regional linguist partners. The standard multilingual list covers 15+ business languages routinely; less common languages add 1 to 2 days to the schedule but the same quality bar applies. We will scope availability during onboarding.
How is accessibility delivery audited?
Two ways: by the customer (sample-test caption accuracy, verify file formats, confirm conformance documentation matches the finished asset) or by a third-party accessibility audit firm if your procurement requires it. Shootsta can supply per-video conformance documentation in formats that fit common audit frameworks.
Where to go next
For the multilingual production layer that overlaps with accessibility, read how to scale video across global offices. For the brand-control discipline that holds quality consistent including on accessibility delivery, read brand control with a video production partner. For the workflow that lets accessibility default into every project, read how a video partner extends your in-house team.
To scope an accessibility plan that fits your regulatory exposure, book a free consultation.
