Open ghost opened 3 years ago
Hi @AJSMITH1512, here's the current guidance: https://service-manual.nhs.uk/accessibility/content#set-page-titles
Is the following text clearer? I'll run it by a few content designers this week, and will check it with the team and Ben too before asking the AWG to approve the change.
Set page names and page titles For: Content, Development, Testing
The page name:
<H1>
tag in the <body>
of the page, for example: "Achalasia"The page title:
<title>
tag in the <head>
section of the pageIf you can, use templates to keep things consistent and use your content management system (CMS) to add the site name after the dash.
Good page names:
@davidhunter08 or @AdamChrimes, for info. This content didn't work well for content designers so I'm going to rethink and chat with Adam and Dom on Friday.
Should probably go to AWG too. I'm testing it with some content designers this morning. @EllenDoyle @georginaplatt, see my Slack message.
We say this in the accessibility guidance: https://service-manual.nhs.uk/accessibility/content#set-page-titles, i.e. Page title - Site name. For example: Achalasia - NHS. I think we're OK on the health content front, because it's templated in Wagtail. But we're not consistent with services. We have some services that follow the GOV.UK pattern: eg: Do you know your NHS number? - Book a coronavirus vaccination - NHS. https://www.nhs.uk/book-a-coronavirus-vaccination/do-you-have-an-nhs-number. And some which don't mention that it's the NHS website, e.g.: Search - Find a walk-in coronavirus (COVID-19) vaccination site. https://www.nhs.uk/service-search/find-a-walk-in-coronavirus-covid-19-vaccination-site
Had a chat with Alistair Duggin and Sarah Norman about this. We know that some transactional services are failing WCAG2.1 AA on page titles. Other pages are not following latest best practice.
Alistair is going to draft a brief note with examples and best practice that could go in the accessibility guidance.
We also need a way to make this guidance easier to find in the service manual. It's not just an accessibility issue.
This all needs further review and testing. Put back into team backlog for now.
See also our draft URL guidance: https://github.com/nhsuk/nhsuk-service-manual-community-backlog/issues/265
The BBC guidance for title is Page name - Section name - BBC
And the GOV.UK guidance is: Page name - Service name - GOV.UK eg https://www.registertovote.service.gov.uk/
Writing for user interfaces says:
"Each page should have a single<h1>
. The <h1>
should describe what the page does.
The <title>
should be based on the <h1>
, and follow this format:
Where do you live? - register to vote - GOV.UK"
Page titles should be short. GOV says "Your title should be 65 characters or less (including spaces). You can use more than 65 characters if it’s essential for making the title clear or unique, but do not do this routinely because:
A lot of our page titles are very lengthy.
I think we've seen teams struggling with titles, H1s and URLs for fail pages.
For example, a service may have quite a lot of pages with the heading "You cannot use this service". The body copy explains why.
The URL will be different in each case and may reflect why this applicant is not eligible. E.g. .../apply/under-16
I'm a new user of the NHS Design system so recently queried the policy on titles.
There's some guidance under the accessibility section, but alas I didn't find it.
Some extra things it would be good to cover:
- NHS
or - NHS App
?I think the app itself might use NHS App
, but we may decide that services within it don't - many things are available both within the app and via the web. If we ask them to add NHS App
to the end of their titles I think it implies the page title being dynamic based on use case - which might be challenging for some services.
What about hyphens, en-dashes etc in title? Does it make a difference?
GOV uses hyphen: Where do you live? - Register to vote - GOV.UK (https://www.gov.uk/service-manual/design/writing-for-user-interfaces#headings-and-title)
Interestingly the NHS.UK CMS uses a hyphen by default, but it would not be v difficult to change this to an en-dash.
What
As part of the review of our accessibility pages, the guidance for content on setting page titles (linked here) needs to be reviewed.
Also, we may want to review where this guidance sits.
Current guidance
Why
The guidance needs to clarify how page titles differ from page names.
We see that quite a lot of people can't find this guidance.
Done when