Marcin Wichary of Unsung starts from cars driving through heavy rain without tail lights, likely because drivers confuse the parking and driving light icons, and moves on to Apple swapping text labels like Done, Cancel and Return for icons in iOS 27 and on keyboards. He revisits Jef Raskin's finding that icons are harder to understand than labels and shares his own iconography cheat sheet.

“In every study that considered the question”

I spent most daylight hours yesterday driving in torrential rains in pretty bad visibility, and I was astonished how many cars didn’t have their lights on.

It looked something like this. The cars with tail lights on were somewhat visible, but the cars without them didn’t stand a chance:

I read up about it, and it turns out that the issue wasn’t as much forgetfulness or carelessness. Rather, it all might have to do with iconography.

Cars have two main settings for lights:

“regular driving,” meant to be used at night and during limited visibility – like in heavy rains,
“parking,” which activates only front lights, at half brightness, and (for some reason) leaves the tail lights off.

The UI for lights seems to typically look like this:

Without knowing, can you figure out which setting is which?

The left icon with two lights facing away from each other means the parking lights. The far-right icon with one light pointing slightly down (“low beams”) is regular driving lights. The latter is the right thing to do in the rain, but the assignment feels kind of arbitrary to me, and I could totally see the icons going the other way.

Also, the above is a somewhat gentle situation. In my rental car, the lights were on a stalk, and the setup looked more like this:

Here:

the lightbulb on the left is a meta indicator for “this is the main light setting” (you can see it above too, on the dial),
the middle part with the wavy line is fog lights,
the arrow-heavy thing on the right informs of two things: pull on the stalk for high beams (another mode), or rotate the stalk left or right for turn signals.

That’s a lot of stuff going on, and many similar icons that do not appear immediately understandable. The whole interface seems optimized for motor memory, but harder to approach at first.

In both modes, the feedback from inside the car is exactly the same – you see the interior dashboards illuminate, and the front lights go up. At night, you might spot the difference in the front light intensity. But in the daytime rain, it’s less likely – especially if it’s a rare intense rain you don’t encounter often. Most importantly given the beginning of the story, you simply can’t see what your tail lights are up to.

From reading up on it, I believe what happened was the confusion between the two modes – people were driving with the best of intentions, actually turning on the lights… except the wrong kind of lights.

(Many cars have an AUTO option now, but would you trust it to choose the right thing? I didn’t, being unsure if it properly accounted for daylight rain driving.)

Lost perhaps amidst the recent conversations about icons in menus and app icons was another subtle change: Apple started embracing more iconography on buttons, too.

You can see it on keyboards, where the U.S. models followed in the footsteps of international ones, now showing symbols instead of legends for Tab, Caps Lock, Shift, Fn, Enter, Return, and Delete. Here’s the previous generation and the 2026 one:

The shift also happened on screens. Below are examples from the last three versions of iOS (18, 26, and 27), side by side.

When starting a new note, it’s not just the keyboard’s ↵ that replaced Return. The back icon also lost its legend, and Done became a checkmark:

Here might be the best case scenario, with Cancel and Done swapped with icons:

In this AirDrop screen, Done became a close box:

Elsewhere, Cancel morphed into ×, in an unfortunate position next to a different ×. Plus, Search on the keyboard became a loupe:

When screenshotting, Done was splintered into a checkmark and an ×:

And here, Done transformed into a checkmark, while Edit became a new kind of a paint icon:

Seeing all this, I was reminded of this old post from Dmitry Fadeyev, titled “False simplicity”:

Sometimes, what appears on the surface to be simple is actually far from it. For example, there’s a trend in Twitter clients to use icons instead of text labels for buttons. Just icons, no text at all. These icons don’t take much space, look elegant and maintain that simple feel of Twitter, except…they’re actually just confusing.

Fadeyev also quoted Jef Raskin’s take on icons:

In every study that considered the question, icons were demonstrated to be more difficult to understand than were labels, especially at first viewing, which contradicts one of the most frequently cited reasons for using icons, namely, comprehensibility for beginners. […] Although it is true that tiny icons can take less screen space than labels, you have to ask: At what cost? The smaller a button, the longer it takes to operate it, and the more difficult it is to find; also, it is difficult to make a small icon distinctive.

I like that take.

Here’s my personal go-to cheat sheet when it comes to iconography:

icons are compact, allowing you to squeeze in “more UI,”
people probably understand only a few icons (close box, checkmark, plus, some chevrons), and can learn others – but the learning process will be harder than you think,
many icons are never understood, but people can still to some extent use them without ever understanding them,
icons can break the monotony of an all-text interface,
well-made icons make the interface look more attractive in a way type can’t.

I don’t believe Apple is doing it all just for aesthetical reasons. My guess is that it’s more about the first bullet point above: liquid glass added so much chrome and padding that Apple simply ran out of room for text labels encased in glass.

At the first glance, Apple is avoiding the car light problem by using popular icons. However, there’s a new challenge: most of these icons are too popular, and overloaded with meaning:

checkmark: “commit” or “to do item/checkbox”?
×: “close” or “clear”?
loupe: “search” or “zoom”?

The only outlier is the edit icon, relatively new and likely unknown. With the extra challenge that on-hover tooltips don’t exist on touch devices, the way forward would be to use the paint icon consistently to teach it to people, but it seems Apple isn’t yet doing a great job at that. The below screenshots are all iOS 27, where you can see the leftover Cancel and Done labels in place, and a missed opportunity to put the new edit icon next to Customize to help people connect the concepts:

I wish I could peek inside Apple to see how these efforts are faring, and what’s in store.

To go back to keyboards, I am curious why Apple didn’t consistently apply text and icons for all the affected keys, like they did for the bottom row a while back. Here there was enough room:

And how could we solve the car problem, if iconography is indeed the culprit? I could imagine a similar idea here as well:

But the funny thing is that most modern cars have a digital dashboard, so for the first time, tooltips are an option. You could imagine turning the stalk and seeing this kind of a message appear for a few seconds, the description and the icon side by side to help the user connect one to the other:

Perhaps seeing the word “parking” would help some people realize their mistake.

Of course, introducing a tooltip means “now you have two problems,” but let’s save that for a different post.