content-and-usability.md

Check content and usability

This task is to ensure that the service is understandable, simple to use and consistent with the GOV.UK guidance.

System set-up

Not applicable.

Testing notes

HMRC services should follow:

• GOV.UK Design System
• HMRC design patterns
• GOV.UK Content design: planning, writing and managing content
  • GOV.UK Style guide
  • HMRC content style guide

What to look for

• established design components and patterns followed
  • page title matches the level 1 heading <h1> and also includes the service name [page name] - [service name] - GOV.UK (each page title should adequately describe and be distinguishable from other pages)
  • hint copy and error messages conform to the standard messages
  • usage of microservices, for example, address lookup frontend, autocomplete component
• heading hierarchy is correct - this should provide a table of contents with headings correctly nested and no heading levels skipped
• for content
  • structured with headings, paragraphs and lists
  • plain English is used
  • consistency of terminology used
  • cognition load not overloaded, for example, check your answers page follows the user journey steps
  • the user is informed if selecting a link will open a new window
• on forms
  • ask only required questions; additional inputs are marked as "optional" in the label
  • inputs have visible label
  • ensure hints and error messages are associated with input (or with fieldset when used)
  • no other content is present between form elements, for example, a warning message before a submit button may be missed by screen reader users navigating using shortcut keys
  • check data is re-populated when navigating through completed screens
• for tables
  • used only for comparison data, not for layout
  • have a caption
  • have correct markup for column and row headings and the headings make sense
• any auto-updating content or auto-playing video or audio can be paused, hidden or stopped
• check videos contain captions and transcripts
• check support links (for example, in the footer) are consistent and present on each page
• make sure language translations are complete
• if the service has a session timeout, a timeout dialog allows the user to extend their session
• check printed content (print preview)