Skip to content
Interface language: English
Design / Signal

Long names in interfaces: design for content that does not fit

Keep long names, addresses and conditions readable. Test wrapping, truncation, text spacing and language versions across menus, cards and forms.

Article language: English

Aeneia world concept: a worn wooden template with brass hinges and red thread on material samples.
In this article

“This will be a short title,” promises the mock-up. Then the real service name arrives and the card runs out of breath. A good interface should accommodate long titles, company names and document addresses without shrinking the letters to the size of a contract footnote. First decide what can be shortened, what should wrap and what the customer needs in full. A readable offer condition matters more than keeping every card the same height.

The most useful test replaces the ideal text in the design with real, more demanding content. Take the longest names, several language versions and an address without convenient places to break it. Check the menu, form, card and heading on a phone. Set out rules for editors and the team building the site, so each publication does not start another discussion about button width.

Collect the content that will actually appear

Do not start with a randomly long string of letters. You need different kinds of difficulty: a name made up of several words, one long word, a web address, a title with a qualifier and a label in another language. Each case may need a different presentation. One test cannot stand in for the others.

In a hypothetical studio, “Website design for companies providing specialist services” might fit in a heading but need a shorter version in the menu. A company name entered by a customer, by contrast, cannot be freely rewritten. The design should distinguish company copy controlled by the editorial team from data whose meaning must be preserved.

For each place, record the text's purpose and what may be changed. A heading explains a subject, a label signals an action and an identifier lets someone recognise a particular document. Shortening the last of these can remove precisely the part that distinguishes it from another. The information's function matters more than its length.

Connect this review with typography for a premium website (in Polish). Typeface, column width and line rhythm affect the composition, but they should not lead to content being hidden by default. A well-chosen system handles differences instead of requiring every word to have a similar form and size.

Decide when an editorial abbreviation is honest

A shorter menu name can make navigation easier if it remains consistent with the full title and does not change the scope. “Service pages” may be a clearer link than an extended offer name, provided the context makes its destination clear. “More” on its own does not solve the problem. It removes information.

Provide separate fields for the full title and the navigation name if the system requires them. Do not ask editors to shorten an article's main title simply because it looks awkward in a small card. The content publishing process (in Polish) should explain where a shorter version may be used and who checks that it remains consistent.

Compare names side by side in your own mobile menu. The mobile-menu guide (in Polish) can help plan it. Two shortened labels can become almost identical even when their full titles are clearly different. Someone browsing the offer should be able to choose the right destination without opening both pages as a test.

Do not use an abbreviation to hide an inconvenient condition. “Consultation” and “Consultation after an initial review of documents” can imply different preparation. If the condition affects the choice, it should remain readable by the link or close to it. A cleaner layout should not make the offer ambiguous.

Let the layout grow with the text

A card title may take one, two or several lines. If its container has a fixed height, part of the text can overlap the button or disappear. Ask the developer to test longer content and zooming in. Assess the whole card, including the element immediately below it.

Uneven heights are not always a problem. In many lists, letting content flow naturally works better than perfectly aligned bottom edges. If a shared height has a good reason, decide how the longest item will behave. Otherwise the design may work only until a detailed title appears.

Buttons need room for longer labels too. Check wrapping, spacing and any icon next to the text. A word should not push the control off screen or cover a neighbouring action. Text size should support reading; do not treat automatic shrinking as a universal rescue.

In your own comparison of two services, a longer condition may increase the height of one row. The service-comparison guide (in Polish) can help structure the comparison. Keep the relationship between headings and values clear. Removing a passage simply to even out the layout can take the meaning out of the comparison, especially when that condition is what distinguishes the scopes.

Separate wrapping from changing the value

MDN describes the overflow-wrap property, which lets the browser break an excessively long string so it does not extend beyond the line box. This changes presentation; it is not an instruction to change the content itself. Consider it for addresses or other strings without convenient break points.

Ask someone to test copying. An address shown across several lines should still lead to the right place when copied. Do not insert arbitrary spaces into the data just to make it fit a design. A document identifier must likewise remain recognisable even when its display adapts to screen width.

Not every text should be broken at any position. For proper names, numbers and units, choose rules that fit the meaning. Check the composition with real data rather than only a string of repeated characters. Something that technically fits inside a rectangle may still be difficult to read.

For external links (in Polish), it is often better to display an understandable destination name than a full technical address with parameters. Keep the correct link and show the complete value where it is actually needed for copying or verification. That reduces visible length without losing the function.

Set rules for ellipses

Truncating text after a few lines can be useful in an article list if the full content is easy to reach by following the link. It can mislead in an offer condition, file name or error message. Before using an ellipsis, decide what disappears and how the reader can retrieve the whole text.

Aeneia conceptual photography

Do not rely on hover alone. A person on a phone needs another way to see the content, and a keyboard user should not have to discover it by accident. If the full text matters, consider an ordinary expansion or a separate description. A content accordion is one option, provided its title indicates what is hidden. The content-accordion guide (in Polish) can help design it.

Test similar names that differ at the end. “Workshop programme: team version…” and another file with a similar beginning may look identical after truncation. In that case, expose the distinguishing part or add a separate label. A truncation mechanism does not know which part matters most. If the problem recurs across a catalogue, review the names of the product and service family (in Polish). Record the distinctions in the naming before more views start cutting them off.

Set separate rules for different kinds of content instead of one rule for the whole site. Truncating a card description may be acceptable, while the same treatment of a form response may not be. Editors should know when a component limits the view automatically and where a separate way to show the full content needs to be agreed.

Test reader settings and other languages

W3C explains the text spacing criterion, which checks that content can tolerate specified spacing changes without losing information or functionality. It does not require authors to use those values as the default appearance. The acceptance test concerns what happens when a reader adjusts the way they read.

Prepare a test using the values in the criterion and check menus, cards and forms. A fixed height that worked with the author's settings may then cut off the last line. Record problems against the specific elements. A general statement that the site is responsive does not answer this case.

Use real translations when checking the site's language versions (in Polish). Do not assume one expansion percentage for every text and language. A short label, a title containing a proper name and text in another writing system can behave differently.

Also check the name, company name and description entered in the contact form (in Polish). A comfortable input field is not enough if a summary or a message after submission later cuts off the same value. Support for long data should cover the whole path through the task.

An error message needs room to explain

An error often needs more text than the initial state. “Complete the field” is short, but it may not be enough when the problem concerns an attachment format or several connected pieces of data. Prepare a real explanatory example and check that it fits in a logical place without covering the next field.

A hypothetical form might ask for a description of a problem and a document. If the file is unsuitable, the customer should learn what to change and whether the information already entered remains in the form. That message may need several sentences. Do not automatically shorten it to one line if doing so removes the instruction needed to finish the task.

Check several errors at once too. The message above the form and the description by a field should still belong to the right elements. Longer content may move controls, but it should not leave the user lost. Someone using a keyboard must be able to return to the place that needs correction without searching for where the current selection went.

During acceptance, carry the test through until the data has been corrected successfully. Text appearing on screen alone does not prove that the explanation is readable or sufficient. If a person repeats the same mistake, the message's language, the layout or a missing condition may be responsible. Record the actual obstacle rather than shrinking the type to recover space.

File names and versions need a recognisable difference

A long document name may be necessary to distinguish the programme, language, date and variant. When designing the list, decide which details should be separate fields instead of joining everything into one string. Title, version and language can each have their own place, keeping the whole item readable on a phone. For a larger collection, extend those rules in a resource centre showing each file's version and use (in Polish) instead of leaving all identification in the name.

Do not change the actual name of a downloaded file solely to shorten its label. The presentation and the saved document can serve different purposes. If you show a friendly title, make sure the recipient can still recognise the right material after downloading it. Otherwise the short description on the page and the technical name in the folder may look like two different documents.

For a small exercise, prepare two items with similar beginnings in their names and different versions. Ask someone to download the specified variant and recognise it after saving. If they must open both files to tell the difference, improve the labelling. The layout should support the choice, not transfer it to another application.

Repeat the case with enlarged text and without access to the description in the neighbouring column. Important meaning must not depend solely on exact alignment. This test helps you design for real documents and later updates, not only the first convenient sample in the mock-up.

Leave editors rules and examples they can reuse

Prepare a small set of difficult content to rerun after components change. It does not need to be huge. It should represent different problems: a long word, a multiword name, an address, a translation and an important condition. Each example needs an expected result so a new person knows what they are checking.

Include sample views and shortening rules in the website acceptance process (in Polish). If an editorial limit exists, explain its purpose and what to do with a justified exception. A limit should not mask a layout error or force publication of an unclear abbreviation.

In the editor, also preview the finished content before publication. If a limit applies only to the view, do not present it as a ban on saving a longer name without explaining it. An editor should see the effect and know how to prepare a justified exception. Otherwise they will adjust the text through repeated publications instead of assessing it calmly beforehand.

Review problems after actual changes: a new kind of card, a different typeface, an additional language or a redesigned menu. There is no need to repeat the entire set after correcting a comma. Keep examples that previously exposed lost content, however, so the same error does not return in the next redesign.

If your site looks good only with short text, see the scope of Aeneia Design.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear