Website icons: making the symbol match the action
Choose icons for real actions, give them clear labels and accessible names, and check their states, activation areas and meaning in context.
Article language: English

In this article
An arrow, a cloud, a mysterious little star. An interface need not make customers play a guessing game. An icon helps when people recognise the action or have a clear label beside it. If they have to guess whether a click will open details, download a file or take them to another page, the picture adds work. Let's look at where a symbol makes the journey shorter and where two ordinary words would do a better job.
Start with a list of functions, rather than an icon library. Separate icons that trigger actions from those that convey information or simply decorate the page. Then record what each one means, what description it needs and how you will check it. This preserves the site's visual character without making visitors decipher symbols in the contact section, menu and service pages.
Establish what the image does in this particular place
The same drawing can serve different purposes. An envelope beside the label “Write to us” supports the visible text. An envelope that is the only content of an unlabelled button has to communicate the action on its own. An envelope in a section background may be purely decorative. Each case needs different treatment, even though the graphic file is the same.
W3C describes functional images as images that initiate an action, and recommends that their text alternative explain the purpose rather than their appearance. For a print button, the action matters, rather than the fact that the picture depicts a printer. Carry that distinction into the way you specify icons in the design.
Not every illustration of a service is a control. If a symbol beside a description of an analysis is decorative, it should neither behave like a button nor take a place in the keyboard navigation order. If it opens details, people need to recognise that before clicking. Similar visual elements should not sometimes work and sometimes merely look as though they do.
In a hypothetical consultancy, three icons might represent research, recommendations and implementation. A magnifying glass, a light bulb and a cog will not explain where those services begin and end. The names and short descriptions still do the main work. An icon can help people remember the distinction, but should not create it in place of the content.
Describe the meaning in a sentence you can check
For each control, finish the sentence: “When the user selects this element, they will…”. Open the menu, expand an answer, download a file or reach a form. If the team cannot agree on one ending, it is too early to choose the drawing. Settle the action first. If arrows are meant to change the order of items, check reordering and alternatives to dragging (in Polish) so that the name and symbol describe the actual result.
A right arrow is a useful example of ambiguity. It might lead to the next step, indicate a link or simply suggest the direction of reading. Decide what it means across the site and look at its surroundings. The same arrow on a card and in a form may make sense if the text explains the difference; using a consistent shape will not explain it on its own.
In your mobile menu, distinguishing a link to a category from an action that expands a submenu is particularly important. The B2B mobile-menu guide (in Polish) helps plan that distinction. If a row does one thing and its small icon does another, separate the two targets clearly and test them on a phone. Accidentally opening another level should not be the price of trying to read a service name.
A written description of the meaning also helps when things change. A new team member need not guess why a particular sign was chosen. They can check whether a planned function still fits the recorded role. Add these choices to a design decision log (in Polish), rather than relying on the memory of the original designer.
A visible label and an accessible name meet different needs
A label on screen helps someone who does not know the symbol. An accessible name is the information that allows a screen reader, among other tools, to name a control. One does not always automatically provide the other. A well-built text button often uses the same words for both, but an icon-only control needs its name to be planned deliberately.
MDN's documentation on aria-label explains how to give an accessible name to elements that can receive one, including icon buttons. It recommends prioritising a reference to an existing visible label when one is available. This is not a universal fix that means adding hidden text to everything.
For example, a button shown as a cross could have the name “Close window”. With several windows, the context may call for a more specific name. An icon beside the visible word “Contact”, on the other hand, should not cause the same information to be announced twice. Ask the developer to check the actual name in browser tools and in a trial of the interaction.
Do not make a short description that appears on hover the only explanation of an unfamiliar symbol. A phone does not offer the same way of pointing, and keyboard use needs its own route. The basics of checking descriptions and controls are covered in company website accessibility (in Polish).
Check recognition before judging appearance
Place a few icons in their actual surroundings, with the same labels the site will use. Ask someone outside the project to say what will happen when they select them. Do not just ask whether they look familiar. Someone may recognise a picture of a box and still not know whether it means archiving, a service package or downloading a resource.
Then try a small exercise without labels if you are considering removing them. Record the different interpretations and compare them with the intended action. This does not prove that every user will understand the icons. It can, however, quickly expose ambiguity that a team looking at the icon since the start of the project no longer notices.
If the answers diverge, consider a label before trying another version of the symbol. Some concepts have no convenient, unambiguous picture. “Scope of responsibility” is hard to fit into twenty-odd pixels without losing meaning. In those places, text is the right tool, rather than a design failure.
Keep the results with the premium website brief (in Polish). Instead of “the icons should be intuitive”, you will have a concrete finding: people confuse downloading with opening details, so the control needs a label. That is easier to implement and check at acceptance than a general promise of a modern design.
Build a set with a shared logic, not just matching strokes
A consistent set should have similar stroke weights, corner treatments and optical sizes. That does not mean forcing every sign into an identical shape. A circle and a narrow symbol may need different adjustments to look equally clear side by side. Judge them at their actual size, not just on an enlarged presentation board.

Choose a limited vocabulary of meanings. If the same kind of download is represented by a down arrow in one place, a floppy disk in another and a sheet of paper elsewhere, people have to learn unnecessary variations. Conversely, using one sign for several different actions creates a superficial consistency. Organise both the appearance and the vocabulary of functions.
In breadcrumb navigation, a separator may resemble an arrow without being a button of its own. The breadcrumb guide (in Polish) explains its navigational role. Elsewhere, a similar sign really does take the user further. The surroundings and behaviour should explain the difference without requiring customers to investigate every element with the cursor.
Keep track of file sources and set rules for introducing new signs. Someone adding a service should not have to choose a random icon from another set merely because it describes the subject best. A short process for fitting a new need into the existing visual language is better than discovering a year later that the site speaks three graphic alphabets at once.
Make the state understandable without guessing from colour
An icon may change when a section expands, a setting is saved or a task starts. Record the states before, during and after the action. If a plus becomes a minus, the control still needs information about what it refers to and whether the section is open. The drawing alone does not provide the whole interaction. As the system grows, also record the roles of colours and spacing as design tokens (in Polish) so that the same control states follow shared rules on subsequent screens.
Check the visible focus indicator, which shows which element has keyboard focus, as well as the pressed state and any unavailable state. If an element cannot currently be used and this affects the customer's task, the reason should be understandable. A grey icon without an explanation may look like decoration or a loading error. Important meaning should also be conveyed through text or the control's structure.
In a contact form (in Polish), a success symbol should not be the only confirmation that the message was sent. Likewise, a warning beside a field needs to identify the problem and explain how to correct it. The symbol helps people recognise the type of message; the text explains what to do. Their roles complement each other.
Work on movement after the states. Website microinteractions (in Polish) should help people recognise a change without delaying the action. A rotating arrow will not fix an unclear function, though it can make the fact that nobody knows what happened look very elegant.
The drawing's size is not the size of its activation area
A small symbol can sit inside a comfortable button with space around it. A large drawing may respond only within a narrow area. At acceptance, ask to see the actual activation area, rather than just the file dimensions. This matters particularly for closing windows, expanding menus and choosing between neighbouring options.
W3C explains minimum target size in criterion 2.5.8, including spacing and specific exceptions. Do not reduce the assessment to saying that every small icon is a failure or every large button is correct. Check the actual target, its surroundings and how it is used.
Try the journey yourself with one hand on a phone: open the menu, choose a subcategory, close the panel and go to contact. Record cases where you activate a neighbouring action. This is not a measure of a particular person's dexterity. You are looking for places where the layout demands unnecessarily precise aim.
Watch for overlapping areas too. A card might lead to a description while an icon in its corner opens an additional action. Both functions must be recognisable and should not accidentally capture the same press. If you cannot separate them comfortably, consider a simpler layout with a separate, labelled button.
Translate the meaning, not just the file's caption
A language version should retain both the control's visible label and its accessible name. Sometimes translators receive only the text visible in the design, while hidden names remain in the previous language. Include those names in the content list and check them at acceptance alongside the icons' behaviour.
Do not assume that a metaphor will make sense in every situation either. People may recognise the symbol but infer a different action from its surroundings. If you have no basis for judging it, keep a clear label and test the scenario with someone who uses that language version. That is more useful than confidence based solely on the appearance of an icon library.
Do not accidentally change the function when changing the language. A download icon beside a file name should still lead to the right resource, rather than its general description. Shared checks of website language versions (in Polish), covering names, targets and the actual result of the action, can help.
Look at the icons in less comfortable conditions
Check the set on a phone, with enlarged text and in both palettes if the site offers a dark mode (in Polish). Thin strokes and delicate outlines can become hard to distinguish. Do not judge them solely on the large, bright monitor used to create the design.
Try a long label and another language version. The icon should neither push the text outside the button nor become detached from the name it belongs to. Check the spacing between two neighbouring controls. Equal gaps on a presentation board do not prove that a customer will avoid selecting the next action during ordinary phone use.
If the file fails to load, an available function should not turn into an empty space with no description. The developer is responsible for choosing how to embed it and what the fallback does, but you can request a specific test. What matters more than the file format is whether people can still recognise and perform the action.
When several icons look the same, check whether their names distinguish the right objects. Three controls labelled only “Download” may make it harder to select a document from a list of interface elements. The name should identify what the action concerns while keeping the visible label understandable. Try it with a workshop programme, a service description and a catalogue, rather than three identical test files.
Finish with a short list: meaning, visible label, accessible name, states and the test result. If you want to organise a set like this on your site, see the scope of Aeneia Design.







