Native `<details>` elements will work in most
evergreen browsers but the details component from
GOVUK Frontend adds missing accessibility
information through ARIA.
accented characters rather than special characters. call them accented
as special is a bit wishy washy and doesn't explain what they actually
are. "Diacritics" is correct but too technical. Accented characters is
a happy middle ground
screanreaders struggle to distinguish accented letters, capitals, etc,
so by having a simple two column layout we can have the full unicode
glyph name, removing any ambiguity.
So that you don’t have to use the footer navigation to switch between
these related pages. Matches the template we use for organising
features-related content.
