This article explains how to author accessible content and maintain multi-channel consistency in Messages XR Enterprise, including WCAG 2.1 Level AA standards, alt-text requirements, and voice script best practices.
💡Quick answers
- Does Messages XR Enterprise follow WCAG accessibility guidelines? Yes, the platform is designed to support WCAG 2.1 AA compliance for both the admin interface and delivered content.
- Is alt-text required when inserting images into messages? Yes, all images inserted into messages should include descriptive alt-text so screen readers can convey the content to visually impaired recipients.
- Does Channel Equity mean every delivery method should carry equivalent content? Yes, Channel Equity means the core message must be accessible and complete across email, SMS, voice, and other channels — not just one.
- Why should abbreviations be avoided in voice message scripts? Text-to-speech engines may mispronounce abbreviations, causing confusion for recipients who rely on voice delivery.
- Is there a minimum color contrast ratio required for accessible MXRE email templates? Yes, WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
- Who is responsible for ensuring accessibility in MXRE communications? District administrators and content authors share responsibility; the platform provides tools, but accessible content creation is the sender's obligation.
Part 1: Authoring accessible content
The way you draft your messages determines whether assistive technologies can interpret your information.
Include descriptive alt-text for images
- Provide text alternatives: Whenever you insert an image, include alt text so screen readers can describe it to users with visual impairments.
- Be concise and functional: If the image contains vital info (like a flyer), summarize it. Mark decorative items to be skipped.
- Avoid "image of": Start descriptions directly, e.g., "Students gathered for the district science fair."
Use descriptive action links
- Avoid generic phrases: Do not use "click here" or "read more."
- Configure descriptive links: Use names like "View the Emergency Procedures PDF" so users understand the destination.
Audit video captions and notification logic
- Review auto-captions: Verify captions for accuracy to support individuals who are deaf or hard of hearing.
- Create action-oriented alerts: Use clear language like "Tap to sign the permission slip" in app notifications.
Verify color contrast in templates
- Check contrast ratios: Ensure custom button or background colors meet the 4.5:1 ratio for WCAG compliance.
- Maintain legibility: Urgent alerts must be readable in high-glare environments or for users with low vision.
Part 2: Ensuring multi-channel consistency
Accessibility is about ensuring the experience is consistent across email, text, voice, social media, and app notifications.
Optimize voice scripts for pronunciation
- Type out words completely: Avoid abbreviations in TTS scripts. Type "Thursday" instead of "Thurs" and "Street" instead of "St."
- Ensure clarity: Full words ensure the text-to-speech engine pronounces the message correctly for audio listeners.
Prioritize information hierarchy
- Lead with vital info: Place dates, times, and locations at the very top of your message.
- Optimize for SMS: Putting the "who, what, and where" first ensures the core message is accessible even on limited-formatting channels.
How we support assistive technologies
- Screen readers: Optimized for VoiceOver, NVDA, and JAWS.
- Touch targets: Interactive elements meet the 44x44 pixel minimum for motor impairments.
- Structure: We use logical layouts so content is presented clearly across all devices.
Our shared responsibility in accessibility
Because MXRE allows for custom templates and scripts, accessibility is a shared responsibility. We remain committed to improving the foundation while your team’s content authoring ensures consistent messaging for every channel.