ACCESS · CLARITY · PARTICIPATION
A living experience should make room for different ways of seeing, navigating, understanding and interacting.
OUR COMMITMENT
MICROBA is building a connected digital ecosystem intended to be understandable, operable and usable by a broad range of people. Accessibility is part of how we design, build, review and improve that experience.
Because MICROBA continues to evolve, accessibility work is ongoing. New pages, products, services, third-party integrations and content can introduce new barriers. We aim to identify those barriers, reduce them and learn from people who encounter them.
Our goal is practical access: people should be able to understand where they are, what an action does, and how to continue their journey using the technology that works for them.
01 · THE FOUR PRINCIPLES
Our accessibility direction is organised around the four established WCAG principles: perceivable, operable, understandable and robust.
Information should be available in ways people can perceive.
We design for readable text, meaningful structure, sufficient visual distinction, useful alternative text and content that does not depend on colour alone.
The experience should work beyond a mouse or touchscreen.
We design navigation, controls and interactions so they can be reached and understood with a keyboard, visible focus and predictable interaction patterns.
Language, structure and actions should be clear.
We aim for consistent navigation, descriptive labels, clear instructions, understandable errors and content that explains what will happen before an important action.
The experience should work with different technologies.
We use semantic HTML and established web patterns so browsers, assistive technologies and future interfaces can interpret the experience more reliably.
02 · WHAT WE DESIGN FOR
Accessibility is not one feature. It is the result of many small decisions across structure, content, interaction, visual design and engineering.
Interactive controls should be reachable by keyboard, follow a sensible order, and show a visible focus state.
Pages should use meaningful headings, landmarks, labels and skip navigation so people can move through content efficiently.
Typography, spacing and contrast should support reading, zoom and reflow without making content depend on decorative presentation.
Meaningful images should have useful alternatives. Decorative imagery should stay out of the accessibility tree when it adds no information.
Forms should have labels, instructions and understandable feedback. Authentication should avoid unnecessary cognitive barriers where practical.
We respect reduced-motion preferences and aim to avoid interaction patterns that require precise movement, rapid timing or a specific device.
03 · ASSISTIVE TECHNOLOGY
We aim to use semantic HTML, native controls and predictable patterns before introducing custom interaction. This gives browsers and assistive technologies a stronger foundation to interpret the interface.
Technology combinations vary. A page that works well with one browser or assistive technology may behave differently with another, so real-world feedback remains important.
04 · CURRENT LIMITATIONS
We do not assume that every part of a growing ecosystem is barrier-free. Where we find limitations, the aim is to understand their impact and improve them responsibly.
Embedded tools, payment services, media, authentication providers or other external systems may have accessibility characteristics outside MICROBA's direct control.
Older material, user-contributed content and imported resources may not always meet the same accessibility quality as newly designed MICROBA experiences.
New features can create new barriers. Accessibility therefore needs review during discovery, implementation, testing and later refinement—not only at launch.
USING MICROBA
05 · TELL US WHERE ACCESS BREAKS
If you encounter an accessibility problem on MICROBA, contact us and tell us what you were trying to do. Useful details include the page URL, the problem you encountered, your browser or device, and any assistive technology you were using.
Accessibility is not a separate destination.
