An accordion interface lets users expand or collapse content by clicking headings. Its benefits include providing a page overview, reducing scrolling, and letting users choose which parts to read. The trade-off is that content is hidden and requires an extra action to reveal. It is better suited to finding individual answers than to content users need to read from beginning to end. Whether to use one should depend on how readers need to use the content and how its sections relate to one another, not simply on a desire to shorten the page.
Collapsing content can organize long pages, but headings must be clear
When content is collapsed, the list of headings acts like a small table of contents. Users can see what is available before deciding which section to expand. A 2014 NN/g article noted that this can also make long pages look less daunting, but it does not necessarily make the content itself easier to understand.
- FAQs or indexes: Users looking for just one answer can select the relevant heading without browsing every answer in turn.
- Very long pages on mobile: If a page contains several loosely related topics, collapsing them can reduce scrolling and give users an overview of what the page covers.
These benefits depend on descriptive headings. For example, a complete question used as an FAQ heading tells users more about what they will find than a label such as “More information.” If headings do not help users judge whether the content is relevant, they are left guessing.
Less scrolling may mean more clicks and overlooked content
Accordions do not necessarily make reading easier. Users still have to find where to click, decide whether to expand a section, and wait for content to appear. NN/g articles from 2014 and 2017 both cautioned that when users need to read most sections, expanding them one by one adds effort and makes reading more fragmented.
For example, articles or book chapters that need to be read in sequence are generally not well suited to having every section initially collapsed. When most of the content is relevant to the reader, displaying it all at once and letting readers scroll through it may be more appropriate. A shorter page does not necessarily make the task easier.
Hidden content is also easier to overlook. If a user does not expand a section, that does not necessarily mean they do not need the information. The heading may not have made its usefulness clear, or the user may not have noticed that the content was there.
In-page links are optional; collapsed content must be expanded
In-page links are an additional navigation aid: users can still scroll through the full text without using them. An accordion, by contrast, requires interaction to reveal collapsed content. A 2014 article noted that in-page jumps without clear cues can leave users unsure of where they are on the page; this does not mean accordions are better in every situation.
A 2017 article also noted that users at the top or bottom of an expanded accordion section can see other section headings directly. This makes switching sections easier than with a table of contents placed only at the top of the page. However, this comparison does not apply to a fixed, persistently visible in-page table of contents.
The implementation also needs to support accessibility and be adapted for printing. A 2014 article cautioned that accordions can make it difficult to print all the content at once, potentially forcing readers to print it in sections. Simply confirming that content expands and collapses on screen does not mean the design is complete.
Accordion interfaces: perspectives from across the web
Do FAQ pages have to use accordions?
No. If readers usually look for individual answers, an accordion lets them choose what to view from a list of questions. A question list with in-page jump links is another option, allowing readers to scroll through all the answers even if they do not use the links. A 2015 article considered collapsible accordions suitable for the content it discussed, but also cautioned that desktop implementations are not always effective. An approach that works on mobile should not automatically be assumed to suit desktop use as well.
How should content be presented when a complete answer spans multiple topics?
If readers need to expand most topics to get a complete answer, displaying the content all at once is more appropriate than requiring them to expand each item. Repeatedly clicking and deciding what to read next adds effort and can interrupt reading. By contrast, when topics are loosely related and readers need only a few items, a collapsed layout is more likely to make it convenient to choose what to read.
Can accordions still be used when printing or accessibility matters?
Yes, but accessibility and printing needs must be addressed; expand-and-collapse functionality alone is not enough. A 2014 article cautioned that accordions need to be coded to support accessibility and adapted for printing. Otherwise, readers may find it inconvenient to print the document or may even need to print it in sections. If readers are expected to print the content in full, check how collapsed content appears in print, not just on screen.
References
- An FAQ’s User Experience Deconstructedwww.nngroup.com · 2015-01-25T17:00:00+0000 — Discusses: Do FAQ pages have to use accordions?
- Accordions Are Not Always the Answer for Complex Content on Desktopswww.nngroup.com · 2014-05-18T16:00:00+0000 — Discusses: How should content be presented when a complete answer spans multiple topics?; Can accordions still be used when printing or accessibility matters?
- Anchors OK? Re-Assessing In-Page Linkswww.nngroup.com · 2017-05-07T16:00:00+0000 — Discusses: Do FAQ pages have to use accordions?



