The email ecosystem is failing accessibility at every layer (senders, platforms, and clients) and nothing is improving.
The Email Markup Consortium analyzed 376,348 HTML emails sent between May 2025 and May 2026 and found that all but eight contained serious or critical accessibility issues. The failure rate is effectively unchanged from 2025. EMC calls it a “technical standstill.”
Five years of annual reports. Hundreds of thousands of emails analyzed. Nothing has changed.
EMC 2026 accessibility report
Platform audit — none passed: Substack (6,909 emails) · Shopify (1,468 emails) · Beehiiv (2,189 emails)
Source: Email Markup Consortium, Accessibility Report 2026
Fixable
Most of what is failing is machine-checkable and cheap to fix:
- Add lang=”” to your email body tag, matching the language of your content, i.e., lang=”en” for English, lang=”fr” for French, lang=”es” for Spanish. (Missing in 95.66% of emails.)
This tells screen readers which language to read in. Getting it wrong is almost as bad as leaving it out. - Add dir=”ltr” to your email body tag if your language reads left to right (English, French, Spanish). Use dir=”rtl” for right-to-left languages like Arabic or Hebrew. (Missing in 97.41% of emails.)
This tells assistive technology which direction to read the text. - Add role=”presentation” to any table used for layout purposes — not for data. (Missing in 83.78% of emails.)
This tells screen readers to ignore the table structure and just read the content. - Add alt=”” to every image. (Missing in 47.88% of emails, classified as critical.) If the image adds meaning, describe it in plain language. If it is purely decorative, leave the attribute empty but keep it there.
Leaving it out entirely means a screen reader may read out the file name instead.
It is possible. Three brands, Customer.io, NaomiWest.ca, and Noble Panacea, passed every automated check in the 2026 report.
Platforms are not helping
EMC audited emails sent through Substack, Shopify, and Beehiiv this year. None passed. If your organization sends through any major platform, assume the platform is part of the problem. If your platform does not give you access to the underlying markup, raise it with the platform directly, or factor accessibility support into your next platform evaluation.
If your organization falls under Canada’s new digital accessibility regulations, email documents published on public-facing platforms are in scope starting June 2028. The same issues the EMC flags (missing language attributes, unlabelled images, inaccessible markup) apply.
Email clients compound the issue
EMC expanded its client benchmark to 37 feature tests this year, covering semantic HTML, ARIA, focus states, and language attributes. No client supported all 37.
- Outlook for Windows scored 11 out of 37.
- Gmail scored between 15 and 17 depending on the platform.
- Apple Mail on macOS led at 34.
Even a fully accessible email can break when the reader opens it in Outlook, Gmail, or Apple Mail.
Do not rely on tools alone
Automated tools help, but they do not catch everything. Even the eight emails that passed all the checks still had problems a human reviewer caught, like image descriptions that did not make sense or text that was too small to read. EMC also notes that AI may eventually help evaluate alt text quality and link context, but it is not a substitute for human review yet.
The structural fixes listed above address what machines can check. Cognitive accessibility (clear subject lines, plain language in the body, consistent layout) is the layer tools can’t evaluate.