Why are toggleable captions still not enough for some classroom and civic deployments?
Classroom panels, kiosk browsers, and locked-down civic portals often hide caption menus, excluding deaf and hard-of-hearing audiences by accident. Burning makes information visible regardless of player literacy. Teams search accessible video captions burned in, classroom recording captions, government explainer subtitles, and WCAG video contrast tips because policy asks for proof, not promises. Burning alone never satisfies every WCAG criterion: line spacing, flash thresholds, and color-blind safety still need design review. Critical numbers should also appear in downloadable transcripts for screen-reader paths. Bilingual stacks can crowd small screens—consider simplified single-language burns per SKU. Post-burn text cannot track system font scaling—test on the smallest supported phone width. Medical or legal phrasing needs dual human review because pixel typos are painful to retract. This variant sequences contrast, line length, muted QA, companion transcripts, then archived audit notes.
Accessible burn variant: document decisions, not just pixels
- List must-read nouns for deaf viewers, pick high-contrast colors, and keep lower-thirds clear of faces and critical UI.
- Export, mute-play on a 375px-wide phone, log any occlusion or flicker, and iterate before org-wide distribution.
- Link a searchable transcript with burn version and publish date; keep a clean master for audiences who prefer toggleable tracks.