UI/UX Tip


Hello Reader,

Make it easy to spot interactive elements.

I might not have drawn the best illustration, but I’ll try to explain.

First, we should learn about signifiers. Here is the definition from the Interaction Design Foundation:

Signifiers are perceptible cues that designers include in interfaces so users can easily discover what to do.

I’m going to show a bad example for the sake of demonstrating why certain elements might not look interactable or may not look “sufficiently” interactable.

In the left image, apparently, nothing looks interactable. But what exactly should we do to fix it?

  1. Links should be underlined. This not only makes it more obvious that they are links, but also addresses an accessibility issue: users with color vision deficiencies will benefit from the underlining.
  2. If the textarea can be resized, there should be a handle that can be dragged. Ideally, it should stand out enough to be easily seen.
  3. In the dropdown, apart from having an icon (which is essential), we can also play around with background and shadows to make the input look like something clickable.
  4. And the last thing is the button. It should not only look like a button (having a background, standing out enough to be clearly visible) but we can also use an icon as a signifier that the form will be submitted.

There are many cases when we can forget about it. We tend to forget about such things as:

  1. Reaction on mouse hover (read about affordance)
  2. Placing an icon, e.g., in a file upload area
  3. Making the element stand out enough to be considered as an interactive element
  4. Links should be underlined
  5. Carousels (if you use them) should have large, clearly visible handles that are easy to hit

And so on.

Thank you and have a nice day.

Victor Ponamariov

I'm a full-stack developer that is passionate about good user interfaces. In my newsletter, I talk mainly about UI/UX stuff. You could expect an email or two in a month, I'm not aiming to spam you with non-useful info.

Read more from Victor Ponamariov

Here is a quick recap of all CSS prefers-* queries that you can use to adjust to user settings. Prefers Reduced Motion (95.57% global support) Indicates whether the user prefers less motion to avoid VIMS - Visually-Induced Motion Sickness. Here we disable any animations or transitions, but we can be flexible here (e.g., REDUCE motion but do not disable it completely) Prefers Color Scheme (95.16% global support) Detects whether the user prefers a light or dark color theme. In this example we...

Today we'll cover another CSS media query: prefers-reduced-motion, and how to load (or avoid loading) styles based on user preferences — this is genuinely cool stuff! I've just posted the same article on LinkedIn, for my first time. Accessibility concern There’s a condition called VIMS: Visually induced motion sickness (VIMS)—a subcategory of motion sickness that specifically relates to nausea, oculomotor strain, and disorientation from the perception of motion while remaining still. To...

After a rough patch, I’m getting back to writing. More practical stuff that you can apply directly in your projects. One topic that looks really good is how to use modern CSS to support UI/UX and accessibility. Preference Media Queries Preference Media Queries allow you to adapt your UI based on the user's system-level settings and personal preferences — like reduced motion, high contrast, or dark mode. They're mostly used to improve accessibility and user experience. Let's cover one of them....