Reformat search results metadata to be more verbose

[owenatgov]

Just a draft at the moment. Full description coming soon

[netlify]

✅ You can preview this change here:

Name	Link
🔨 Latest commit	5f6b3ec
🔍 Latest deploy log	https://app.netlify.com/sites/govuk-design-system-preview/deploys/673381d0e896e90008239a54
😎 Deploy Preview	https://deploy-preview-4290--govuk-design-system-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[calvin-lau-sig7]

Here's my thinking for showing the results:

• [Page] in [section]
• [Heading], part of [page] in section]

[owenatgov]

I ran accessibility testing against this PR and the 3 other PRs with different methods to visually and programatically highlight the pages and sections in metadata:

• Reformat search results metadata to be more verbose - quotes #4302
• Reformat search results metadata to be more verbose - italics #4301
• Reformat search results metadata to be more verbose - bold text #4300

My general analysis of these findings: None of these 3 methods really make a difference to identification of sections and pages specifically for those words in screen reader audio. Quotes start imacting readout, notably for JAWS and Talkback, but not for any other screen readers.

From off-github chats, we're starting to lean towards not having any extra indiciation as the content of the readout provides context. On the other hand it gives us some freedom to experiment since at least these techniques don't impact screen readers.