Template
Wireframe review checklist
Review structure, content and states before moving to visual design.
Wireframe review checklist
Screen / flow: Reviewer:
Purpose and hierarchy
- The screen's main purpose is obvious within five seconds
- One primary action per screen, visually distinct
- Content is ordered by what users need first, not by what the organisation wants to say
- Headings describe the content below them
Content
- Real or realistic content, not lorem ipsum
- Long names, long text and large numbers have been tried
- Labels and buttons use clear verbs ("Book appointment", not "Submit")
States
- Empty state
- Loading state
- Error state with recovery
- Success or confirmation state
- Partial data or very large data sets
Layout and responsiveness
- Mobile layout designed, not just squeezed
- Reading order makes sense when stacked in one column
- Touch targets are large enough and spaced apart
Accessibility (structural)
- A logical heading order
- Form fields have visible labels
- Information is not conveyed by position or colour alone
Open questions for the team
View the Markdown source
# Wireframe review checklist
**Screen / flow:**
**Reviewer:**
## Purpose and hierarchy
- [ ] The screen's main purpose is obvious within five seconds
- [ ] One primary action per screen, visually distinct
- [ ] Content is ordered by what users need first, not by what the organisation wants to say
- [ ] Headings describe the content below them
## Content
- [ ] Real or realistic content, not lorem ipsum
- [ ] Long names, long text and large numbers have been tried
- [ ] Labels and buttons use clear verbs ("Book appointment", not "Submit")
## States
- [ ] Empty state
- [ ] Loading state
- [ ] Error state with recovery
- [ ] Success or confirmation state
- [ ] Partial data or very large data sets
## Layout and responsiveness
- [ ] Mobile layout designed, not just squeezed
- [ ] Reading order makes sense when stacked in one column
- [ ] Touch targets are large enough and spaced apart
## Accessibility (structural)
- [ ] A logical heading order
- [ ] Form fields have visible labels
- [ ] Information is not conveyed by position or colour alone
## Open questions for the team