Accessibility isn’t a checkbox. It’s an ongoing practice that spans both the technology behind a product and how it’s used day to day.
Finalsite communications tools, including Finalsite’s Messages XR Enterprise (MXRE), are built with WCAG 2.1 Level AA standards in mind, providing a strong foundation for accessible digital communications across channels. Because these tools are used to create and deliver messages, accessibility is also influenced by how content is authored and how messages are configured. Schools and districts play an important role in ensuring communications are clear, readable, and usable for all audiences.
In communications, this is vital because schools share time-sensitive information, and every family must be able to receive and understand those messages regardless of how they access them. Use this guide to ensure your communications maintain Channel Equity so that a parent receiving a text message gets the same vital info as someone reading a rich-text email.
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.