Skip to main content

Why I stopped using ASCII art

Posted in Accessibility

I love those old-school ASCII art drawings. They’re full of character and pre-emoji charm. Remember using a colon and a closing bracket for a smiley face? Or my personal favourite, the shrug:

¯\_(ツ)_/¯

Visually, it has a lot going for it, but to a screen reader users (apologies if you’ve just listened to that via a screen reader!) it’s gibberish:

Space with a combining macron backslash underscore comma underscore slash space with

I should mention that I’ve never actually typed all of those brackets, slashes and underscores; I map a shortcut like sshrug to a text snippet.

What I’m doing instead

Instead of burdening non-sighted people with all of those ASCII characters, I’m sticking to emojis:

🤷‍♂️

That one conveys the same visual meaning as the ASCII shrugger but is much more understandable for screen reader users:

Man shrugging

Subscribe

I send a newsletter on the last day of every month, containing:

  • A roundup of the articles I’ve posted
  • A hot pick from my archives
  • Some interesting posts from around the web

I don’t collect any data on when, where or if people open the emails I send them. Your email will only be used to send you newsletters and will never be passed on. You can unsubscribe at any time.

More posts

Here are a couple more posts for you to enjoy. If that’s not enough, have a look at the full list.

  1. It’s good to make mistakes

    As a designer and developer I’ve made countless mistakes, but that’s part of the reason I’m good at what I do.

  2. Focus appearance explained

    There’s some great stuff coming up in WCAG 2.2, but there’s one rule that’s particularly difficult to understand, so here it is in a bit more detail.