Amazing! What will this mean to me, then?īasically, it means Gmail won’t be the main cause of your coding problems anymore (at least for a while).

What this means, overall, is that there won’t be a need to use the aria-labelledby hack anymore. Combined with media queries, this is significant step forward in the battle to conquer responsiveness across all devices. This is a huge improvement and will have a massive impact on the time spent coding an email. By doing so, Gmail gives developers the opportunity to finally move away from the inline styles. Gmail has also announced that they will start supporting embedded styles, including classes and IDs, which were previously stripped. Now, stacking different blocks in your multi-column designs or targeting different screen sizes will be way simpler.Īnd that’s not all. Well, for starters, Gmail has announced they will start supporting media queries, which will significantly ease the pain of coding responsive emails that look beautiful on every device. A workaround for this is to rely on the aria-labelledby hack to target elements that you can’t address with the classic “class” and “id” attributes, like our open source markup language MJML does. This ultimately means that developers need to specify the formatting of every tag they want to style by using the always-reliable-but-incredibly-time-consuming inline styles. In its attempts to protect users against security threats, Google’s email solution strips out most of what’s in the tags, including that embedded style. While with other webmail providers it just takes a few lines of code to add embedded styles at the top of your HTML file to ensure your message is consistently formatted the way you want across all email clients and devices, this is not an option with Gmail. But Gmail’s restrictions are not limited to media queries.

Mjml code for a line