Content design in beta

During the beta phase, we refine and optimise user experience. We iterate and improve the product or service, testing with real users to make sure content supports a simple, clear and accessible experience.

What content designers do in beta

Our content designers:

  • build on content findings from alpha
  • test prototypes with a select group of users (this is known as private beta)
  • make sure content supports interactions and works within selected components
  • observe user research, continuing to iterate based on user feedback
  • make sure content meets the latest published WCAG guidance to at least ‘AA’ standard
  • share any new content patterns we’ve developed with NHS and GOV design communities
  • collaborate with policy and subject matter experts to ensure content is accurate and compliant
  • collaborate with developers to identify error scenarios and create error messages
  • design accessible URLs and page titles across the user journey
  • work with the delivery team to decide when changes are ready to be released and measured

Improve the playbook

If you spot anything factually incorrect with this page or have ideas for improvement, please share your suggestions.

Before you start, you will need a GitHub account. Github is an open forum where we collect feedback.