Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Design, UX and accessibility

    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 person using a keyboard to examine a form displayed on a laptop.
    AI-generated illustration

    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.

    Educational example

    Use the vocabulary to make a decision

    Hands at a keyboard beside a laptop and loupe on printed pages
    AI-generated illustration · Test a task with the keyboard and enlarged text.

    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.

    From a word to an observation

    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.

    Illustrative observations to adapt to your project
    Observed signalWhat to checkWhat it means
    Content shifts while readingObserve images, fonts and blocks inserted during loading.Reserving space for later content helps keep the page stable.
    A button has no visible responseObserve the delay after a real interaction.Responsiveness matters after initial loading too.
    An error is communicated only by colourCheck the explicit message, field association and keyboard journey.The correction must remain understandable without relying on colour.
    Core Web Vitals: thresholds for the “good” category
    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

    1. Name
    2. Email
    3. Send

    Observed keyboard sequence

    1. Name
    2. Send
    3. Email

    Proposed order after correction

    1. Name
    2. Email
    3. 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.

    Examine the interpretation

    An image’s role depends on context

    Fictional teaching case. Open each interpretation to examine its scope; there is no score or professional assessment.

    1. Function identified
    2. Information compared
    3. 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?

    Decide according to its role in each placement

    A decorative image can have an empty alternative. When it supplies necessary information, make that information accessible in a suitable form.

    Automatically reuse the filename

    A filename may not describe the information needed. Repeating it can create noise or leave an important detail unavailable.

    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 .

    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.

    Related topics