Skip to main content
service_manual_guide documents
- Understanding WCAG 2.2
- How the discovery phase works
- 1. Understand users and their needs
- How the alpha phase works
- How the beta phase works
- Making your service accessible: an introduction
- 2. Solve a whole problem for users
- Check if you need to meet the Service Standard or get an assessment
- What each role does in a service team
- Learning about users and their needs
- Agile tools and techniques
- Testing for accessibility
- Data you must publish
- 5. Make sure everyone can use the service
- Naming your service
- 3. Provide a joined up experience across all channels
- Artificial intelligence (AI) community
- 6. Have a multidisciplinary team
- Structuring forms
- Testing with assistive technologies
- 7. Use agile ways of working
- 12. Make new source code open
- 4. Make the service simple to use
- Governance principles for agile service delivery
- Set up a service team at each phase
- Agile methods: an introduction
- Planning and writing text messages and emails
- Get a GOV.UK feedback page
- Agile and government services: an introduction
- What happens at a service assessment
- Writing user stories
- 11. Choose the right tools and technology
- Core principles of agile
- Measuring user satisfaction
- How the live phase works
- Sending emails from your service
- User research for government services: an introduction
- Designing for different browsers and devices
- Designing good government services: an introduction
- 10. Define what success looks like and publish performance data
- 9. Create a secure service which protects users’ privacy
- Making your service look like GOV.UK
- Assisted digital support: an introduction
- How to set performance metrics for your service
- Get a service domain name
- User research in discovery
- Developing a roadmap
- Writing for user interfaces
- Making your service more inclusive
- Plan user research for your service