Skip to content
Interface language: English
Design / Signal

Accordions on a service page: what to collapse without hiding the answer

Decide what belongs in an accordion, keep important conditions visible, and test headings, keyboard access, copying and print.

Article language: English

A woman holds a fan beside draped fabric and flowing water.
In this article

An accordion should organise a page, not try a customer's patience. Expandable sections help when people need only some additional answers and can recognise them from their headings. The basic scope of a service, an important price or a condition for starting work must still be easy to find. Here is how to decide what to collapse, what to keep visible and how to check the component.

First arrange the content as an ordinary explanation. Mark the information everyone needs and the details that apply only in particular situations. Only then consider putting the second group in expandable panels. Afterwards, check the panels on a phone, with a keyboard and in print.

Hide the detail, keep the basic answer visible

In a hypothetical design service, a customer should immediately know what they will receive and what materials to prepare. Detailed instructions for sending photographs can go in a panel if its heading clearly promises them. The fact that photographs are needed should remain visible next to the scope of work.

The same applies to price and timing. If either depends on a condition, do not move that condition solely into a section at the end of the page. An accordion can hold explanations, but it should not act like fine print with an extra task attached. A customer should not have to open every closed panel to learn what is actually being offered.

Start with the layout of a service page (in Polish). If a few concise paragraphs contain the whole offer, collapsing them may only add steps. If the description is long, assess its order and divisions first. A better heading and shorter copy can sometimes help more than closing a section.

In information architecture (in Polish), an accordion is a way to present part of the content, not a substitute for organisation. A dozen unrelated panels are still disordered content in a more compact package. Before hiding the clutter, see whether you can simply tidy it.

Give panels headings people can choose from

A heading must indicate its content clearly enough that customers do not need to open everything on trial. “Materials” may be too broad. “How should I prepare photographs for the project?” gives people enough information to judge whether it is relevant. In a questions section, a specific heading preserves the purpose better than a generic company slogan.

Compare the closed panels without reading their answers. Can you tell where to look for the way to submit feedback and where to find instructions for sending files? If several headings sound alike, improve the division. People should not have to learn the company's internal structure to recognise an ordinary instruction.

In a service-page FAQ (in Polish), questions should come from real doubts. Do not add pretend questions just to fill the component. Two useful answers may help more than eight nearly identical invitations to get in touch.

Check long interface labels and text (in Polish). A panel heading should be able to span more than one line without overlapping the expand symbol. If an abbreviation removes the distinguishing part, let the label wrap. A consistent visual rhythm does not require every question to have the same length.

Decide whether one or several panels can stay open

One open section can limit the length of the view. Several open at once allow people to compare answers and return to an earlier passage without selecting it again. The choice depends on the task. If a customer is comparing material requirements with a schedule, automatically closing the previous answer can make reading harder.

Prepare a test: open two needed sections, find the relationship between them and copy an important passage. Also check the page position after a long panel closes. A sudden jump can leave someone disoriented. Do not assume that fewer visible paragraphs always mean less effort.

The W3C accordion pattern describes headings, expanded state and keyboard operation, and accommodates different opening rules. Choose the behaviour deliberately in the specification. It should not be an accidental library setting that nobody considered in relation to the content.

If the text requires several answers to be compared at once, consider an ordinary list or a comparison of two services (in Polish). An accordion need not be the right format for everything that looks too long. Sometimes the greatest help is to leave the needed information side by side.

Check the heading, state and keyboard

A panel heading acts as the control that starts an action. It needs an understandable name, an indication of whether the panel is expanded and keyboard support. A custom appearance does not mean recreating these behaviours without a tested mechanism. Ask the developer to explain the chosen solution and demonstrate a complete test.

In the W3C pattern, when focus is on the header button of a collapsed panel, Enter or Space opens the associated panel. When focus is on the header button of an open panel, the same keys can close it if the implementation permits this. Tab moves focus to the next element in the tab order. Focus identifies the element receiving keyboard input, while a visible indicator helps people see where focus is. Check the actual order and the visibility of the indicator. People should not have to guess which heading will respond when they press a key.

Once a section is collapsed, its hidden links should no longer receive ordinary keyboard interaction. When it is expanded, they must be available in a logical order. This is a specific test, not merely a judgement of the plus symbol. The wider context is covered in business website accessibility (in Polish).

MDN describes the built-in HTML details and summary elements as a way to show and hide information. They can be a starting point for a simple solution, but their appearance and behaviour still need checking in the environment being used. Choosing an element does not remove the need to review the actual page.

Plan for content that does more than reading

A panel can contain a link, a form or a video. Each introduces additional states. If you close a section while media is playing, decide what happens to the sound. If it contains entered data, decide whether the data remains and how people will recognise its state when they reopen the panel.

For video on a service page (in Polish), important information should not depend on watching the recording. In a closed panel the material is even less visible, so its title and short description must explain its role clearly. Do not hide the only evidence supporting the service's main promise there.

Aeneia conceptual photography

For external links (in Polish), check the journey out and back. Is the panel still open? Does the user return to the right place? If changing the address or refreshing closes everything, assess whether the lost state makes the task harder to resume.

Avoid nesting more accordions when ordinary headings would be enough. Opening several levels can turn an answer into an unpacking game. For a longer instruction, consider a separate page that is easy to link to and return to instead of an ever deeper drawer. Give it a table of contents and a way back to one's place in a long guide (in Polish), so customers can open the requested chapter and keep their bearings.

Read the answers outside the ideal view too

Check a long answer, a list and a new language version. Once opened, the whole text should remain available without being cut off at the height prepared for the first sample. Animation may change the transition, but it should not impose a maximum answer length unknown to the editorial team.

For website microinteractions (in Polish), decide what happens when a panel is selected again quickly. The person's latest decision should lead to the state they now want, without replaying a queue of old movements. Motion should explain the change, not delay access to a paragraph.

Prepare a printed version of the page (in Polish) too. If important answers stay closed, a customer may receive questions without answers. Decide which content should be retained and check the actual output. The fact that everything is visible on screen after being opened by hand does not settle how printing behaves.

Test search in the service being used. An internal search tool (in Polish) should lead to the relevant information if it is meant to cover panel content. Do not assume that every mechanism automatically reveals a hidden answer when someone follows a result. That requires a test of the particular solution.

A support worker may want to send a customer a direct link to the material-preparation rules. If the address leads only to the top of a long page with all panels closed, some of the benefit is lost. Decide whether the solution can point to a particular section and what should happen when someone arrives there.

In the test, open the link in a new browser session. Check whether the right answer is visible and its heading is not covered by a fixed menu. Then go to a neighbouring section. A direct link should help people start reading, not block the rest of the interaction or impose an order.

Do not assume every library behaves identically. Write the requirement as an outcome for the reader: on arrival, they can find the intended answer and understand its place on the page. The developer can choose a suitable mechanism. It must be possible to check it at a real address, not only in an open design preview.

When changing a panel heading or order, check older links used in messages. You need not keep every old answer forever, but a replacement should be deliberate. If content has moved, establish the right destination and update the materials the company still uses to support customers.

Compare the accordion with shorter copy

Take the three longest answers and put the main point of each in its first sentence. Then remove repetitions and information already present in the service description. See how much remains. After that edit, an ordinary section may be just as convenient and give the reader an answer without another action.

In a second version, keep the panels but show a short summary above them. Check whether a customer can select the right topic without opening every section. This test helps show what the component actually contributes: selection of supplementary content or merely concealment of verbose copy.

Do not judge the versions only by the number of screens. Record whether the person found the answer, understood it correctly and can identify the next step. A longer view can be easier when the content is well ordered. A shorter one can help when questions address separate situations and their labels distinguish them clearly. A plain-language comprehension test (in Polish) helps here: the participant explains the condition they found and what it means for their task.

Finally, choose a solution for the specific section, not the entire site in advance. An FAQ, preparation instructions and a comparison of scopes have different jobs. A shared visual style does not require the same way of hiding all content. This keeps the page coherent without making every answer play the same accordion.

Maintain the content with simple rules

In the editorial instructions, record what information may go in a panel, how to write headings and when a separate page is better. At each update, check whether an answer has become a basic condition of the service. If so, move the important part into the visible scope instead of leaving it at the end out of habit.

When writing copy for a service page (in Polish), a clear answer comes first. A component cannot repair a verbose paragraph or give meaning to an unclear question. Read the content without animation and consider whether each section helps with a specific task. Only then refine the speed of expansion.

For the hypothetical studio, prepare this test: a customer knows they want to commission a project but does not yet have photographs. They should immediately see whether photographs are needed and find how to prepare them in the appropriate panel. They should then be able to get in touch without losing that information. This scenario checks the content division and interaction, not merely whether any answer opens.

In a second test, the customer receives a link to a specific instruction. They open it on a phone, copy a passage and return to the offer. If that requires browsing every panel, improve the labels or direct entry. If the text is findable but does not answer the question, return to editing. The expansion mechanism and the quality of the answer need separate assessment.

For website acceptance (in Polish), choose several real questions and check whether people find the answers without hints. Record wrong panel choices and loss of orientation after opening one. The number of expansions alone cannot show whether customers understood the content; it may also reflect searching at random.

If you want to organise a long description or a questions section, 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