Really interesting stuff!
25.02.2026 14:46
👍 0
🔁 0
💬 0
📌 0
Really interesting stuff!
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...
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...
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.
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
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.
Sign the EMC supporters list and show the industry Email Accessibility matters!
Add your name: emailmarkup.org/en/supporters/
#a11y
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.
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.
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.
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.
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.
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.
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
This is a fun frontend challenge. You don't have to be interested in email to find this interesting and discuss it with us.
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.
In this article, Sarah Gallardo discusses how different the accessibility challenges between web vs email dev are:
a11y.email/the-accessib...
How should a web app allow third-party HTML to make use of the CSS prefers-color-scheme media feature?
Mark Robbins (@goodemailcode.com) has some good ideas utilising modern CSS features. Join the discussion on GitHub:
github.com/email-markup...