Inclusive forms: Anatomy of a (fictional) GOV.UK service

Last night I spoke for the first time at the London Accessibility Meetup.

I talked about how we build inclusive online forms across government, using a fictional GOV.UK service as an example.

To those who weren’t able to make it, the talk is available on YouTube.

In putting it together I found myself pulling together information from loads of different blog posts, previous talks, and from pull requests and issues from GitHub.

This is an attempt to link out to all of those things, for anyone that wants to find out more.

Have I missed something out here? Feel free to edit this post on GitHub and raise a pull request.


1. Start Page

Naming your service using verbs, not nouns

Conveying page structure using headings

Clear and consistent focus states

2. Have you held a juggling licence before?

Supporting users who change colours in their browser

Start with one thing per page

Making a legend a heading

Custom radio buttons and checkboxes

3. Previous licence details

Form layout

Asking for dates

Helping users understand when there is a problem

Linking from the error summary to different fields

Associating the error message with the input

4. What is your most impressive juggling trick?

Making a legend a label

Providing feedback using a character count

5. Check your answers

6. Confirmation page


  • ‘Register as a childminder’ is built by Ofsted, not the Department for Education.