Understand design, UX and accessibility
Design organises what people perceive and can do. Examine content, component states and interaction modes together. Useful design also explains what happens with larger text, an error or an image carrying no information.
81 concepts to explore with definitions and practical advice.
Search the full glossary
A reading path
1. Guide reading
Visual hierarchy helps identify page purpose, decision information and action. Headings and links should retain that meaning in document structure.
- Visual hierarchy
Graphic organization indicating what should be seen and understood first through size, contrast, space and position.
- Information architecture
Organization of content, categories, labels and navigation paths so information is easy to find and understand.
- Reading order
Sequence in which page or document content is encountered, including by keyboard or assistive technology.
2. Describe interactions
A component has a state and purpose. Define label, help and error so implementation retains keyboard and small-screen behaviour.
- Accessible name
Name used by assistive technologies to identify an element, such as a field or button. It should convey purpose and remain consistent with the visible label. Inspect the computed name in the accessibility tree: an icon that makes sense visually can still be unnamed for a screen reader.
- Component state
An interface element’s condition, such as selected, expanded, unavailable or busy. Make it perceivable and consistent with behaviour; a colour change alone does not explain available actions.
- Field error message
Text associated with rejected input that identifies the problem and helps correction. Distinguish invalid format from processing failure, and avoid unnecessarily clearing other valid answers.
3. Observe the experience
Try a specific task with enlarged text and realistic content. Performance metrics provide additional observations rather than replacing journey checks.
- Usability
Ease with which users can understand an interface, complete tasks and avoid or recover from errors.
- Responsive design
Design that adapts layout, media and text to available space. Flexible grids alone are insufficient: also check navigation, long content and essential tasks at intermediate widths.
- Cumulative Layout Shift
Cumulative Layout Shift (CLS): visual-instability metric based on unexpected element shifts. It can be affected after initial loading, for example when content is inserted late.
Useful distinctions
Alternative text / Accessible name
Alternative text matches an image’s role. An accessible name identifies a control or element to assistive technology. An image used as a control should communicate its useful action.
Wireframe / Mockup
A wireframe explores structure and content placement; a mockup details presentation further. Neither proves the interface works in a browser.
Use the vocabulary to make a decision

Situation
A form works with a mouse but its error is unclear with a keyboard.
Before deciding
Connect the message to the affected field and check control name and navigation order. A more visible colour alone does not solve the problem.
A concrete check
Repeat the error with intentionally invalid input and check how someone finds the field to correct.
Observe reading, keyboard use and stability
Tie a visual check to a task: read an offer, find an answer or correct a field. Technical measurements complement this observation but do not independently establish accessibility.
On a narrow screen, scroll the table horizontally to read all three columns.
| Observed signal | What to check | What it means |
|---|---|---|
| Content shifts while reading | Observe images, fonts and blocks inserted during loading. | Reserving space for later content helps keep the page stable. |
| A button has no visible response | Observe the delay after a real interaction. | Responsiveness matters after initial loading too. |
| An error is communicated only by colour | Check the explicit message, field association and keyboard journey. | The correction must remain understandable without relying on colour. |
- LCP
- ≤ 2.5 sLargest visible content rendering
- INP
- ≤ 200 msInteraction responsiveness
- CLS
- ≤ 0.1Visual stability, unitless score
Assess the 75th percentile of field observations, separating mobile and desktop. These thresholds are not measured scores for this page. A Lighthouse navigation test uses TBT as a laboratory indicator, not as an INP measurement.
Next step : Fix the obstacle affecting the task, repeat the journey and compare measurements under equivalent conditions.
Technical reference : web.dev — Web Vitals. The scenarios and numerical examples above are educational, not measurements of this website.
Compare visible order with keyboard navigation
In this form example, the display suggests Name, Email, Send, but the observed sequence reaches Send before Email. The proposed correction puts the fields before the final action. The actual journey still needs testing in both directions, including whether errors are understandable.
Proposed visible order
- Name
- Send
Observed keyboard sequence
- Name
- Send
Proposed order after correction
- Name
- Send
A different order is not automatically an accessibility failure: it must preserve meaning and use. This educational diagram certifies no actual form.
Reference : W3C: Focus Order.
An image’s role depends on context
Fictional teaching case. Open each interpretation to examine its scope; there is no score or professional assessment.
- Function identified
- Information compared
- Alternative adapted
An image accompanies text that already supplies all useful information. Elsewhere, the same image shows a detail the text does not describe.
Should the same alternative be reused everywhere?
A useful next step : Establish what a reader would lose without the image. Choose an alternative for that function rather than for the file alone.
Reference to explore : W3C WAI · An alt Decision Tree · Consulted .
All concepts in this topic
Links open the full definition on its alphabet page. Acronyms and synonyms remain searchable in the main glossary.
- Above the fold
- Accessibility conformance report
- Accessibility tree
- Accessible description
- Accessible entrance
- Accessible name
- Active filter
- Alternative text
- ARIA
- ARIA live region
- Art direction
- Breadcrumb trail
- Breakpoint
- Carbon-aware design
- Chart description
- Comparison table
- Component state
- Cumulative Layout Shift
- Dark pattern
- Design token
- Digital accessibility
- Download link
- Drag and drop
- Error summary
- European Accessibility Act
- Fallback font
- Favicon
- FID
- Field error message
- Figma
- First Contentful Paint
- Focal point
- font-display
- Glyph
- Hamburger menu
- Hero section
- Icon
- Image optimization
- Information architecture
- Interaction to Next Paint
- Interface component
- JPEG
- Kebab menu
- Largest Contentful Paint
- Lighthouse
- Main navigation
- Media query
- Mobile job application
- Mobile menu
- Mobile-first
- Mockup
- Navigation
- No-results state
- Overlay
- Page speed
- Pagination
- Performance budget
- Pixel
- Professional portrait
- Reading order
- Responsive design
- Sort order
- Submission confirmation
- Synchronized captions
- Tagged PDF
- Template
- Typography
- UI
- Usability
- User flow
- UX
- Vector image
- Video thumbnail
- Viewport
- Visual hierarchy
- WCAG
- Web design
- Web form
- WebP
- Wireframe
- z-index
Frequently asked questions
Does a good score prove accessibility?
No. An automated tool covers some defects in a particular context. Add content, keyboard and representative journey checks.
Must every image be described?
Choose alternatives by purpose. Decoration differs from an informative image, chart or button. Keep essential information accessible within page context.
Primary reference documents
These documents explain technical concepts. Reading paths and examples are editorial methods to adapt to your project.