A long online guide: a table of contents that helps readers return to their question
Design guide navigation with clear headings, reliable section links and understandable paths back to the content.
Article language: English

In this article
“It's in the guide, in the preparation section,” a colleague writes. The guide runs for more than ten screens, has three headings called “Preparation” and a menu bar that hides the required heading when clicked. The information exists. Finding it starts to feel like a test of how well you know the author.
People read a long online resource in different ways. One person reads it all, another checks a condition, and a third returns to the point where a phone call interrupted them. A table of contents should support those paths, not merely show how many chapters were written. The design includes names, links, the view after navigation and what happens on return.
Consider a fictional guide to preparing a trade-fair stand. The organiser describes registration, materials, delivery and assembly. Several different tasks therefore sit under the word “preparation”. The person responsible for transport needs only the condition for collecting equipment. They must still know whether it applies to their day and delivery type. A jump to the right paragraph is not enough if the context disappears on the way.
A table of contents begins with editing
First collect readers' questions and see which parts answer them. “Delivering equipment before the event” gives a better idea of what to expect than “Stage two”. If a chapter combines delivery and assembly only because the same employee describes both, the division reproduces the company's structure instead of the audience's needs.
Read only the headings, without their accompanying text. They should give a recognisable picture of the material. Look for repeated labels such as “Information”, “Rules” and “Other”. These need clarification. Three similar links in the contents will not help readers choose the right one, even if each technically leads to the correct place.
WAI's guide to headings explains that headings communicate the organisation of content and can support navigation within a page. Their levels should reflect a logical hierarchy. Skipping levels when opening subsections can be confusing.
In the design, distinguish a chapter from a part within it. Letter size and colour can show the division, but it should also come from the document structure. “Collection outside assembly hours” could belong to the delivery chapter. Show that relationship in the contents instead of presenting every entry as an equal peer.
Not every subheading must appear in the main contents. With many small points, the list can become another long document before the guide itself. Select levels that help people decide where to enter. In a longer list, also check how names wrap. Two lines of one link should not look like two separate entries, and an abbreviated label must not hide the difference between collection and delivery. If more detailed navigation is needed, it should keep a clear hierarchy and avoid covering content on a small screen.
Links may repeat headings or use an abbreviation that preserves their meaning. Do not shorten a title to “Transport” if it covers conditions for delivery, collection and removal and readers must distinguish them. An abbreviation should reduce length, not change the promise.
Distinguish this navigation from breadcrumbs showing a place in the site (in Polish). Breadcrumbs can show that the guide belongs to the exhibitors' section. The contents lead to parts of this one guide. Both are useful, but should not have identical labels or pretend to solve the same task.
A link should lead to a recognisable place
An anchor is a marked place in a document reached by a link with an address fragment after the hash sign. For readers, the result matters more than the mechanism's name: on arrival they should see the relevant heading and some content. The team creating the page should check this in the finished layout.
In our guide, a link to equipment collection must not land with its heading hidden beneath a sticky menu. Someone seeing the middle of a sentence immediately may think they have arrived at the wrong place. Check the target heading's position, the space above it and what occupies the top of the screen.
MDN's documentation for scrollIntoView shows how scroll-margin-top and scroll-margin-bottom can set an offset when aligning a scrolled element. It notes their usefulness when a header remains at the top of the viewport. This is a technical means; acceptance still concerns the visible result.
Do not set one offset based on a wide screen and call the task complete. The bar may have a different size when text is enlarged, the language changes or menu items wrap. In a trial, inspect the heading in those states too. If two bars overlap, account for their combined effect.
When the contents highlight the section currently being read, agree what that signal means. After a reader selects a chapter and manually scrolls farther, the old highlight should not pretend to indicate the current location. Also distinguish the current-section state from a previously visited link. In a short trial, ask a reader to indicate where they are after scrolling and how to reach the neighbouring section. If they must guess what colours mean, improve their explanation and behaviour.
Preserve the context of a condition. A chapter may begin “applies to deliveries on the day before the event”, while a link leads farther down to the collection time. Someone entering directly from a colleague's message did not see the beginning. At the specific condition, show enough indication of its scope or lead to a place where readers can recognise it before using the information.
Treat exceptions similarly. If a timetable has a separate note for large loads, the jump should not make the ordinary time appear to apply to everyone. You do not need to repeat the whole chapter beside each row. Choose a visible connection that survives a narrow screen and entry into the middle of the document.

Assess keyboard operation too. Scrolling the screen and the place from which a user continues operating are separate observations. After choosing part of the contents, check whether the onward path makes sense, whether the current element is visible and whether the person can reach the right content. Do not infer this from animation alone.
Do not impose a long, smooth journey through the entire document as the only way to reach the end. The aim is to find a place. Motion can help orientation, but should not delay a simple jump or hinder someone who needs reduced animation. Check the solution against the settings adopted in the project.
If a section is inside a collapsible element, entering through a link should lead to information that can be reached. We discuss when hiding content helps in an accordion on a service page (in Polish). For the guide, also decide what happens when an address to a collapsed section opens. A closed heading alone may not fulfil a link's promise to take someone to a specific condition.
Returning and sharing are part of reading too
A heading can offer a way to copy a link to that section. Describe the action clearly, especially if it is represented only by a small icon. People should know whether they are copying the chapter's address or opening somewhere else. Afterwards, show an understandable confirmation that matches the actual outcome.
Check the copied address in a new tab without first opening the guide. This exposes dependence on state the tester already had prepared: an expanded section, a selected variant or a loaded fragment. The link's recipient does not automatically inherit those same conditions.
The Back button should behave in a way readers can understand. Several jumps between sections may affect history differently depending on implementation. Agree on the expected path and check it in the finished solution. After several jumps, also test returning to the page from which the guide was opened. Readers should understand whether they are going back between sections or leaving the document.
After visiting an external resource and returning, a person wants to find their reading place. Check this on the actual guide, particularly if images or other elements load later and shift the text. A position measured only in pixels may no longer mean the same paragraph after the layout changes.
On a phone, the contents may become an expandable list or a short block at the top. It should not occupy the entire screen throughout reading. If it remains available, let people recognise its state and return to the content. A large navigation overlay should not force someone to look for their sentence again after every selection.
Aeneia Design Let us design navigation for a substantial guide around readers' questions, durable links and the view after navigation. We will check entry to a specific condition and returning on a phone and with a keyboard. Make a long guide easier to navigate
Decide separately how return works in the same browser and how reading continues on another device. If the design saves a position for a later visit, show readers how to recover it. If only a section address is available, explain how to copy and open it later. A bar showing scroll percentage alone does not save a place for the next visit.
Editing text should not break its addresses
Give sections stable identifiers. Improving a heading's wording need not change the place old links lead to. Agree on that rule in the publishing process. If the system generates an identifier from the current heading every time, check the effects of editing before sharing a new version.
When two sections are combined or one is split into several, decide where their old addresses lead. Opening the beginning of the whole guide is not enough. Someone looking for a collection time would lose the promised location. When old information no longer applies, explain the change and show the relevant scope rather than directing people to a similarly named heading.
With several language versions, test switching from inside the document. If the same chapter exists in the selected language, preserve a recognisable subject. If it does not, name the limitation. Check the address after the language change as well as the view. If the person shares it, the next reader should receive a recognisable version and part of the guide. Record the expected result for the particular publishing system; a similar chapter name alone does not confirm that addresses are linked. Returning to the top without explanation can mislead someone who expected only to change the language of the same condition.
Also assess the accessibility of this path with people using appropriate tools. Research with people using assistive technologies (in Polish) helps plan a trial of actual orientation. A participant should find and understand the condition, not reproduce a sequence of clicks prompted by the author.
An AI-assisted automated accessibility audit (in Polish) can supply some observations, but cannot replace checking the meaning of the whole path. The correct presence of a heading does not establish whether its name helps someone choose a section or whether the relevant context is visible on arrival. Record what was assessed automatically and what was assessed in a user trial.
If the material also remains in a file, decide the role of both versions. PDF or HTML on a company website (in Polish) helps select a format for the task. A link to a section of a web page should not be presented as an address for the same page in a PDF when the documents use different divisions and numbering.
Before acceptance, choose three real questions and give a reader direct addresses to places with answers. Ask them to state the scope of a condition, move to a neighbouring chapter and return. Then change one heading in a controlled copy and check old links. This is a proposed design trial, not a description of research carried out for this article.
In the Aeneia Design offer, such a guide can be treated as a content and navigation project together. A good map will not shorten every chapter, but it can help someone enter the right one, understand its scope and return without messaging a colleague: “Where exactly was that preparation section?”







