Learning pages
Short, practical guidance you can use today and share with your team.
Writing error messages people can fix
A good error message says what went wrong, where, and how to fix it, in that order: "Enter your email address in the format name@example.co.uk" rather than "Invalid input". Put the message next to the field and at the top of the form, keep what the person typed, and never use colour alone to show the problem.
Instead of
"Error 422: validation failed"
Try
"Enter a date in the past, for example 27 3 2024"
One field
"Full name", plus "What should we call you?" if you need it.
Asking for names respectfully
Not everyone has a first name and a surname, or uses them in that order. Some people have one name; some have several family names. A single "Full name" field accepts them all. Allow accented characters, apostrophes and hyphens, and never reject a name for being "too short" or "too long" within reason.
The five-minute keyboard test
- Click in the address bar, then press Tab repeatedly.
- Can you always see where you are?
- Does focus move in a sensible order?
- Can you open menus and close them with Escape?
- Can you complete the main task without the mouse?
If any answer is no, people who use a keyboard are stuck there too.
Readable documents
Use real headings, not bold text. Left-align text. Describe images. Use at least 12-point text in a plain font. Avoid scanned PDFs where possible; screen readers cannot read a picture of words.