Category: Design systems

  • Web accessibility and design systems: building inclusion into every component

    Web accessibility and design systems: building inclusion into every component

    Web accessibility is more reliable when it is built into the design system rather than added at the end. That does not automatically make every interface accessible. Shared components, rules and tests do, however, prevent the same mistakes from recurring from one screen to the next.

    An unclear button, a field without a label or a modal that cannot be closed with a keyboard are not small isolated flaws. If the same component appears on ten screens, the problem appears ten times. A well-defined component provides a safer starting point for every new page. That is a very practical function of a design system.

    Turn an intention into a reusable rule

    Saying “we need to think about accessibility” does not guide a team. That intention needs to become choices that are visible in mockups, documented in the system and verifiable in the product. Start with what appears everywhere: buttons, links, form fields, alerts, tabs, menus, modals, cards and tables.

    For each component, the design system should define its purpose, permitted variants and states. A button is not just a colour and a label. It can be active, hovered, focused, disabled, loading or unavailable. A field can be empty, completed, required, invalid or valid. If these situations are neither designed nor named, they will often be improvised during development.

    The logic of atomic design helps apply the same behaviours from one element to the next.

    Design components around their real states

    A useful component shows what happens when someone acts, hesitates or makes a mistake. For an email field, for example, the system should provide a visible label, an indication of the expected format when it helps, error handling and text that explains the error. Red alone is not enough. There needs to be a clear message associated with the relevant field.

    The same principle applies to alerts. A success, error or information notification must be understandable through its text and context, not only through an icon or colour. A trash icon needs an accessible name when it triggers an action. A decorative pictogram, by contrast, should not add noise for readers.

    Component decision What to document in the system What to check in the product
    Button Action label, focus and disabled states, loading behaviour Usable with a keyboard, understandable action, visible focus
    Form field Label, help text, required status, error and input example Message linked to the right field, clear error, consistent reading order
    Modal Trigger, title, closing behaviour, focus return Opens and closes with a keyboard, focus kept within the modal
    Navigation Active state, submenus, labels and item order Predictable journey, access without a mouse, explicit links

    Keyboard access and focus are not technical details

    Many interfaces feel smooth with a mouse, then become confusing as soon as the Tab key is used. Keyboard navigation must therefore be part of the design scenarios. Focus should follow a logical order, remain visible and not disappear behind an animation or a colour that is too subtle.

    Labels, errors and contrast that genuinely help

    Web accessibility also depends on simple words. “Submit” is often clearer than “OK”. “Create my account” describes the action better than an arrow on its own. Labels should state what will happen. Help text should resolve a specific hesitation.

    Errors need the same care. “Error” says neither what is preventing progress nor how to fix it. “Enter an email address in the format name@domain.com” gives direction. The system can provide a message structure, but content teams need to adapt it to each situation.

    For contrast, plan colour pairs for text, surfaces, borders and states. An attractive palette does not guarantee that every use will work. Test text against its actual background, including links, focus states, secondary buttons and status messages. Colour should reinforce information, never be its only carrier.

    Make content, design and development work together

    An accessible design system is not the responsibility of one discipline. Content teams define useful labels and errors. Designers create states and priorities. Developers choose appropriate structure and behaviours, then check the result in the browser. The same rule must be understandable to all three disciplines.

    On SourceHub, Fauves worked with the product and development teams, aligning mockups, wording and micro-interactions with the product’s mission and technical constraints, through to development.

    A brand system and a design system also benefit from working together. Our article on the link between a brand system and a design system shows how shared rules can preserve consistency from one touchpoint to the next. In accessibility, this also applies to words, contrast, components and behaviours.

    Document and test at every stage

    Documentation should not be limited to a library of screenshots. For each component, it can state when to use it, when not to use it, the content it needs, the states to provide, keyboard rules and error examples. A short, concrete rule is easier to follow than a vague instruction.

    Testing complements that documentation. Check new components in real cases: keyboard navigation, focus visibility, message comprehension, contrast in different states and behaviour on mobile. Automated tools can spot some issues. They cannot judge whether a label is clear or whether a journey is logical. A manual review remains necessary.

    A practical checklist before adding a component

    • Is its purpose and use clearly defined?
    • Are all useful states designed and named?
    • Can it be reached and used without a mouse?
    • Is focus visible and placed logically?
    • Do the labels explain the action or information?
    • Do errors state what to correct and how?
    • Does the information remain understandable without relying only on colour?
    • Are the rules documented for content, design and development?
    • Has the component been checked in a real interface?

    Resources

    For a closer look at the core principles and recommendations, consult the Web Content Accessibility Guidelines (WCAG) from W3C. They provide a useful foundation for organising discussions, design criteria and checks throughout a project.

    Are you building or redesigning a digital product? Fauves can help you turn inclusion principles into design and development decisions that fit your existing system. Let’s talk about your project.

  • Atomic design: structuring interface components as a product evolves

    Atomic design: structuring interface components as a product evolves

    Atomic design helps an interface evolve without redesigning everything for every new page. It organises reusable elements: buttons, fields, cards, content blocks and templates. When a page changes, the team knows what to reuse, what to adapt and what to maintain.

    Think of the interface as something that can change

    An interface rarely stays still. An offering becomes clearer, a journey gets shorter, a feature appears, a team shifts its priorities. Without a structure, adjustments pile up: a slightly different button, a card tailored to one page, a typography rule forgotten in a file, mobile behaviour addressed too late.

    Atomic design offers a practical response. It breaks the interface into components that are simple enough to understand, complete enough to reuse and documented enough to change without surprises. A form field, for example, is not just a border and text. It includes its states, label, helper text, error message, keyboard behaviour and mobile version.

    The vocabulary popularised by Brad Frost, atoms, molecules, organisms, templates and pages, can act as a guide. It should not become doctrine. Some teams will be more comfortable with “foundations”, “components”, “sections” and “pages”. The goal is not to classify every element perfectly. It is to make dependencies visible and to reuse the same decisions.

    Atomic design, design system and brand system: three distinct roles

    These ideas complement each other, but they do not mean the same thing.

    • Atomic design structures the way an interface is composed. It helps decide what becomes a component, what belongs in a variant and what remains specific to a context.
    • The design system brings together components, rules, documentation, accessibility principles, usage guidelines and governance. It can draw on atomic design, but does not have to.
    • The brand system frames how the brand is expressed: tone of voice, visual identity, hierarchy, motion, iconography, editorial rules and adaptation across channels. It guides the interface, but goes beyond it.

    In practice, the brand system answers: “How is the brand recognised and how does it adapt?” The design system answers: “How does the team design and deliver consistently?” Atomic design answers: “How do interface building blocks fit together without multiplying unnecessarily?” To explore the relationship between the first two levels, read our article on the brand system and the design system.

    Put the method to work for the product

    Do not start with an empty component library. First, look at the screens and journeys that matter. Where do the same patterns recur? Which elements actually change with context? Which decisions are creating inconsistencies or slowing development today?

    Step Decision to make Useful deliverable
    1. Audit Identify recurring patterns and duplicates. Screen audit and component list.
    2. Define foundations Set rules for colour, typography, spacing, grid and states. Documented tokens or baseline rules.
    3. Compose Group elements that serve a clear use case. Components with limited variants.
    4. Test in journeys Check that components support real cases, including on mobile. Reference screens and usage feedback.
    5. Evolve Clarify who decides, documents and deprecates. Simple contribution rules.

    This progression avoids two pitfalls: creating an abstract catalogue that answers no need, or allowing every page to become an exception. A card does not necessarily deserve to become a standalone component when it first appears. But when the same need returns across several journeys, it is better to formalise it than to improvise each time.

    Decisions and risks to own

    A set of components does not remove choices. It makes them explicit. Before creating a variant, ask whether it answers a lasting need or a one-off circumstance. Before adding a colour or spacing value, check whether the existing rule is truly insufficient. This discipline keeps the system readable.

    • Risk of over-componentisation: breaking things down too far creates assemblies that are hard to understand. Keep components focused on an identifiable use case.
    • Risk of infinite variants: every added option increases the cost of testing, documentation and maintenance. Prefer intentional choices to universal properties.
    • Risk of a design-development gap: a component designed without behavioural rules is not enough. Define its states and constraints with the people who will build it.
    • Risk of late accessibility work: contrast, focus, error messages and keyboard navigation must be part of the component from the outset. Find the essential guidance in our article on accessibility and the design system.

    SourceHub: a structure built to move

    At SourceHub, the product evolved every week. Fauves developed the identity and interface with the project and development teams, rather than treating the brand as a layer added afterwards. The mock-ups, wording and micro-interactions were aligned with the product’s mission and technical constraints.

    This way of working called for a modular, adaptable brand. The components did not only save production time: they provided a shared framework for change while giving the product the flexibility it needed. Discover the SourceHub project.

    Resources

    Evolve without losing the thread

    A good set of rules does not prevent change. It helps teams make changes without losing consistency, speed or the purpose behind decisions. If your interface is growing faster than its rules, let’s talk about the structure to build.

  • From brand system to design system: translating an identity into an interface

    From brand system to design system: translating an identity into an interface

    A design system turns brand choices into practical reference points for designing an interface and helping it evolve. It replaces neither positioning nor strategy. It prevents teams from having to reinterpret them for every new screen.

    The brand system sets the direction

    A brand system brings together the choices that make a brand recognisable: its role, personality, language, visual principles, message hierarchy and way of building a relationship. It helps answer simple questions: what needs to be understood? What impression should remain? What tone fits the situation?

    This framework is not just a visual identity guide. A colour, typeface or illustration only makes sense when it supports an intention. A brand may aim to feel precise without becoming cold, accessible without becoming patronising, committed without overstating its message. These choices start with substance before they are expressed visually.

    In a digital product, that direction is tested in every interaction. People do not encounter the brand only once, on a homepage. They find it again in a form, a search, a notification, an empty state or an error message. Everyday details matter too.

    The design system makes that direction repeatable

    The design system brings together the rules, components and decisions that help an interface stay consistent over time. It translates the identity into specific situations: how a button draws attention, how information is prioritised, how a message is written or how an element responds when someone uses it.

    It does not plan every screen in advance. It gives the people designing, writing and developing the product a shared vocabulary. A new feature can then follow the same logic without mechanically copying what already exists.

    A design system does not create the strategy. It helps apply it as the product evolves.

    UI kits, components and tokens: three useful levels

    These terms are often used together, but they do not mean the same thing. Telling them apart prevents a design system from being reduced to a library of attractive screens that is hard to maintain day to day.

    • A UI kit brings together interface elements ready to assemble: buttons, fields, cards, menus, icons or text styles. It is a valuable design resource, but it does not explain when to use each element.
    • A component is a reusable element that combines appearance and behaviour. A button, for example, can have different levels of importance, loading or disabled states, and a label that follows a language rule.
    • Tokens are named, reusable decisions, such as a text colour, spacing value, corner radius or font size. They avoid making the same choice in isolation and make consistent adjustments easier.

    The design system connects these three levels to an intention. It does not simply say that a button is blue or that a card has a certain amount of spacing. It clarifies what needs emphasis, what should remain secondary and what makes content easier to read. Components and tokens are means. The decisions they carry remain at the heart of the system.

    A decision table before multiplying elements

    The number of components is not enough. What matters is the choices the team can make in the same way. This table does not replace design work. It gives examples of decisions a design system can make explicit.

    Interface situation Decision to make explicit Intended effect
    A primary action is expected Define a priority button and the cases where it is justified Make the next step clear without giving everything the same weight
    Information needs attention Choose a hierarchy for headings, body text and supporting information Make information easier to understand before taking action
    An action fails or is unavailable Provide a state, a message and a possible solution Inform people without leaving them stuck
    A new feature is added Reuse a component or define a justified exception Let the product evolve without diluting its language

    The brand also lives in micro-decisions

    An interface expresses an identity through its rhythm, words and responses. An overly technical label can contradict a brand that promises clarity. A crowded screen can weaken a brand that aims to feel calm. Conversely, an interface that is too polished can erase a distinctive tone if it applies conventions without questioning them.

    The design system lets the team address these points together. It can connect component copy to components, clarify where supporting information belongs and distinguish messages that confirm, alert or guide. The brand voice does not stop at editorial content. Visual design does not stop at the mockup.

    To go further, our article on brand platforms and brand systems sets out the starting point. Our article on atomic design in interfaces explains how to organise reusable elements. Our guide to web accessibility in a design system is a reminder that an interface must also remain usable by as many people as possible.

    In practice: SourceHub

    SourceHub is a shared responsible purchasing platform for Belgian non-profit organisations. The product was evolving every week when it launched. The challenge was to communicate from the start without locking its future into an overly rigid identity.

    Fauves created SourceHub’s name, visual identity and tone of voice, working directly with the project and development teams. Mockups, copy and micro-interactions were aligned with the project’s mission and technical constraints. Fauves remained involved during development.

    The result: an adaptable, modular identity and a clearer user experience. This case illustrates a simple idea: a useful system does not impose a final form on a product. It provides enough consistency to move forward while leaving room for the product to evolve.

    A system that supports sound decisions

    The value of a design system does not lie in the number of elements it contains. It lies in its ability to help the team make consistent decisions. It makes it possible to distinguish a rule, a variation and a genuine exception. It reduces unnecessary differences without replacing judgment.

    Starting with a brand system avoids confusing uniformity with consistency. The aim is not for every page to look the same. Each interaction should belong to the same product, carry the same intention and help people move forward with confidence.

    Need a design system that can support a product as it grows? Talk to us.