Module 3.2: Reviewing Video Intros, Transitions, Motion Graphics

Your agency's video content does more than inform—it represents your community. Station IDs, meeting intros, animated lower thirds, and slide transitions all help establish a professional identity on air and online. But these same elements are among the most common sources of visual accessibility problems in government video, and they often go unreviewed because they feel like background assets rather than content.

The good news is that most issues are straightforward to catch once you know what to look for. This article explains the WCAG standard that applies, walks through the most common problem areas in government video production, and gives you a practical review process you can apply to any asset in your library. A downloadable checklist is available at the end of this article.

Think of this review as part of your regular production workflow—not a special project. Most government video libraries rely on a small number of reusable template assets. Reviewing them once, and keeping them current, goes a long way toward making your content accessible to everyone who watches.

The standard that applies: WCAG 2.3.1

WCAG 2.1 Success Criterion 2.3.1, "Three Flashes or Below Threshold" (Level A), states that content should not flash more than three times in any one-second period—unless the flashing falls below specific luminance and color thresholds defined in the standard.

Level A is the baseline tier of WCAG. Success criteria at this level address the most serious potential harms, which is why flashing content sits here alongside requirements like providing text alternatives for images. For people with photosensitive epilepsy, and others who experience physical reactions to rapid visual changes, content that exceeds the flash threshold can trigger seizures. This isn't a hypothetical edge case—it's a documented harm that informed the standard's design.

What exactly counts as a flash? WCAG defines it as a pair of opposing changes in relative luminance where the darker image has a relative luminance below 0.80 and the change is at least 10% of maximum luminance. A red flash is any pair of opposing transitions involving saturated red. Both types count toward the three-per-second limit. In practical terms: any element that strobes, pulses rapidly, or alternates between high-contrast states multiple times per second should be flagged for review.

Common problem areas in government video

Government media teams frequently work with assets inherited from vendors, previous staff, or template libraries. These were often built for visual impact—not accessibility. Here are the elements that most often need attention.

• Station IDs and channel bumpers. These short clips—often three to five seconds—can pack in a lot of motion. Animated logos that flash into frame, high-contrast color sweeps, and rapid zoom sequences are common in broadcast-style openers. Because station IDs play before every recording, a single problematic bumper creates a risk across your entire archive. This makes them the highest-priority asset to review.

• Meeting intro sequences. City hall footage, aerial shots, and animated text reveals are common in government meeting openers. Watch for rapid cross-dissolves between bright and dark footage, or animated text that appears to strobe as letters build on screen one by one.

• Animated lower thirds and name slates. Lower thirds that fly in or pulse to draw attention can cross the flash threshold if the animation is fast enough. Lower thirds using high-contrast color combinations—bright yellow on black, white on deep blue—are especially worth scrutiny, because a fast animation creates a strong luminance shift that may meet the definition of a flash.

• Slide transitions in recorded presentations. When staff present with PowerPoint or Google Slides and the session is recorded, those transitions become part of the video. Many default transitions—wipes, flashes, and checkerboard patterns—can be problematic. The checkerboard transition is particularly risky: it combines rapid alternating contrast with a pattern that covers a large portion of the screen simultaneously.

• Animated logos and watermarks. A static "bug" in the corner of the screen is rarely an issue. An animated version that pulses or flickers may contribute to flash problems, particularly when it appears alongside other animated content at the same time.

• Sparkle, glare, and light flare effects. Decorative effects added in post-production—lens flares, sparkle overlays, spotlight sweeps—are easy to overlook because they feel like polish. They're also one of the most common sources of red flashes, since light effects frequently use warm yellow-to-red color palettes.

The review process

Reviewing video for visual accessibility issues doesn't require expensive software. A structured approach with free tools is sufficient for most government use cases.

1. Inventory your reusable assets. Before reviewing individual recordings, identify the template assets used across your library. Your goal is to find elements that repeat—because improving one asset improves every recording that contains it. Make a list of your standard elements: station ID, meeting intro, outro card, lower third templates, and any animated overlays. These are your highest-priority review targets. A problematic station ID that plays before every city council meeting creates a risk at scale; fixing it once addresses the problem everywhere.

Screen for flashing content. Play each asset at full speed, paying close attention to any rapid visual changes. Your own eyes are a reliable first pass—if something looks like it's strobing or flashing, it warrants closer analysis. For a more precise check, use the free Photosensitive Epilepsy Analysis Tool (PEAT), developed by the Trace Research & Development Center at the University of Maryland. PEAT analyzes video files and flags content that exceeds WCAG flash thresholds. Upload your file, run the analysis, and review the output report. Any flagged segments should be modified or removed before the asset goes back into rotation.

1. Check contrast and readability. Flashing isn't the only visual risk. Text overlays—lower thirds, title cards, on-screen captions—need a minimum contrast ratio of 4.5:1 between text and background to support WCAG 1.4.3 (Contrast, Minimum). Non-text elements like icons and graphic borders need at least a 3:1 ratio to support WCAG 1.4.11 (Non-text Contrast). For each text element in your video assets, identify the text color and the background color beneath it. Use a free tool like the WebAIM Contrast Checker to enter the hex values and verify the ratio. If the element appears over video footage rather than a solid background, add a semi-transparent dark box behind the text. This creates a consistent, verifiable contrast surface regardless of what's playing behind it.

2. Evaluate motion for purpose. Beyond the flash threshold, consider whether animations in your assets serve a clear communicative purpose or just add visual complexity. Purely decorative animations—a spinning logo, a particle effect background, an animated watermark with no identification function—can disorient people with vestibular disorders or cognitive disabilities, and they render poorly for viewers on slower connections. A simple question helps here: what does this animation communicate? If the answer is "nothing," it's a candidate for simplification. Reducing unnecessary motion often improves the experience for a broader audience than you'd expect, including people watching on mobile or in noisy, low-attention environments.

3. Document your review. Once you've reviewed an asset and confirmed it passes—or modified it to pass—record that in your asset log. Note the asset name and version, the review date, who reviewed it, and which tools were used. This creates an activity trail that supports your agency's ongoing accessibility recordkeeping. When you update an asset, replace it everywhere it's used. A revised station ID doesn't help if old recordings continue to air the original version in future broadcasts.

Real-world application: city council meeting production

Consider a typical city council meeting recording workflow. The production technician plays the station ID, rolls the intro sequence, and the meeting begins. Lower thirds appear as speakers are recognized. After the meeting ends, the recording is exported and uploaded to the city website.

Each of those moments—the station ID, the intro, every lower third—is a point where a visual accessibility concern can enter the final product. A practical review schedule might look like this: new or vendor-supplied assets go through the review process before entering regular rotation; existing assets are reviewed annually or when a concern is raised; meeting recordings are spot-checked quarterly; and full reviews happen when production software or templates are updated.

This doesn't need to be a great effort. Most government media operations use a small, stable set of template assets. Building visual review into your normal production cycle—rather than treating it as a separate accessibility project—keeps the workload manageable and consistent over time.

MediaScribe integration

Reviewing your video assets for visual accessibility issues pairs naturally with the caption review process you already do in MediaScribe. When you archive recorded meetings through Cablecast or publish video to your agency's website, the visual elements of that content—intros, lower thirds, transitions—accompany every caption-reviewed file you produce. MediaScribe's AI Audio Description feature can also help surface visual content that may need additional accessibility attention, such as complex on-screen graphics or text in presentation slides that captions alone wouldn't convey. In the next article, we'll walk through setting up accessible in-room caption displays step by step.

Summary

• WCAG 2.3.1 (Level A) applies to all digital video content, including station IDs, meeting intros, slide transitions, and animated overlays—not just web pages.

• The most common problem areas in government video are station IDs, meeting intro sequences, slide transitions, animated lower thirds, and decorative effects like light flares.

• A structured review process—inventory reusable assets first, then screen for flashing, check contrast, evaluate motion for purpose, and document your work—keeps the effort manageable.

• PEAT provides automated flash threshold analysis, but always pair it with manual review by a trained staff member.

• Reviewing and updating reusable template assets has the highest impact, because one fix carries through every recording that uses that asset.

• Documenting your review process, including tools used and outcomes, supports your agency's ongoing accessibility recordkeeping.

• Reducing unnecessary motion improves accessibility for people with vestibular disorders and cognitive disabilities, and often improves the viewing experience for a broader audience as well.

Downloadable checklist

The Video visual accessibility review checklist is available as a PDF download. Use it to guide your review of any video asset before it enters regular rotation. The checklist covers asset documentation, flashing content analysis, contrast verification, motion review, and recordkeeping—with a section for escalating concerns that can't be resolved in-house.