Graham-Pembrey
commented
1 year ago We tested using the contents list component as a ‘table of contents’, placed at the top of a very long page. We used it as a list of In-page anchor links, which dropped users down to sections of the page. The page we were testing was an NHS.UK template prototype page, showing a possible presentation of the NHS App privacy policy.
Before creating the prototype, we were conscious that:
- Contents lists are usually used on the NHS website to link to related pages, rather than within a page.
- GOV.UK guidance cautions against in-page links, because they may be disorientating for some users.
However, we noted that NHS Login had used this presentation on their privacy policy. They shared research with us showing that it tested well with users. WCAG also have guidance on using this style of table of contents in an accessible way. As do the charity Mind who use it on their pages. This gave us confidence to try the design.
The content was tested with both users without any stated access needs, and screen reader users who were blind or partially sighted. For screen reader users we found that:
- In-page anchor links were familiar and easy for them to use.
- Returning to the top of the page could be an issue. Some told us they would navigate by heading back to the main H1 quite easily. Others told us they would prefer a ‘back to the top’ link.
- More technologically confident users were able to search the page comfortably by keyword when looking for specific information.
- One screen reader user found that the links in the contents list did not work. We are not sure what caused this, but it highlights the potential for varying experiences depending on the technology used.
@sarawilcox
Use this issue to discuss contents lists in the NHS digital service manual