Hussein Al Hammad | حسين آل حماد

🎉 Great news folks, the good people at Gmail have finally fixed the forced dark mode issue. In both the iOS and Android apps 🎉 They now support setting the color-scheme meta tag prevent the forced dark colors being used <​meta name="color-scheme" content="light only" /> #EmailGeeks

Me: How do I implement x? AI: Option 1 (recommended) [explanation...] Option 2 [explanation...] "I actually prefer this approach because it's cleaner."

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.

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

The Email Markup Database is live! Did you know that ~20% of emails collected still use the <center> element but only 0.5% of emails use <picture>. Well you do know, and there is loads more exciting information to find as you dig in database.emailmarkup.org

Real usage metrics from 1M+ real-world emails. The Email Markup Database is a major step toward a more transparent and collaborative ecosystem. With this level of data, we can identify gaps and have constructive discussion on how email clients and ESPs can evolve.

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.

This is grotesque. I lost any love for Vercel & Next years ago, but seeing him cozy up with genocide in Gaza — is beyond words. I feel for the employees. The horrifying truth: businesses that worked with the Nazis didn’t fall to capitalism. It’s down to us, we have to take our business elsewhere.

There’s never been a better time to switch from Next.js to Astro nitter.net/rauchg/statu...

🔥 I have news! After a 1y hiatus, I’m once again leading this year’s #StateOfHTML survey, thanks to generous funding by Google. ❤️ 🙋🏽‍♀️ Is there is an HTML feature or Web API you're dying to see progress on? Suggest it and it could be included! [1/2] lea.verou.me/blog/2025/de...

A more hopeful, nuanced take on programming and AI medium.com/@kt149/githu...

Still a week left to take the State of CSS survey! The survey hasn't got as many responses as last year, so any help sharing will be much appreciated :) survey.devographics.com/en-US/survey...

Email preview text has never had a proper spec, but it could. Google's Gmail and Yahoo Mail already support Schema structured data. Adding support for a standardized metadata-based preview text isn't a technical leap; it's the natural next step.

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

Web sites with a Facebook pixel were communicating with local native apps (Instagram, Facebook, maybe WhatsApp) to log (and attribute) incognito web browsing activity. Write-up: localmess.github.io Story: english.elpais.com/technology/2...

The 2025 State of CSS survey is now open! survey.devographics.com/en-US/survey...

Does anyone else "feel the clipboard" at the tip of their fingers after they copy something on their computer?

It's hard to reconcile the excellence of Google Chrome with the limited accessibility support in Gmail. We know Google has the talent and track record; so why not bring that same energy to email?

In some environments, change can only happen mid air hussein-alhammad.com/blog/2025/05...

Government communications are often required by law to be accessible. Yet 100% of the emails we tested failed basic automated accessibility tests. #A11y

Following on from the @emailmarkup.org Accessibility Report yesterday. If you support the work we're doing to make email markup more accessible, more consistent and all round better. Please add your name to the list. emailmarkup.org/en/supporters/ #EmailGeeks

We've just put our the latest Email Accessibility Report. There has been some improvement from previous years, but the results are still pretty dire. So today on #GAAD please take a moment to look at fixing at least one thing in your emails.

Today is GAAD, a good opportunity to reflect on the state of accessibility in the email ecosystem (email clients, ESPs, build tools, developers). Looking at real-world data, the sad truth is the whole ecosystem is failing the recpients - the most important party of the ecosystem.

This is a great example of how standards make a massive difference. Dealing with accessibility issues in web dev can feel like "easy mode" in comparison to email dev where there is zero standards when it comes to HTML messages.

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