A Bitmoji Steve angrily flipping a table. Four different colored QR codes are flung off the table.

They’re Ugly! They’re Ugly! Their Mama Says They’re Ugly! 

We need to talk about QR codes.

I know I’m a weirdo. I’m starting from that premise when I say that I do not like QR codes. To start: They’re ugly. They are never going to match a theme, except maybe in color. 

While I have increasingly come to appreciate form as well as function, the ugliness of QR codes is not my main issue. 

I hope you’ll take a few minutes to think about how you’re using QRs, and how you might be impeding access to information.

Problem #1: Phone Keyboards (And My Fingers)

Not too long ago I was in a large meeting room. A VERY important slide deck of resources was shared. And the only access point was a QR code. 

Friends, that’s not okay. 

I like taking notes. And I have fat fingers. Trying to thumb type on a phone touchscreen just doesn’t work for me. Even the best autocorrect in the world can’t make sense of the results of my meat paws smashing multiple keys at a time on a teeny virtual keyboard. 

So I need a way to access information through my computer. This is one way QR codes are a metaphorical rock in my metaphorical shoe. For folks on computers, QR codes are not user-friendly. 

Solution: We need to give the overly-wide-fingered among us options for accessing information using actual, real keyboards.

In Praise Of Short Links

There are SO MANY link shortening tools and services in the world. Whether you use TinyURL or Bitly or something else, it’s just as easy to make a short link as it is to make a QR code. 

And most link shorteners let you customize the back half of the link. This lets you create a name for your link, something the audience can remember and use to access your shared material without having to dig through a camera roll to find a picture of a QR code that may not have any context clues around it to help you know what that QR code even goes to. 

Short links don’t rely on having a QR scanner built into your device. They work just as well on a phone as on a computer. And, unlike a QR code, if you don’t get your phone out fast enough, you can still recall and enter a short link. 

Yes, they are case-sensitive. That’s easy enough to deal with – just go all upper- or lowercase letters. Or, if you mix ‘em, make sure you remind the audience about case sensitivity. I usually include a blurb that states the short link in words with spaces – making it easier to quickly read and grasp – followed by “This is case-sensitive.” 

Pro Tip: You can also embed the short link into the margin of the master slide so it’s visible on every slide, saving you from having to repeatedly explain that, yes, the link to the slides will be available after the presentation. 

A screenshot of a slide from a presentation; a QR code takes up most of the left side of the slide. To its right, text reads: View these slides at: bit.ly/getinfolit ("Get Info Lit", all lowercase).In the lower left corner, the short link is also embedded in the margin of the slide.

Real big QR code. Read bit short link, spelled out. Short link embedded in the margin. Clear QR, short link, can’t lose!

Problem #2: Size DOES Matter

See if this sounds familiar: 

You’re in a conference session. Someone puts a QR code up on the screen. And people from the back start jumping up and running to the front so they can scan the QR because it’s too small for their phones to resolve from 30 feet away. 

QR codes are actually pretty fascinating, from a technology standpoint. But they rely on the QR code having blocks large enough for a scanner to resolve. That’s easy when the code is right in front of you on a screen. But when the QR is on a screen in a large room, between lighting and size issues, QR codes become a point of failure. 

Solution: If you’re using QR codes, make sure they’re HUGE. 

I usually dedicate the second slide in my presentation to the largest QR I can fit on the screen. And even then, I have folks making the trek from the back of the room, because projector resolution is only so good, and lighting conditions are rarely excellent in larger rooms. 

A slide from one of Steve's presentations. The QR code dominates the right half of the slide, almost completely filling it from top to bottom. On the left side of the screen, text reads: "This slide deck is shared at: bit.ly/SLAdvocacyMatrix26That’s “SL Advocacy Matrix” & it’s case-sensitive. The link is in the upper-right corner of every slide. These slides are shared with a Creative Commons BY-NC-SA license. This license enables reusers to distribute, remix, adapt, and build upon the material in any medium or format for noncommercial purposes only, and only so long as attribution is given to the creator. If you remix, adapt, or build upon the material, you must license the modified material under identical terms. CC BY-NC-SA includes the following elements: BY: credit must be given to the creator. NC: Only noncommercial uses of the work are permitted. SA: Adaptations must be shared under the same terms." In the upper right corner, the short link is embedded in the margin of the slide. In the lower right corner, the text "Steve Tetreault" and a Creative Commons license for CC-BY-NC-SA.

HUGE QR code.
Large, easy to remember short link.
Short link embedded in the margin.
This is the way.

“Yes, And…”

I recently went on an anti-QR code rant on Bluesky. The awesome Martha Hickson and the wonderful Rain Smith both pointed out that they may have their place in the world. 

As information professionals, we should always strive to offer multiple points of access to the information in our keeping. 

So if you’re doing a QR code, PLEASE, for the love of all that is holy, make sure you also include a short link. That way, the savages and the slim-fingered can navigate on their phone via the Minotaur’s maze that is the QR, while the enlightened and rugged-fingered have the ability to use their computers to access information like civilized folk. 

I kid. But for a profession that works hard to provide accessibility options, QR codes alone are simply not enough. 

What Did I Miss?

I am sure there are elements of accessibility I’m missing here. Please help fill my knowledge gaps with your wisdom in the comments below!