-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate when hidden 'Support Links' heading in footer is helpful #1763
Comments
For context, this visually hidden heading has been used in the footer by GOV.UK for nearly 7 years: I think the heading probably does make sense in the context of GOV.UK, where the additional links in the footer immediately follow other lists of links with their own headings – without it, a screen reader could interpret is as a continuation of the previous list. However, my initial reaction is that it might not be necessary when the 'meta' links are the only links in the footer (which will be the case in a number of services)? |
That sounds right to me - I guess that for most GOV.UK services, the list of support links will follow the 'Continue' button rather than another list of links? That said, this seems like a good example of the subtle differences in optimising the design system for GOV.UK transactional services vs optimising it for creating static websites. |
We should also make it possible to localise the text as per this comment. |
I was just auditing the Prototype Kit site and came across this - 'Support links' doesn't really describe whats in the footer, and as it was hidden, I didn't even realise there was a heading there to check. Maybe the heading could be opt in, or flagged as something to check when getting started? |
What
The footer has a hidden 'Support Links' h2 in the footer:
govuk-frontend/src/govuk/components/footer/template.njk
Line 35 in ce2a717
This was flagged in another departments audit as potentially confusing:
We should better understand in what situations this heading is useful (or not), and whether there's a better default heading that we could use.
(The heading can be overridden by setting
params.meta.visuallyHiddenTitle
, but it cannot be removed)Why
We want to ensure that the footer is as accessible as we can make it.
The text was updated successfully, but these errors were encountered: