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.
