Blog

  • Is a compliant website really accessible?

    Is a compliant website really accessible?

    I still often see accessibility treated as a final step: an audit is commissioned, the reported issues are fixed, and the website is then considered accessible. That is a good start. But, for me, it is not enough proof.

    A website can meet a large proportion of the WCAG success criteria and still be frustrating, confusing or impossible to use for a disabled person. When I work on a website, I am interested in a more practical question: can someone find the information, understand what is expected of them and complete what they came to do without having to ask for help?

    That distinction guides how I approach accessible website design. Standards provide an essential framework. But they cannot replace observing how people actually use a service.

    Accessible website design: why I do not stop at WCAG compliance

    The WCAG have given teams, organisations and regulators a shared language. They provide specific reference points: text alternatives, keyboard navigation, contrast, heading structure, error messages, focus states and text resizing. Without that framework, everyone would decide for themselves what is acceptable.

    So I do not set them against user experience. On the contrary, they are the foundation I aim to build in from the design stage. But a standard checks conditions. It cannot, by itself, experience an entire user journey.

    An element may be technically keyboard accessible while the tab order remains illogical. Text may be enlarged without the page remaining genuinely readable or usable. A form may follow the markup rules and still leave someone without a clear answer when an error occurs. Compliance is a necessary minimum. It does not automatically guarantee usability.

    What tools and audits do not tell me

    Automated tools are useful. They help identify recurring defects quickly, monitor quality over time and prevent some obvious regressions from reaching production.

    But they read code and rules, not lived situations. They cannot tell whether a button label is ambiguous, a modal provides enough context, form errors are understandable, or someone can actually complete a task with the tools they normally use.

    That is why I do not limit the question to, “does the page pass?”. The useful question is: “can someone complete the action that matters without relying on outside help?”

    The ways of using a service that I try not to overlook

    When people discuss accessibility, they often first think of blind and partially sighted people. That is essential, but the subject is broader. An interface can also create barriers for deaf and hard-of-hearing people, people with reduced mobility, cognitive or learning difficulties, or people who use assistive technologies.

    I also try not to reduce the issue to permanent situations. Someone with an arm in a cast, a parent holding a child, or a person looking at their phone in noise or bright sunlight may encounter a context-related barrier. That does not minimise disability. It is a reminder that a service designed for different ways of using it is usually more robust for everyone.

    In practice, this means not depending on a single gesture, sense or speed of interaction. An important action should be possible with a keyboard as well as a pointer, with understandable labels, sufficient time and clear feedback about what has just happened.

    Movement should help, not demand attention

    I am not trying to remove every animation. A transition can explain that a panel has opened or that a form has been submitted. But continuous, automatic or decorative movement can distract from the task and make concentration more difficult for some people.

    The prefers-reduced-motion system preference makes it possible to offer a calmer version to someone who has chosen to reduce animations on their device. For me, the right question is simple: does this movement help someone understand, or does it demand attention without providing useful information?

    I test a journey, not just a page

    For an organisation, the useful question is rarely, “is our website accessible?”. I prefer to ask: can someone actually complete the tasks that matter? Find important information, compare an offer, contact the organisation, fill in and correct a form, book, pay or follow up a request.

    This approach exposes what an isolated page can easily hide: implicit instructions, poorly announced changes of context, vague buttons, errors that are hard to correct, or steps that depend on visual information alone.

    Testing with disabled people can reveal these barriers in very concrete ways. It does not replace a serious WCAG assessment, just as a single person’s feedback cannot represent every way of using a service. The W3C recommends combining the involvement of people concerned with conformance evaluation. That combination seems the most honest approach to me.

    Why I prefer to discuss cost at the start of a project

    Taking accessibility seriously takes time, skills and sometimes a dedicated budget. Building robust components, reviewing content, testing with a keyboard, fixing forms and checking critical journeys are part of the work. Bringing in an independent body for an audit, or organising tests with disabled people, also adds a cost.

    I prefer to say that from the outset rather than presenting accessibility as an easy option to add at the end. An independent audit, such as those offered by AnySurfer, is a paid expert assessment service. Usability testing has a separate budget: scenarios must be prepared, participants recruited and paid, sessions facilitated, findings analysed and then addressed.

    That does not mean every website must immediately fund a label or a full user study. The appropriate level of effort depends on the service, its audience, the risks and the applicable obligations. But the choice should be deliberate. Leaving the issue until the end often means discovering structural problems when they are more expensive to fix.

    In Belgium, digital accessibility is already a legal obligation for public-sector services. Since 28 June 2025, some consumer-facing private services, including e-commerce, have also been covered by new European requirements. These obligations do not simply depend on the size of a business: they depend on the service offered and the intended audience. The Federal Public Service Economy guidance explains, among other things, the framework that applies to e-commerce in Belgium.

    What I take from WCAG and AnySurfer

    WCAG 2.2 remains a very useful quality baseline today. The work under way on WCAG 3 also points to an interesting shift: more attention to users’ functional needs and the outcomes they need to achieve, rather than only a list of technical checks.

    I also value AnySurfer’s approach in Belgium because it connects the skills of the teams, the quality of the delivered product and the client’s ability to maintain that quality over time. An interface does not stay accessible by magic once it is live. Content changes, new features appear and teams change.

    In 2023, I completed AnySurfer’s Web accessibility training for developers. Not to present myself as an all-knowing expert, but to better understand my responsibilities as a developer and keep improving my practice.

    How I approach accessibility at Fauves

    I do not see accessibility as a perfect state that can be reached once and for all. It is ongoing attention: checking, correcting, learning and doing better at every stage.

    • Define the critical journeys. Identify the tasks that must not leave anyone behind.
    • Design with accessible principles. Plan robust components, understandable content, visible states and consistent navigation.
    • Check regularly. Combine manual review, automated tests and checks against the relevant WCAG criteria.
    • Test when the project warrants it. Observe concrete tasks with people concerned and incorporate their feedback early enough to make changes.
    • Maintain quality. Train the people who publish content, document decisions and recheck changes to the website.

    At Fauves, I want to keep making this approach more concrete, more verifiable and more sustainable, including by starting the steps needed to obtain an AnySurfer label.

    Key takeaway

    A compliant website is better than a non-compliant one. But a genuinely accessible website is not judged by its code compliance alone. It is judged by whether people, in all their diversity, can understand, navigate and take action without encountering unnecessary barriers.

    Standards point the way. The people concerned tell us whether we have got there.

  • 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.

  • How to make a brand identity work across channels, teams and audiences

    How to make a brand identity work across channels, teams and audiences

    A brand identity is not sustained by a well-applied logo alone. It holds when everyone knows what to protect, what they can adapt and when to ask for input. Without that, teams start with good intentions, but messages, visuals and experiences eventually stop working together.

    This is not about controlling every publication. It is about helping teams make decisions faster, whether for a website, presentation, campaign, offer, event or customer response. A useful brand identity provides a shared direction while leaving room for the situation at hand.

    Moving brand identity from a document to a system

    A set of brand guidelines alone is not enough. It often tells teams what to use. It is less helpful when they need to choose between options or handle a new situation. To last, a brand identity must guide day-to-day work.

    It connects the brand platform, messaging, tone of voice, visual rules and production tools. If this foundation lacks clarity, start by distinguishing the brand platform from what makes it possible to activate every day. Our article on the brand platform and brand system explains how they work together.

    In practical terms, a team should be able to answer five questions quickly:

    • What central idea must remain recognisable?
    • Which audience are we addressing here, and what do they expect from us?
    • Which message takes priority in this context?
    • Which elements are non-negotiable?
    • Who decides when a case falls outside the framework?

    These answers prevent two pitfalls: repeating the same message everywhere or reinventing the brand for every channel.

    Define decision-making rules, not just visual rules

    Visual rules are necessary. But if the message is unclear, they come too late. Give teams a simple order: first the promise they need to convey, then the audience, the level of proof, the format and finally the visual form.

    A short post can retain the intent, tone and an accurate message. A sales presentation needs more proof. Being consistent does not mean doing everything in the same way.

    Document the limits too. Rules in the form of “if…, then…” are more useful than a list of broad principles. For a new audience, validate the angle before producing. For an existing offer, start with the planned template.

    Give teams the right tools to act independently

    Autonomy is not about sending a PDF and hoping it will be read. It depends on resources that are easy to find, understand and use when work begins.

    Prepare an operational kit in a shared space:

    • a one-page summary of the brand fundamentals;
    • a message library organised by audience, topic and objective;
    • annotated examples of successful content;
    • templates for presentations, documents, social media, newsletters and briefs;
    • a bank of approved images, videos, icons and components;
    • a frequently asked questions page and a contact for complex cases.

    Templates should guide without restricting. A good template shows what stays consistent, what can change and why. It saves time without opening the door to arbitrary adaptations. The logic is the same as for a design system: reusable elements, assembly rules and accessible documentation. See how to connect a brand system and design system.

    Put lightweight, visible governance in place

    A brand becomes diluted when no one knows who makes the final call. On the other hand, having every detail approved in one place slows everyone down. Useful governance distributes decisions.

    Define what teams can publish independently, what requires a review and what must be decided by a brand lead. Everyday content can follow pre-approved templates. Launches, changes in positioning, sensitive communications or new communication territories require a more structured review.

    Also clarify timelines and the request format. A short brief with the objective, audience, message, channel, deadline and a reference example already makes approvals much easier. The brand lead is not there only to say yes or no. They explain the decision so the team can act more effectively next time.

    Create feedback loops that improve the system

    Not every deviation is a mistake. Some show that a rule is missing, a template is too rigid or a need was not anticipated. Schedule a regular check-in that is short and practical. Review a few recent pieces of content: those that translated the brand well, those that needed too many rounds of revisions and those that need better documentation.

    Then turn these lessons into visible updates: an example in the guidelines, a new answer in the FAQ, an updated template, a reworded rule. Without this maintenance, teams find their own solutions and the system stops being their reference point.

    In practice: The Belgian Red Cross

    The Belgian Red Cross is a humanitarian organisation with diverse activities, audiences, messages and teams. Fauves worked through workshops across four areas: the meta-brand, donations, blood donation and youth engagement.

    The work resulted in editorial and visual guidelines. They define the tone, emotions, audiences and appropriate messages. For each area, they set out a narrative and key messages, then document the visual logic, do’s and don’ts, checklists, photo and video guidance, and templates. Discover the Belgian Red Cross project.

    Checklist before rolling out a brand identity

    • Can teams express the brand’s central idea in their own words?
    • Are messages adapted by audience and situation without contradicting the promise?
    • Are the non-negotiable elements and areas for adaptation explicit?
    • Are approved templates and examples available for the most-used channels?
    • Does everyone know when to act independently and when to request approval?
    • Is there a feedback rhythm that makes it possible to improve the tools and rules?

    Make the brand work in real life

    A brand identity becomes strong when it helps teams make better decisions, not when it adds control. Start with the situations where inconsistencies recur most often. Equip the people who create the most content. Then evolve the tools based on their feedback.

    Want to turn static guidelines into a working framework everyone can use? Let’s talk about your brand system.

  • Brand platform and brand system: what is the difference and how do you make them work?

    Brand platform and brand system: what is the difference and how do you make them work?

    A brand platform clarifies what a brand stands for, who it serves and the place it wants to occupy. The brand system turns that direction into rules, tools and habits for teams. The platform sets the direction. The system helps apply it in content, campaigns and day-to-day interactions.

    The brand platform: a shared direction

    The brand platform provides a strategic framework. It puts words to what matters: the organisation’s role, its audiences, its positioning, its promise and the beliefs that guide its communications. Above all, it helps people make choices.

    It is not only for writing a corporate presentation. It helps answer practical questions: does a new service, campaign or partnership strengthen the role the brand wants to make clear? Does it respond to the needs of the intended audience?

    A useful brand platform does not try to cover everything. It sets a guiding line that teams, partners and suppliers can follow. Without this foundation, messaging quickly becomes fragmented.

    Brand identity, brand system and design system: different levels

    Brand identity is what makes a brand recognisable. It includes the tone of voice, language, logo, colours, typefaces, imagery and composition. It gives strategy a tangible form. On its own, it does not say how to act in every situation.

    The brand system organises this expression over time. It connects strategic principles to practical work: messages, tone of voice, visual choices, templates, adaptation rules and approval. It helps teams stay on course when formats, audiences or stakeholders change.

    The design system is more focused. It mainly concerns the design and production of digital interfaces: components, states, behaviours, spacing, accessibility rules and technical documentation. It can be part of a brand system, but it does not replace one. A brand can have an excellent design system for its website or app while still lacking guidance for its campaigns, videos, messages or partner materials.

    Element Key question What it produces Example use
    Brand platform What direction do we share? Positioning, promise, role, audiences, principles Choosing the angle for a new campaign
    Brand identity How is the brand recognised? Voice, logo, colours, typefaces, visual world Designing a poster or presentation
    Brand system How do we stay consistent in different situations? Rules, examples, templates, tools, governance Adapting a message for an audience or channel
    Design system How do we design consistent digital interfaces? Documented interface components and rules Building a web page or digital journey

    Why a brand platform is not enough on its own

    A strategy takes shape in day-to-day work. A team may need to adapt a message quickly. A partner or supplier needs clear instructions. In these situations, a general principle is not always enough.

    The brand system turns strategic decisions into easy-to-use resources. It can show which messages to prioritise for each audience, the right level of emotion, image choices, what to avoid, the formats available or the approval steps. This limits unnecessary interpretation. Teams can also make decisions faster, without starting from scratch for every request.

    The system should not become a manual that no one consults. Documentation organised around real situations is more useful than a collection of rules. The tools need to meet concrete needs: writing, briefing, designing, adapting, getting approval and handing work over.

    In practice: a framework for the Belgian Red Cross

    The Belgian Red Cross is a humanitarian organisation with varied actions, audiences, messages and teams. In this context, the challenge was not to apply a single message everywhere. It was to create a framework that made it possible to activate the brand consistently while taking different realities into account.

    With the Belgian Red Cross, Fauves identified four mobilisation areas: the meta-brand, donations, blood donation and youth mobilisation. Workshops and co-creation work made it possible to build an editorial and visual brand charter with practical guidance.

    This charter covered tone of voice, emotions, audiences and message adaptation. For each area, it also set out a narrative and key messages. Visual choices were documented with do’s and don’ts, checklists, photo and video recommendations, and templates. The intention was to help internal teams, external partners and suppliers activate the brand consistently.

    This case shows what gives a brand system its value: it does not stop at defining an identity. It provides practical guidance when one organisation needs to address several audiences, mobilise different teams and produce content in multiple contexts.

    How to make it work over time

    Launching a brand platform or brand system is the beginning of adoption. The people who use it need to find the right resource quickly. Documentation organised by use case is more helpful than a file that no one opens.

    Then establish simple routines: include the principles in the brief, use the available templates, identify the moments when approval is needed and note recurring questions. These questions often reveal a rule to clarify, an example to add or a tool to simplify. To explore adoption further, also read how to make a brand identity work.

    Finally, evolve the system when the organisation, its offers or its channels change. This is not about reinventing the brand for every medium. It is about keeping a direction clear enough to guide decisions and flexible enough for new situations. If your challenge is more specifically about interfaces, also discover the difference between a brand system and a design system.

    Checklist before rolling out your brand system

    • Does the brand platform provide concrete criteria for making choices?
    • Does the brand identity clearly translate that direction into language and visuals?
    • Do teams have rules suited to their working situations?
    • Do partners and suppliers know which tools to use?
    • Are examples, templates and checklists easy to find and understand?
    • Is there a way to update the documentation when a need arises?

    Set a direction, then give people the means to apply it

    The brand platform aligns intentions. Brand identity makes them recognisable. The brand system gives teams the means to apply them. Clearly distinguished and closely connected, these three levels help an organisation speak with a more consistent voice without erasing the diversity of its audiences and formats.

    Do you need to clarify your brand platform or turn an existing identity into tools people can actually use? Contact Fauves to discuss it.

  • What makes a brand credible over time

    What makes a brand credible over time

    A brand does not become credible because it lists attractive values or adopts a confident tone. It becomes credible when what it promises, shows and asks people to experience stays aligned over time.

    Consistency does not mean repeating the same words everywhere. It means that the same intention can be felt in decisions, messages, tools and interactions. That continuity is what gives people reason to trust an organisation.

    A promise that helps people choose

    A brand promise is not a decorative slogan. It should express something real for the people an organisation serves and help the organisation make choices. If a promise changes nothing about how an offer is designed, a need is answered or a project is prioritised, it remains abstract.

    A useful promise creates a standard. It asks teams whether a decision makes their purpose clearer and whether it genuinely helps the people they are addressing. When the organisation has moved on and those reference points no longer fit, the signs that it may be time to rebrand are worth examining.

    Simple messages, without flattening the truth

    Complex organisations often try to explain everything. Arguments, pages and caveats multiply until the value becomes difficult to remember. A clear message does not hide complexity. It gives people a way in before opening up the detail they need.

    Clarity starts with shared language. Teams should be able to describe the organisation without inventing a different version each time. That takes sound messages, concrete proof and words that match what the organisation actually does.

    Evidence matters more than posture

    A brand gains weight when it can show how it acts. A method, a project, a difficult decision, a way of working or a tangible improvement will usually say more than a long statement of intent.

    Evidence is not limited to figures or testimonials. It may be a more transparent process, better-designed tools, a more attentive welcome or a simpler digital experience. It makes the story believable because people can see it in practice.

    An identity people can recognise

    Visual identity has an important role in credibility. It helps people recognise the brand across different channels and avoids the sense that the organisation changes face every time it speaks. Yet it needs to adapt to different contexts without becoming rigid.

    A well-considered identity does more than produce attractive visuals. It helps the people who write, present, design or approve work. As visual identity becomes easier to use, it gives teams useful reference points without making every output identical.

    Experience either supports or undermines the brand

    A promise can be clear and an identity distinctive. If the experience that follows is confusing, slow or impersonal, trust wears away. The website, documents, conversations, contact journeys and internal tools all shape the brand as people encounter it.

    A credible brand can evolve with its organisation and its audiences. What should remain steady is not every phrase or visual detail, but the logic that helps people decide what to keep, adapt or leave behind.

  • Choosing your branding agency: The 5 boxes it needs to tick

    Choosing your branding agency: The 5 boxes it needs to tick

    The success of your branding or rebranding project starts with the agency you choose. It is a crucial decision that can propel your brand forward… or sink it.

    Choose poorly, and you risk a resounding failure. Before committing, make sure the agency you select ticks these 5 essential boxes.

    They are the foundations of a winning collaboration that will lead your brand toward success.

    We explain more in this article.

    Listening and process clarity: the foundations of a transparent exchange

    Above all, a branding agency must be able to listen to you, not just hear your needs, but truly understand them.

    This requires active listening and constant attention to your expectations. An agency that gives you this level of attention and explains its process clearly and in detail from the start is an agency you can count on.

    If the collaboration process is not clear and communication is not fluid, misunderstandings can quickly appear and slow down the project.

    Before signing, make sure the agency takes the time to listen to you and that its process is structured and transparent.

    The personality fit: essential chemistry

    As in any relationship, harmony between you and your agency is essential.

    You will spend time collaborating, exchanging ideas, and confronting visions.

    If the conversation feels forced or artificial, that is a bad sign.

    Before committing, ask yourself whether you feel comfortable with the team and whether the contact feels fluid and natural.

    This connection is the key to a successful collaboration.

    You do not want simple providers, but real partners who understand you and share your vision.

    The culture & values fit: are you on the same wavelength?

    Your agency’s values must be fully aligned with those of your company.

    If you are looking for an agency that places honesty, transparency, and commitment at the heart of its approach, make sure it truly practices them.

    A good agency will be ready to answer all your questions, even the most difficult ones, and will encourage you to ask them.

    If the agency seems to avoid certain topics or hide information, that is a warning sign.

    Make sure the agency’s values and your own are aligned before making a final decision.

    An agency that challenges you

    A branding partner that approves all your ideas without question will not help your brand evolve.

    A true branding agency must know how to challenge you, push you to rethink certain ideas, and take you out of your comfort zone.

    Sometimes, it will have to confront you with difficult truths, but that questioning is what will move your brand forward.

    If you do not feel that ability to challenge you and offer new perspectives, it may be time to look for another team.

    Process and project management: the framework needed to move forward

    Good project management is essential for a smooth process. Before choosing your agency, ask to see how it manages its projects. A serious agency should have a clear schedule, with management tools such as a Kanban board or backward planning, and be able to keep you informed of progress at every stage. If the agency has no methodology in place to manage the project smoothly, this can lead to delays and confusion. You need to be able to track progress, receive regular updates, and adjust things when necessary.

    An agency that supports you beyond simply working for you.

    Choosing the right branding agency is a decisive choice for the future of your brand.

    If you make the wrong choice, you risk wasting time and money and ending up with disappointing results.

    That is why you need to make sure the agency you select meets these fundamental criteria before you commit.

    It must be able to listen to you, share your values, challenge you, and support you with a clear and effective process.

    Do not underestimate the importance of this choice.

    By following these steps, you maximize your chances of making your branding or rebranding project a success.

  • Branding: what it really changes for an organisation

    Branding: what it really changes for an organisation

    Branding is often reduced to visual identity, a logo or a campaign. Those things matter, but they do not explain why some brands feel clear and credible. Branding shapes how an organisation understands itself, presents itself and becomes recognisable over time.

    It is not about making a confused reality look more attractive. It is about making that reality easier to grasp. A useful brand helps people explain what they do, who they are here for and why their work deserves attention.

    Branding gives decisions a shared direction

    Organisations make communication decisions all the time: launching an offer, writing a presentation, recruiting, answering a tender, building a website or planning a campaign. Without a common direction, each decision can make sense on its own while the overall picture becomes muddled.

    Branding provides that direction. It clarifies the organisation’s role, the people it wants to serve, the place it wants to hold and the promise it can genuinely keep. It does not replace business strategy, but it makes that strategy easier to understand and share.

    Identity is not just the logo

    A logo, colours, typefaces, imagery and layouts make up the most visible part of a brand. They help people recognise an organisation and give its communications a sense of continuity. But visual identity cannot make up for a vague position or messages that could belong to anyone.

    An identity works when it expresses a clear intention. It should hold together across a website, presentation, signage, post, proposal or internal document without losing its character. That is what makes it useful rather than merely decorative. For a closer look at the practical side, see what a visual identity changes for an organisation.

    A story gives facts their meaning

    A brand story is not a polished tale added on top of an organisation. It connects its work, convictions, history and choices in language people can follow. It helps explain not only what the organisation offers, but also what drives it and why it is well placed to do the work.

    That story then carries through the website, talks, offers, presentations and commercial conversations. It gives messages continuity without making them sound scripted. A credible brand story keeps each channel from having to begin the explanation from scratch.

    The experience confirms the brand

    A brand does not live only in a brand book. It shows up in a reply to a client, the clarity of a proposal, the ease of a website journey and the way someone explains the organisation outside the office. When promises, messages and experience contradict one another, credibility falls quickly.

    That makes branding a matter of coherence. It connects words, images, tools and behaviours. This does not mean that everything should look the same. It means the choices should move in the same direction and remain recognisable in different situations.

    Keeping the brand useful over time

    The challenge is not only to define a brand. It is to help it hold up as teams change, projects multiply and formats evolve. That calls for practical reference points, examples, tools and decision rules that people can actually use.

    A branding project is worth revisiting when the organisation has changed faster than its brand: perhaps the offer has moved on, audiences have shifted or the identity has become hard to use. The point is not always to start again. It is to see clearly what still fits, what is missing and what is causing confusion.

  • Mobil Studio becomes FAUVES

    2024 was a wild year. A year that marked a decisive turning point for Mobil Studio. In 12 months, we seized opportunities, explored new perspectives, and laid the foundations for our shared adventure.

    And in 2025, Mobil Studio became FAUVES.

    Like fauves: Mobil Studio asserts its identity

    This new name did not appear by chance. Inspired by Fauvism, the artistic movement that dared to break the rules by celebrating color, boldness, and intensity, FAUVES expresses our deeper ambition: to create without limits, bring powerful projects to life, and reveal the authenticity of every brand.

    Choosing FAUVES means claiming a raw force, that of wild creatures: their visceral instinct, overflowing energy, and ability to take root powerfully in their environment.

    From Mobil Studio to FAUVES Agency: a new era

    2025 is not only the year of a new name. It is the year of a major transition. We are evolving from a Studio into an Agency.

    Our positioning is becoming sharper, our identity is unfolding, and we are consolidating our team to serve your projects better, with even more creativity and boldness.

    Mobil Studio becomes FAUVES: new name, same mission

    Our name may be changing, but our mission remains the same. More than ever, we want to create brands that do not simply exist, but embody a collective vision, bring people together, inspire, and unite.

    We are still driven by the same desire: to make you shine, reveal your potential, and support you on the road to success.

    To learn more about our branding agency based in Brussels, visit our About page.

    Ready to unleash your brand instinct? We’re waiting for you.

    The Fauves Morgan, Brahim & Laura