Collection
Make the task usable across different ways of accessing it
Ten bounded interface checks for keyboard, enlargement, forms, status, speech input, motion, targets and tables.
10 elements · Explore in any order.
3 checklists · 7 protocols
10 elements
Complete the journey with the keyboard alone
Being able to reach a button is not the same as finishing the task.
Read the idea ProtocolMake enlarged text fit the task, not just the screen
A larger sentence is not helpful when its ending disappears.
Read the idea ChecklistGive the colour a second way to speak
The meaning should survive when the colour does not.
Read the idea ProtocolKeep the field’s identity after the user starts typing
A field should not lose its name when it receives an answer.
Read the idea ProtocolMake the error show the next repair
Invalid is a verdict, not an instruction.
Read the idea ProtocolAnnounce the result without stealing the user’s place
Finished should not be a message only sight can hear.
Read the idea ChecklistLet voice commands use the label people can see
The screen says Save. The hidden name should not insist on Commit artifact.
Read the idea ProtocolMake non-essential interaction motion optional
A transition should not make someone pay a physical price for pressing a button.
Read the idea ProtocolTest the target and its neighbours, not just the icon
The finger meets the clickable area, not the design file.
Read the idea ProtocolKeep the headers attached when the table leaves your screen
Bold text is not a relationship.
Read the idea