pablobm left a comment (openstreetmap/openstreetmap-website#6383)
@maro-21 - That is a valid opinion, but not a fact. Personally I like the way
that https://github.com/openstreetmap/openstreetmap-website/pull/6410 is
progressing. However I would agree that there isn't a single "best" solution.
We need to put some thought on why we are doing things.
My personal opinions, bearing in mind that I'm not an expert in UX:
- Icons are attractive to first users and create interest in engaging with the
website.
- Icons make the interface more pleasant.
- On first sight, there can be a question of what the icon means. On repeated
uses, after we have associated them to an action, they make it easier to find
the action.
- Icons can be bad if badly chosen, creating more confusion. If there's no
obvious candidate for an action, consider not assigning an icon.
- For example, there's a conversation about the right icon for
"Scroll to changeset" at
https://github.com/openstreetmap/openstreetmap-website/pull/6410#discussion_r2375388539.
It's legit to decide that no icon is suitable.
- We must not rely on icons only. Icons are not universal or fully accessible,
and a text description must always be present.
- When adding more icons in the future, we need to be consistent. Not only make
sure that same icons are used for the same actions, but also that the choices
across different actions are consistent.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6383#issuecomment-3380645025
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/6383/[email protected]>_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
