Understanding Presets and Accessibility Outcomes

How Presets Help You Meet WCAG Requirements

You're configuring MediaScribe to caption your meetings. You're also implementing accessibility solutions that must meet specific Web Content Accessibility Guidelines (WCAG) 2.1 Level AA criteria. Every meeting you caption represents a commitment to serve your entire community—including residents who are deaf or hard of hearing, non-native English speakers, and people who process information better with text support.

Presets bundle your configuration settings together so you can quickly switch between different meeting scenarios while maintaining WCAG compliance. Think of presets as templates that package your language choices, output formats, and vocabulary customizations into reusable configurations. Once you've created a preset for city council meetings, you can apply those same settings with a single click next week, next month, and next year.

This article explains which WCAG success criteria your preset configurations address. It also helps you choose the right settings for different situations. By the end, you'll understand how to build presets that translate legal requirements into practical, repeatable workflows.

The Connection Between Presets and WCAG

MediaScribe presets contain four tabs of settings. These settings directly impact your ability to meet accessibility requirements:

Basic Info establishes naming and organizational structure for your captions and recordings. This doesn't directly address WCAG criteria. However, proper naming helps you manage and archive accessible content effectively.

Languages determines which languages receive live captions and translations. This directly supports WCAG Success Criterion 1.2.4 (Captions Live) by ensuring real-time text alternatives for audio content.

Outputs controls how captions are delivered to your audience. You can configure up to three separate outputs, each serving a different purpose. Closed captions let viewers toggle captions on and off. Open captions are always visible and include a language selection. In-room displays show captions live in the meeting room with template and language options. These choices affect how you meet WCAG 1.2.4 requirements and serve different viewing needs.

Vocabulary improves caption accuracy for specialized terms, proper names, and local terminology. More accurate captions better fulfill the intent of WCAG 1.2.4. This criterion requires captions to be "accurate enough to understand program content."

Legal Context: WCAG Requirements for Government Media

The April 26, 2027 deadline under ADA Title II requires government entities to meet WCAG 2.1 Level AA standards for all web content and digital services. This includes video content whether it's streamed live or posted as a recording.

Your preset configurations directly address the WCAG success criteria that apply to government meetings and video content:

Success Criterion 1.2.4: Captions (Live) - Level AA
"Captions are provided for all live audio content in synchronized media."

In plain language: Every live meeting you broadcast must have real-time captions. This applies to city council meetings, public hearings, county board sessions, and any other meeting the public can watch as it happens. Your preset's language and output settings determine how you fulfill this criterion.

Success Criterion 1.4.3: Contrast (Minimum) - Level AA
"The visual presentation of text and images of text has a contrast ratio of at least 4.5:1."

In plain language: Caption text must be readable. MediaScribe captions use black text on a white background, which meets this standard with maximum contrast (21:1 ratio). This ensures captions are readable for everyone, including people with low vision or color vision deficiencies. While header and footer colors can be customized for branding, the caption text itself maintains this high-contrast standard.

Success Criterion 3.1.2: Language of Parts - Level AA
"The human language of each passage or phrase in the content can be programmatically determined."

In plain language: When you provide captions in multiple languages, the technology needs to mark which language each caption stream uses. Screen readers and other assistive technology rely on these language markers to function properly. When your preset includes translation outputs, MediaScribe marks each caption stream with its language.

Success Criterion 1.2.2: Captions (Prerecorded) - Level A
"Captions are provided for all prerecorded audio content in synchronized media."

While presets focus on live captioning, every live meeting you caption creates a recording. Those recordings become prerecorded content that must also meet WCAG standards. Your preset's recording name template helps you organize this content for later accessibility review and compliance verification.

Choosing the Right Preset for Different Situations

Different meeting types have different accessibility needs. Here's how to match your presets to common government scenarios:

Public city council meetings

Accessibility requirement: Must provide live captions for broadcast stream and in-person attendees. May need to serve multilingual community.

Recommended preset configuration:

• Languages tab: Set source language to English. Add Spanish translation if serving Spanish-speaking community.

• Outputs tab: Configure Output 1 as closed captions for broadcast stream (language determined by Languages tab settings). Configure Output 2 as open captions in Spanish if providing translation to Spanish-speaking viewers. Configure Output 3 as in-room display using the Default template in English for council chambers.

• Vocabulary tab: Add city department names, local street names, council member names, and frequently discussed local terms.

WCAG fulfillment: This configuration meets Success Criterion 1.2.4 by providing live captions in both broadcast and in-person viewing environments. Translation support addresses multilingual accessibility needs beyond minimum WCAG requirements.

Internal staff meetings

Accessibility requirement: Must provide captions for employees with hearing disabilities or who benefit from text alternatives.

Recommended preset configuration:

• Languages tab: Set source language to match meeting language (typically English).

• Outputs tab: Configure Output 1 as closed captions so participants can toggle captions on or off based on their needs.

• Vocabulary tab: Add agency-specific acronyms, project names, and technical terms relevant to your department.

WCAG fulfillment: Closed captions meet Success Criterion 1.2.4 while giving participants control over caption visibility. This respects different accessibility needs and preferences.

Public hearings with translation requirements

Accessibility requirement: Must provide captions and may need real-time translation for non-English speakers.

Recommended preset configuration:

• Languages tab: Set source language and add required translation languages based on community language access requirements.

• Outputs tab: Configure Output 1 as closed captions for the primary language. Configure Output 2 as open captions in Spanish (or other translation language). Configure Output 3 as in-room display using the Default template in English.

• Vocabulary tab: Include technical terms related to hearing subject matter (zoning terminology, environmental terms, legal references).

WCAG fulfillment: Multiple language outputs meet Success Criterion 1.2.4 for English content and extend accessibility to non-English speakers. Language markup supports Success Criterion 3.1.2.

Emergency public announcements

Accessibility requirement: Critical information must reach all community members immediately, including people who are deaf or hard of hearing.

Recommended preset configuration:

• Languages tab: Set source language and primary translation language.

• Outputs tab: Configure Output 1 as open captions (always visible) in the primary language to ensure no one misses critical safety information. Add Output 2 as open captions in Spanish if serving multilingual community.

• Vocabulary tab: Add emergency terminology, evacuation route names, and local landmark names.

WCAG fulfillment: Open captions (always visible) meet Success Criterion 1.2.4 and ensure critical information reaches everyone. The always-visible approach eliminates any risk of captions being accidentally turned off during emergency communications.

Decision Guide: Selecting Your Preset Settings

Use this guide to make informed decisions about preset configuration:

When choosing between closed and open captions:

Closed captions give viewers control. They can toggle captions on when needed and off when not needed. This works well for regular meetings where viewers are familiar with video players and know how to activate captions. Most internal meetings and routine public meetings benefit from closed captions. Note that closed captions use the source language from your Languages tab—you select the language there, not in the output configuration.

Open captions are always visible. No one can turn them off. When you configure an output as open captions, you select which language that output displays. This gives you flexibility to provide different language streams as separate outputs. Use open captions for emergency announcements where missing information could endanger public safety. Also use them in situations where viewers might not know how to enable closed captions, such as community events where many attendees are unfamiliar with the technology.

Consider your audience's technical comfort level. A city council meeting broadcast to regular viewers can use closed captions. A one-time community forum about storm preparedness should use open captions.

When deciding whether to add translations:

Legal obligations drive many translation decisions. If your agency has a language access policy, those requirements determine which translations you must provide. The Department of Justice provides guidance on when language access becomes legally required based on the number and proportion of limited English proficiency residents you serve.

Even without legal requirements, consider your community's language demographics. If 15% of your community speaks Spanish as their primary language, providing Spanish captions serves a significant portion of your residents. If you regularly see Spanish speakers at public hearings, translation addresses a demonstrated community need.

Budget realities matter. Each additional language increases costs. Start with your most common need. Add other languages as budget allows and community demographics justify the investment.

When configuring in-room displays:

In-room displays serve attendees in your physical meeting space. Add this output type when you have people in council chambers, public meeting rooms, or hearing rooms who need caption access. Position displays where attendees can see them without blocking their view of speakers or presentation screens.

When you configure an output as in-room display, you select both the display template and the language. The template determines the visual layout and any header or footer branding elements. Caption text is always black on white background for maximum readability and WCAG compliance. Header and footer elements can be customized with your organization's branding colors, but these customizations must also meet WCAG 1.4.3 contrast requirements.

Test your selected template in your actual meeting room. Consider display size and viewing distance. Attendees sitting 30 feet from a display need larger text than those sitting 10 feet away.

When building your vocabulary list:

Start with proper names. MediaScribe's speech recognition accurately captures common English words but may struggle with unusual names. Add council members' names, department heads' names, and names of community organizations that appear frequently in discussions.

Add local terminology next. Your community has unique geographic names (neighborhood names, street names, park names, facility names) that don't appear in standard dictionaries. Include these in your vocabulary list with phonetic spellings when the standard spelling doesn't match pronunciation.

Technical terms specific to your agency's work improve accuracy significantly. Zoning categories, permit types, program names, and legal terminology all benefit from vocabulary customization. A coastal community needs terms like "FEMA flood maps" and "littoral zones." An inland agricultural county needs different terminology.

Update vocabulary based on actual performance. Monitor your live captions. When you notice consistent errors with specific terms, add those terms to your vocabulary list with correct spellings and phonetic guides. This iterative approach builds increasingly accurate caption output over time.

Maintaining Accessibility Through Preset Management

Creating appropriate presets is the first step. Maintaining compliance requires ongoing attention and regular review of both your preset configurations and the caption quality they produce.

Build a regular review schedule. Set aside time monthly to review caption accuracy. Watch portions of recent meetings. Read through caption transcripts. Look for patterns in errors. If you consistently see the same terms miscaptioned, your vocabulary list needs updates. If captions lag behind speech more than a few seconds, contact MediaScribe support to check your system configuration.

Update presets when circumstances change. Your agency doesn't stay the same. Staff changes bring new names to add to vocabulary lists. New initiatives introduce new terminology. Changes in community demographics may create needs for additional translation languages. When you begin serving a new language community, add translation outputs to relevant presets. When you move to a larger council chamber, verify your in-room display template works in the new space. When new council members join, add their names to vocabulary lists immediately.

Document preset purposes clearly. Use descriptive names that communicate function at a glance. "City Council - Public" immediately tells any authorized user what that preset does. "Emergency Announcements" clearly indicates when to use that configuration. "Internal Staff Meetings" eliminates confusion about appropriate settings. Good naming reduces the likelihood that someone will accidentally select the wrong preset.

Supplement preset names with internal documentation. Create a simple reference sheet that lists each preset name, describes when to use it, and notes any special considerations. Keep this reference sheet where staff can easily access it. Update it when you modify presets or create new ones.

Test presets before critical meetings. The night before a major public hearing is not the time to discover your preset doesn't work correctly. Test new presets in low-stakes situations first. Use them for internal meetings or work sessions before deploying them for important public meetings.

When you do use a preset for a high-profile meeting, verify outputs before the meeting starts. Check that captions appear on your broadcast stream. Verify in-room displays show captions clearly. Confirm translation outputs if you're providing them. This takes five minutes and prevents accessibility failures during critical public meetings.

Keep records of preset changes. When you modify a preset, note what you changed and why. These records help you troubleshoot problems later. They also support compliance documentation if you face accessibility complaints or audits. Simple notes like "Added council member Martinez to vocabulary list" or "Changed Output 2 from closed to open captions for emergency procedures" create a compliance trail.

Remember that presets are tools that support your accessibility goals. They don't guarantee compliance by themselves. Presets make it easier to configure your system correctly every time. They reduce the chance of human error in settings. They eliminate the need to reconfigure everything from scratch for each meeting. But you still need to verify that captions are actually working during live meetings and that recording quality meets standards for archived content.

MediaScribe Integration

MediaScribe's preset system lets you save and reuse configuration packages that address specific WCAG requirements. Each preset bundles language settings, output configurations, and vocabulary customizations. You can switch between meeting types with confidence that you're meeting compliance standards.

To manage presets, navigate to Settings → Presets. Click + New Preset to create a new configuration. Select an existing preset name to edit its settings. You can switch between presets at any time using the preset dropdown in the header.

Summary

Key takeaways:

• Presets bundle settings that directly address WCAG Success Criteria 1.2.4, 1.4.3, and 3.1.2

• Different meeting types require different preset configurations to meet accessibility requirements

• Closed captions give viewers control while open captions ensure visibility for critical communications

• Vocabulary customization improves accuracy and better fulfills WCAG caption quality requirements

• Regular review and updates keep your presets effective as your needs change

• Testing presets before critical meetings verifies compliance and prevents accessibility failures