1. Choose what can be collapsed
Our example page covers opening hours, entry conditions and permitted items. Start by reading all the copy without an accordion. Identify the information visitors need to make their decision and propose keeping it visible. Use collapsible sections for clearly identifiable extra detail if this actually makes the page easier to navigate.
Ask someone unfamiliar with the content where they would look for each answer. If they must open every panel to compare two conditions, visible content may work better. The HTML standard specifically describes this trade-off for exclusive groups: saving space can hinder reading several answers together.
2. Write headings that signal the answer
Replace “Information” and “Other details” with headings such as “Reaching the venue by public transport”. Read the heading alone, then alongside its content. It should describe the subject without promising updated opening hours or booking if the panel provides neither. The W3C headings and labels criterion requires them to describe topic or purpose.
Prepare French, English and Arabic copy before judging the layout. Avoid truncating a heading so far that its difference from the next one disappears. Keep one question per section when this helps people find information, and have the content owner approve the answers. An expansion icon cannot replace an explicit heading.
3. Agree expansion rules before acceptance testing
Record each panel’s initial state: closed or open. Decide whether several answers may remain visible and whether all panels may be closed. In our example, comparing entry conditions and permitted items may justify keeping several panels open. Check this decision with real content rather than two lines of demonstration text.
MDN describes details as a disclosure widget whose summary supplies the label. In a custom implementation following the W3C APG pattern, controls are buttons associated with panels and their expanded state must match visibility. Ask the team to identify its chosen approach: identical appearance does not establish identical behaviour.
Source : W3C APG — Accordion Pattern · Source : MDN — The details disclosure element
4. Navigate panels without a mouse
Start at the top of the page using a keyboard. Find the first panel control, open it, reach a link inside, then return and close it. In the APG pattern, Enter or Space activates the control; Tab and Shift+Tab navigate focusable elements. Check the delivered implementation, including its visible focus indicator.
Observe what happens after closing: hidden links must not become invisible steps in the journey. Arrange checks with the assistive technologies included in the agreed scope to confirm the announced name and state. A keyboard trial provides useful evidence but does not constitute a complete accessibility audit on its own.
5. Repeat the reading journey on mobile and in each language
Open a long panel on a small screen, scroll through its content and reach the next heading. Check links, wrapping and whether neighbouring controls are distinguishable. Open a second panel: the previous answer should remain open or close according to the agreed rule, without making you lose your place in the reading journey.
In Arabic, read headings, body copy and foreign-language fragments in the actual reading direction. Then reload and record which panels are open. Preserving this state, linking directly to an answer or showing it in print are separate needs to agree and test; do not infer them from the presence of an accordion.
6. Keep evidence for each expected behaviour
For each scenario, save the version, URL, language, browser and screen size. Record the initial state, keys or actions used and the final state of each relevant panel. A screenshot of an open panel proves its appearance, not the ability to find the control again or close the answer.
When a difference appears, distinguish an ambiguous heading, missing answer and broken expansion rule. After a correction, repeat the case and check the neighbouring panel. Accept only the observed scope and keep limitations visible. This acceptance exercise proves neither a conversion gain nor improved search-engine rankings.
Collapsible-section acceptance worksheet
| Case | Agreed expectation | Evidence to retain |
|---|---|---|
| First reading | Essential information discoverable | Headings and visible content |
| Successive expansion | One or more panels as agreed | Before and after states |
| Keyboard | Controls and links reachable | Keys and focus position |
| Closing | No invisible navigation step | Journey after closing |
| Mobile and Arabic | Usable reading and controls | Language, screen and observations |
| Reload | State matches the decision | Initial and reloaded states |
Common questions
Should every FAQ answer be collapsed?
No. Decide according to the information people need to find or compare. A short essential answer can remain visible without adding an action.
Is allowing only one open panel always better?
No. Choose according to comparison needs and check the reading journey with real text. Then document the selected rule.
Is a screenshot of an open panel enough for acceptance?
No. Also check opening, closing, navigating links and successive states using the agreed access methods.
Prepare your next check
Choose a page, gather its answers and have someone read the headings alone. Agree the expansion rules, then use the worksheet on a preview in every published language.
Sources and scope
W3C, WHATWG and MDN primary sources checked on 7 November 2026. The visitor page and examples are fictional. Content decisions and the worksheet are an editorial acceptance proposal, without an audit of your website or a compliance certification.
