Hint text for text input

[AndyLongContent]

Screenshot

What problem does this design solve?

Which service are you researching this design on?

How have you approached the design?

• have you tried anything that exists already?

What have you learned from research?

• include any iterations that didn't work.

Have you tested this for accessibility?

• if so, what were the findings?

Link to code

• if you need help publishing your code to the design-examples repo contact Colin Oakley or Craig Abbott.

[AndyLongContent]

There are some inconsistencies with how and when/if we use hint text for text inputs across our services. There is also contradictory user research evidence on whether users actually read hint text, depending on the service.

It would be good to find some consistency on when we should use hint text, and if we do, the styles we adopt (full stop at the end, or not, etc.)

[simonbusch]

Design system doesn't say whether hint text needs a full stop. See examples on this page with and without one: https://design-system.service.gov.uk/components/error-message/

We need to make a local ruling on how to punctuate. Options include:

• use full stops in all cases because easier for people using screen readers
• use only for full sentences but not for standalone phrases, eg, 'For example, 31/3/1980'

[HelenOsg]

New ticket created in backlog