iiinova — where your digital self keeps evolving

Email Markup Consortium @emailmarkup.org · 26/05/2026

100% triggered at least one automated accessibility failure. These findings indicate that platform defaults and generated markup have enormous influence over accessibility outcomes at scale.

120

Email Markup Consortium @emailmarkup.org · 26/05/2026

For the first time, the 2026 Email Accessibility Report audited newsletter and marketing platforms with built-in email builders. We analyzed: • 6,909 #Substack emails • 2,189 @beehiiv.com emails • 1,468 #Shopify Email campaigns

mremail.dev

Accessibility Report 2026 | Email Markup Consortium

Email Markup Consortium Accessibility Report - 2026

142

Email Markup Consortium @emailmarkup.org · 21/05/2026

While developers play a role here, the reality is this is a systemic ecosystem problem across senders, tooling and email clients. Accessibility needs to become part of the authoring and QA process itself, rather than a post-build checklist.

041

Email Markup Consortium @emailmarkup.org · 21/05/2026

The result: • 99.88% triggered Serious or Critical accessibility issues • Only 8 emails passed all automated checks • Most failures were basic, machine-checkable issues

131

Email Markup Consortium @emailmarkup.org · 21/05/2026

The 2026 Email Accessibility Report is now live! We analyzed 376,348 HTML emails across industries, geographies and platforms. mremail.dev/3PFRAR8 #GAAD #EmailGeeks

mremail.dev

Accessibility Report 2026 | Email Markup Consortium

Email Markup Consortium Accessibility Report - 2026

151

Email Markup Consortium @emailmarkup.org · 12/12/2025

In 2022, we began our Data Collection project with a clear vision for how this data could benefit the ecosystem starting with our annual accessibility reports. Today, we’re excited to announce the next major step in that vision: The Email Markup Database emailmarkup.org/en/blog/2025...

emailmarkup.org

Announcing the Email Markup Database | Email Markup Consortium

A comprehensive, continuously updated repository of how real-world emails are built. Real usage metrics from real emails covering HTML and CSS features, external assets and more.

140

Email Markup Consortium @emailmarkup.org · 13/10/2025

Link to the "Accessibility in Email Clients" section in our 2025 Accessibility report: emailmarkup.org/en/reports/a...

emailmarkup.org

Accessibility Report 2025 | Email Markup Consortium

Email Markup Consortium Accessibility Report - 2025

020

Email Markup Consortium @emailmarkup.org · 13/10/2025

This kind of openness and collaboration benefits everyone in the email ecosystem. We’d love to see more email clients follow Proton Mail’s lead in sharing accurate, transparent data with the community. emailmarkup.org/en/blog/2025...

emailmarkup.org

Proton Mail rise up the accessibility rankings | Email Markup Consortium

We’ve updated our 2025 Accessibility Report after Proton Mail updated its data on “Can I Email?”. It’s a reminder of how transparency and collaboration can push the email industry forward.

131

Email Markup Consortium @emailmarkup.org · 13/10/2025

Proton Mail (@proton.me) noticed that some of their data on "Can I Email?" was outdated, and took the initiative to update it themselves. As a result, our 2025 Accessibility Report now reflects a much more accurate picture of Proton Mail’s strong accessibility support.

131

Email Markup Consortium @emailmarkup.org · 23/06/2025

No need to reinvent the wheel. Just a shared, interoperable way to explicitly set the preview text.

010

Email Markup Consortium @emailmarkup.org · 23/06/2025

Our latest blog post explores how preview text could be standardized using a metadata-based solution, which aligns with how Google's Gmail and Yahoo Mail already support Schema structured data in emails today. emailmarkup.org/en/blog/2025... #Interoperability #standards #EmailClients

emailmarkup.org

How email clients can improve preview text with one simple tag | Email Markup Consortium

Email clients can improve preview text by supporting a standard HTML meta tag; no hacks needed.

120

Email Markup Consortium @emailmarkup.org · 23/06/2025

For years, email developers have relied on invisible spacing hacks to influence what appears alongside the subject line in the inbox. But there can be a cleaner, more consistent approach: a simple meta tag.

130

Email Markup Consortium @emailmarkup.org · 10/06/2025

Sign the EMC supporters list and show the industry Email Accessibility matters! Add your name: emailmarkup.org/en/supporters/ #a11y

emailmarkup.org

Supporters | Email Markup Consortium

Supporters of the Email Markup Consortium

032

Email Markup Consortium @emailmarkup.org · 03/06/2025

Respecting user preferences is non-negotiable for inclusive digital communication. It's time email clients enable developers to build more accessible HTML emails.

120

Email Markup Consortium @emailmarkup.org · 03/06/2025

Accessibility in email is hard enough. When email clients block even the most basic accessibility features, they’re not limiting creativity; they’re limiting access.

120

Email Markup Consortium @emailmarkup.org · 27/05/2025

We're calling on Gmail and other major email teams to take accessibility seriously: Let developers build inclusive experiences. Respect user preferences. Read more about this in our 2025 email accessibility report: emailmarkup.org/en/reports/a...

emailmarkup.org

Accessibility Report 2025 | Email Markup Consortium

Email Markup Consortium Accessibility Report - 2025

020

Email Markup Consortium @emailmarkup.org · 27/05/2025

This isn't just a missed feature; it's a barrier. It may even have legal implications. Email clients are disregarding OS-level accessibility settings, and forcing users to endure experiences that may be uncomfortable and harmful. Impacting the sender's the ability to communicate with their audience

120

Email Markup Consortium @emailmarkup.org · 27/05/2025

These preferences exist for a reason: to make digital content safer, more readable, or usable for a large percentage of people in this world. Yet as shown in our 2025 Accessibility Report, Gmail and other clients completely strip out the code developers use to detect and adapt to these preferences.

110

Email Markup Consortium @emailmarkup.org · 27/05/2025

Respecting user preferences is a basic accessibility principle, but Google's Gmail makes it nearly impossible for developers to do this. Email clients should enable developers to query the user's system or browser-level settings, like reduced motion or color scheme.

160

Email Markup Consortium @emailmarkup.org · 23/05/2025

We urge public sector teams to audit their email templates, adopt accessibility best practices, and build emails with inclusion in mind. When accessibility is overlooked, critical public information becomes inaccessible to the people who may need it most.

130

Email Markup Consortium @emailmarkup.org · 23/05/2025

Every government email message in our dataset failed to comply with accessibility requirements. This creates significant barriers for users who rely on assistive technologies. Governments have a responsibility to ensure communications, including email, are accessible to as many people as possible.

130

Email Markup Consortium @emailmarkup.org · 15/05/2025

It's that time of year again. To celebrate Global Accessibility Awareness Day we've released our annual email accessibility report. Unfortunately less than 0.01% of emails passed all automated test, so this is a call to action to do better. emailmarkup.org/en/reports/a... #GAAD #EmailGeeks #A11y

emailmarkup.org

Accessibility Report 2025 | Email Markup Consortium

Email Markup Consortium Accessibility Report - 2025

142

Reposted by Email Markup Consortium

Hussein Al Hammad | حسين آل حماد @hussein-alhammad.com · 09/12/2024

This is a fun frontend challenge. You don't have to be interested in email to find this interesting and discuss it with us.

021

Email Markup Consortium @emailmarkup.org · 12/12/2024

It is not that the challenges are purely different, but rather how widely different your choices to address them are, and how an email developer sometimes has to carry the responsibility to address something user agents (email clients) failed their users by not addressing.

010