Digital Affordances and Signifiers: How an Interface Tells You What You Can Do

A digital affordance is the possibility for action that an interface element offers you. How do you know that you can press a button, scroll a list or drag a card? All these possibilities together are what we call affordances. The concept has to do with what a user perceives they can do on meeting an element, and it sits at the very base of interaction.

Contents

The concept bears directly on localisation, because every text segment that reaches the translator carries a possibility for action with it. A translation made without knowing that possibility can tie the wrong word to the wrong action. In this article we look at what a digital affordance is, how it differs from a signifier and what it amounts to in translation.

Where does affordance come from?

The idea of affordance comes, in fact, from the field of design. The perceived and actual properties of an object determine how it can be used. Well-designed objects are easy to interpret; they offer the user visible cues about how they are to be handled. A door handle suggests pulling, a flat plate suggests pushing.

This thinking has been carried over into digital interfaces as well. Clickable buttons, draggable sliders, tabs: all of them are elements we read at a glance as things we can interact with. Interface design consists in large part of placing these perceived possibilities deliberately. A user should sense what they can do simply by looking at an element.

Yet a perceived possibility is not always self-evident. On a touchscreen it is not always easy to see that an area can be scrolled or held down. This is where another concept steps in, one that makes the affordance visible: signifiers.

Signifiers matter more than affordances

Signifiers are perceptible marks that announce that something can be done. As one design theorist has stressed, signifiers are even more important than affordances, because it is they that give the user a concrete cue that the possibility genuinely exists. A change of cursor, a shift of colour or a small arrow are each signifiers.

The difference is this: an affordance is a possibility, a signifier is the announcement of that possibility. A link shown in a different colour is a signifier saying that it can be clicked. Without that signifier the user will not notice the affordance, even though it exists. Good design makes possibilities visible through signifiers.

Some signifiers are textual. A word on a button, a tooltip or an action label is a signifier telling you what that element does. When these textual signifiers are localised, the action information they carry has to be preserved along with them. A signifier translated wrongly sends the user in the wrong direction.

Digital affordance and the context of the text

When a translator works through text segments from a digital product, the possible actions a segment carries are part of its context. Does a word trigger a tap, a scroll or a deletion? Without that information the translation stays incomplete. The same word may be translated differently when it is tied to a different affordance.

The classic example is the English word Close. It can be a verb, and it can also be an adjective meaning near. If you do not know which action it is tied to, the translation goes wrong. Is it shut, or is it near? The answer is hidden in the affordance that the segment carries.

This is why information about affordance should be included in the context available for a translation segment. Knowing what a string makes the user do is often worth more than the word itself. A segment with no context forces even the best translator into a wrong guess.

The XLIFF context note and action information

Localisation files offer dedicated fields for carrying this context. In the XLIFF format, a note field added beside a segment can explain which action that segment belongs to. In the examples in the source book, this note states that a word is tied to a tap or to a scroll.

Segment	Context note
Close	The action of closing an inactive tab by swiping it
Delete	The confirmation that appears when the user taps the delete icon
Open	The button that opens the box; an action, not an adjective

As the table shows, the note ties a very short word to the right action. These notes are informative, and they are the key to a correct translation. Without the note the translator has to guess which action the word belongs to, and that magnifies the risk of error.

Signifiers and user expectation

When users meet an interface, they bring a mental model built out of past experience. Their interaction with thousands of screens has taught them what particular signifiers mean. It is from this accumulated experience that they know underlined coloured text can be clicked and that a bin icon suggests deletion.

Localisation must not upset that expectation. In translating the text of a signifier, you have to preserve the action the user associates with that mark. Replacing a familiar pattern with a forced equivalent defeats the user’s learned expectation and slows the interaction down.

This is a reminder that signifiers are also read culturally. An icon or a mark can carry different associations in different cultures. By attending to both universal interface patterns and local reading habits, the localiser conveys the meaning of the signifier accurately to the target user.

Affordance is part of constrained translation

Digital texts are multimodal; meaning arises from the combination of text, image, sound and movement. Affordances too are part of that whole. A text segment takes on meaning together with the visual and interactive elements it is attached to. This turns localisation into a form of constrained translation.

In constrained translation the text has to be translated not on its own but in harmony with the elements accompanying it. A button label has to fit the space and to describe accurately the action it triggers. A translation that ignores the affordance may be grammatically correct yet functionally wrong.

Information about affordance is therefore not a luxury of translation but a requirement of it. Working with the screen in view, reading the context notes and grasping the interaction logic of the product are preconditions of an accurate translation. A translator who understands the affordance also understands what the user will want to do.

Haptic and touch signifiers

On touch devices, affordances often work through invisible actions. Tapping, swiping, pinching to zoom or pressing and holding: none of these shows itself the way a button does. The user discovers these actions only through textual cues or haptic signifiers such as vibration. Translating those cues makes a hidden action visible.

The texts that describe these actions are very short but decisive. Phrases such as Swipe to delete or Press and hold to continue tell the user what the interface can do. When these texts are translated wrongly or vaguely, the user never learns that the action exists at all and a part of the product stays closed to them.

Some haptic signifiers, on the other hand, are wordless; a vibration or a small animation reports that the action has taken place. The handful of words that accompany these wordless signifiers reinforce their meaning. In translating these texts, the localiser must also keep in mind which physical action the user will perform.

Keeping visual and textual signifiers in step

In digital products, text builds meaning not on its own but together with visuals. An icon and the label beside it, a screenshot and the help text describing it, must agree with each other. This internal agreement is the most basic requirement of constrained translation; if text and image contradict each other, the user cannot tell which to trust.

Help pages are where that agreement is most fragile. When the screenshots show the interface in the source language while the text has been translated into the target language, the user experiences a break between the screen they see and the explanation they read. Visuals should therefore be localised along with the interface, or at the very least brought into line with the text.

This agreement determines how far a signifier can be relied on. A signifier is read clearly only when text and image say the same thing. The localiser has to think of these two channels together rather than separately, because the user perceives them together too. Signifiers that are in step make interaction intuitive. When they are out of step, the user cannot tell which channel to trust and hesitates over even the simplest action.

The Türkiye context

In Turkish interfaces, the texts that describe affordances are mostly translated from foreign products. When those translations are made without context notes, actions such as tapping, swiping or pressing and holding can end up matched with the wrong words. The user falls back on trial and error to work out what a button does, and that slows the interaction down.

The verb-centred structure of Turkish offers an advantage here: actions can be expressed clearly and briefly. Equivalents such as aç, kapat, sil and paylaş make strong signifiers when they are used in the right context. What matters is that the translator can see which action the string is tied to, and for that the context information has to be present in the project files. Where it is supplied, the Turkish interface becomes intuitive and fluent; where it is not, the user is left to learn what the buttons do by trial and error.

What does this mean for you?

The interface texts of your product are the signifiers that tell the user what they can do. When these signifiers are translated without context, the user pauses for a moment on every screen. Translated with the right context, the interaction becomes fluent and intuitive. Handing over to translation not only the words but also the actions those words trigger is what marks out good localisation.

1. Have the action context of the segments added to the translation files.
2. Provide a screenshot or a note for words that are ambiguous.
3. Do not replace established interface patterns with forced equivalents.
4. Have the interaction tested on a real device.

To talk about how to build this context into your processes you can look at our services, and for a road map tailored to your project you can get in touch with us. A well localised digital affordance lets the user make the right move without a moment’s thought; a badly localised signifier turns even the simplest action into a riddle.

Frequently asked questions

What is a digital affordance?

A digital affordance is the possibility for action that an interface element offers: pressing a button, scrolling a list or dragging an element, for instance.

What is the difference between a signifier and an affordance?

An affordance is the possibility for action itself; a signifier is the perceptible mark that announces that possibility to the user. A signifier actually tells the user that something can be done.

Why do affordances concern translation?

The possibility for action that a text segment carries is part of its context. If that context is unknown, the same word can be tied to the wrong action and cause a translation error.

What is the XLIFF context note for?

The note field in XLIFF files explains which action a segment belongs to; by stating that a word is tied to a tap or a swipe, for example, it secures the correct translation.

Sources

• Jiménez-Crespo, M. A. (2024). Localization in Translation. Routledge (Chs. 6/7).
• Norman, D. (2013). The Design of Everyday Things, signifiers and affordances.
• OASIS, the XLIFF file format and the Note element.