cds-snc / cds-snc/content-patterns

Please and sorry

Open
#1 0 comments 0 reactions 0 assignees View on GitHub
Tone | Ton
Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

# Decision: Avoid please and sorry

## Rationale for why

- There's usually no need to say sorry, please or thank you, when writing for usability.
- Be direct, get to the point. This helps front-load content and aids scannability.
- Based on the hypothesis that people don't need politeness from government content.

## Examples in context

![Image](https://user-images.githubusercontent.com/38330843/233715278-30056ae5-47d7-4681-b5fd-372576446131.png)

## Sources to reference

https://www.gov.uk/service-manual/design/writing-for-user-interfaces#tone
https://design-system.service.gov.uk/patterns/problem-with-the-service-pages/

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.