Want to know everything about sending a perfect welcome email? Read our latest article. đź‘‹

Read Post

This site uses cookies to provide you with a great user experience.


Here's how to get started:


This is the first in a welcome series when a user joins Glitch.com, a Google-docs for code. We're focused on giving new users easy ways to jump into coding, so we start with two ready-to-go projects.

A friendly community is a key piece of Glitch, so we try to make concepts easy to understand, introducing users to "Glitch Tips" (with the Glitch Witch) and easy access to support. Not ready to code? No problem - we give people a way to find inspiration and cool apps as an off-ramp. From a coding perspective, it's wildly mobile-friendly thanks to SaaS, Grunt, and a few other tricks.


How does this look across email clients?

Here’s how Glitch's emails render in the most popular email clients. Are yours rendering as designed? Find out with a free trial of Litmus.

How accessible is this email?

Looks aren’t everything. Does this email follow key accessibility best practices? Our friends at Litmus ran the test.

  • Email headings should be well structured. This will help screen readers easily navigate content.

  • Specifying "alt text" for these images helps screen readers describe the image.

  • Text to voice recording and transcript for hearing impaired.

  • Table roles should be clearly defined. This helps screen readers determine how to interpret the table.

  • Emails should have a "meta content-type" and defined character set.

  • Without a [lang] attribute, screen readers will assume the email is in the default language the subscriber chose when setting up their screen reader. If your email is not in that user’s language, the screen reader may not accurately transcribe your message.

  • Larger paragraphs of text should be left-justified to improve readability for some readers.

Share this ish