Legal
Accessibility Statement
Last updated 5 November 2026 6 min read
Marabi Made It is committed to making marabimadeit.co.ke usable by as many people as possible, including people with visual, hearing, motor or cognitive disabilities and people using assistive technology. We build accessible websites for our clients, so we hold ourselves to the same standard. This statement explains our target, what we have done, where we still fall short, and how to ask for help.
At a glance
- We are working to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.
- The site works with a keyboard, has a skip link, labels its forms, and respects reduced-motion settings.
- The 3D cards and the Marabi assistant have non-motion and keyboard alternatives.
- A few things still fall short, and we list them honestly below.
- Tell us if something is hard to use, and we will help and fix it.
This summary is for convenience. The full text below is what applies.
1.Our commitment
- 1.1We believe the web should be usable by everyone. Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and we treat this as an ongoing process rather than a box ticked once.
- 1.2This commitment is consistent with the Constitution of Kenya, which recognises the rights of persons with disabilities, and with the Persons with Disabilities Act, 2003, which promotes access to information and services.
2.Scope
- 2.1This statement covers the Site at marabimadeit.co.ke, including its pages, forms, the 3D ability cards, the services index, the contact buttons and the Marabi assistant.
- 2.2It does not cover websites and systems we build for clients, which are governed by their own requirements, or third-party sites to which we link.
3.Terms used
- WCAG 2.2 AA
- the international technical standard for web accessibility published by the World Wide Web Consortium (W3C), level AA, which is the widely accepted benchmark.
- Assistive technology
- software or hardware that helps people use a computer, such as screen readers, magnifiers, voice control and switch devices.
- Reduced motion
- an operating-system or browser setting that asks websites to limit animation and movement.
4.What we have done
- 4.1Structure and navigation: we use semantic HTML, a logical heading order, descriptive link text, landmarks, and a skip-to-content link that appears when you press Tab.
- 4.2Keyboard use: all interactive elements, including menus, the services index, the contact form, dialogs and the card controls, can be reached and operated with the keyboard, with a visible focus indicator. Dialogs close with the Escape key and return you to the page.
- 4.3Colour and text: text and interface elements are designed to meet the WCAG minimum contrast ratios in the dark theme, and information is not conveyed by colour alone. Text can be resized and the layout reflows at narrow widths and on small screens without loss of content.
- 4.4Forms: each field has a label or accessible name, required fields are marked, and the form works with the keyboard and with screen readers.
- 4.5Motion: we honour your reduced-motion setting. When it is on, the loading sequence is skipped, the logo marquee stops, the typewriter text appears at once, and smooth scrolling and decorative animation are switched off.
- 4.6Images and media: informative images have text alternatives, and decorative images are hidden from assistive technology.
5.Interactive features
- 5.13D ability cards: the cards are drawn in a graphics canvas. They have a text description giving the person's name and role, a keyboard-operable Flip button as an alternative to dragging or tapping, and a fallback image where the browser cannot display 3D graphics. They tilt with the pointer, but movement is switched off if you prefer reduced motion.
- 5.2Services index: each service opens and closes on hover, on focus and on tap or click, and exposes its open or closed state to assistive technology. Each service also has a plain link to its own page, so nothing depends on the open or closed state.
- 5.3Marabi assistant: the assistant is built to be operable by keyboard, to announce new messages to screen readers, to avoid trapping focus, and to be dismissed at any time. It limits its animation if you prefer reduced motion.
- 5.4Scroll-driven sections: the introductions of the founders appear one after another as you scroll. While an introduction is on screen, its name, role and tagline are available as text to assistive technology.
6.Known limitations
| Area | Limitation | What you can do |
|---|---|---|
| 3D ability cards | The skill bars on the card faces are part of the graphic and are not exposed one by one to screen readers. The card's description gives the person's name and role. | Use the person's introduction text and the About page, or ask us for the card's details in text |
| Scroll-driven introductions | The pinned, scroll-driven introductions can feel long with some assistive technologies and at high zoom levels. | Use the skip link, the headings or the links in the navigation to move on, or ask us for the content as plain text |
| Third-party content | Linked services such as WhatsApp and Instagram have their own accessibility, which we do not control. | Contact us by email instead |
7.Compatibility
- 7.1The Site is designed to work with the current versions of the Chrome, Edge, Firefox and Safari browsers on desktop and mobile, and with common assistive technologies including screen readers such as NVDA, JAWS, VoiceOver and TalkBack, and with browser zoom and operating-system text scaling.
- 7.2It relies on the HTML, CSS, JavaScript and WAI-ARIA standards. The 3D cards additionally use WebGL, and the fallback described above is used where it is not available.
8.How we check
- 8.1We check accessibility as we build: automated checks during development, manual keyboard testing, checks with browser zoom and reduced-motion settings, and manual review of headings, labels and focus order. We re-check when we make significant changes.
- 8.2Automated tools find only a part of the issues, so we do not claim full conformance on that basis alone. We publish the limitations we know about in this statement.
9.Accessibility in the work we build for clients
- 9.1We design client websites and systems to meet WCAG 2.2 AA unless a Statement of Work says otherwise, and check key journeys, such as navigation, forms and checkout, with a keyboard and a screen reader before launch.
- 9.2A client that adds content to its site after launch is responsible for keeping that content accessible, for example by adding text alternatives to images. We can train the Client's team on this at handover.
10.Tell us about a problem
- 10.1If you have difficulty using any part of the Site, or need information in another format, please contact us at marabimadeit@gmail.com with the subject "Accessibility". Tell us the page, what you were trying to do, the problem you met, and the browser and assistive technology you use, if you are happy to.
- 10.2We will acknowledge your message within three Business Days, and aim to give you the information or help you need within 10 Business Days. We will tell you what we plan to do to fix the underlying issue and, where we can, when.
- 10.3You may ask for any content from the Site in an alternative format, such as plain text, large print or a different structure, and we will provide it free of charge where reasonably practicable.
11.If you are not satisfied
- 11.1If you are not happy with our response, please tell us and we will review it, with the founder, within seven Business Days.
- 11.2You may also seek advice or assistance from the National Council for Persons with Disabilities (NCPWD) in Kenya, which promotes and protects the rights of persons with disabilities.
12.Review and dates
- 12.1We review this statement at least once a year, and whenever we make significant changes to the Site. This statement was last updated on 5 November 2026.