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

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...

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

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

If you’re working on Gmail, or any major email client: help us make this better.

Read our article "Email clients are stripping out accessibility at the expense of user needs" to learn more about this:
emailmarkup.org/en/blog/2025...

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

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...

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

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.

Read more about this in our 2025 email accessibility report:
emailmarkup.org/en/reports/a...

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.

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.