WCAG 2.2 Level AA — for the Kubo website, the dashboard and the widget your customers use.
Accessibility statement
Kubo, for everyone.
The standard we work to, what we’ve built so far, what we still need to fix, and how to reach us if something gets in your way.
Kubo follows your device’s reduced-motion setting everywhere, including his own animations.
Partially conformant, based on our own review — not a certification. Known limitations are listed below.
Tell us about any barrier at hello@swiidtech.com.
The summary is a guide only. The full text below is what applies.
Our commitment
Swiid Technologies wants everyone to be able to use Kubo — the businesses that set him up and, just as importantly, the customers who talk to him on those businesses’ websites. Because Kubo is installed on other people’s sites, an accessibility problem in Kubo becomes a problem for every business that uses him, so we treat accessibility as part of the product, not an add-on.
The standard we follow
We work toward the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium. These guidelines explain how to make content more accessible for people with disabilities, including people who are blind or have low vision, are deaf or hard of hearing, or have motor, cognitive or vestibular disabilities.
Conformance status
Kubo is partially conformant with WCAG 2.2 Level AA: some parts may not yet fully meet the standard. This assessment comes from our own review during development, not an independent audit or certification. An independent accessibility review is planned before public launch.
What we’ve built
- Keyboard access. Every control works with a keyboard, with a visible focus ring and a “Skip to content” link on every page.
- Menus that behave. The mobile menu moves focus into its links, closes with Escape and returns focus to the button that opened it.
- Reduced motion. If your device asks for reduced motion, page transitions, entrance animations and Kubo’s own character animations stop; content appears immediately.
- A still background. The night-sky background doesn’t move, flash or scroll-animate.
- Text alternatives. Kubo’s character has a text description, and decorative graphics are hidden from screen readers.
- Live regions. New chat replies and guided-workflow steps are announced to screen readers.
- Readable contrast. Body and label text is designed to meet AA contrast on our backgrounds, and status is never shown by color alone.
- Plain labels. Form fields have visible labels, and errors are announced and explained in words.
- The widget. Customers can open, minimize and dismiss Kubo with the keyboard, close him with Escape, skip feedback, and clear their saved conversation.
- Responsive layouts. Pages work down to 320 pixels wide and when zoomed, without horizontal scrolling.
Known limitations
These are the issues we know about, and what we’re doing about them:
- Animated product story. The homepage’s scroll story changes its content as you scroll. Its scenes are illustrative and the same information is available in the feature list and documentation. We are adding step controls so it can be followed without scrolling.
- Typing effects. Some demo replies appear progressively. Screen readers receive the complete reply; with reduced motion on, it appears at once.
- Character poses. Kubo’s animated poses are pictures; their meaning (for example “thinking”) is also shown in text nearby.
- Languages. Kubo currently answers in English only. Nigerian Pidgin, Yoruba, Igbo and Hausa are planned once quality has been validated with proficient speakers.
- Voice. Kubo does not yet offer speech input or output.
- Businesses’ own content. Knowledge, product descriptions and greetings are written by each business. We encourage clear, plain language, but we can’t control that content.
Compatibility
Kubo is designed for current versions of Chrome, Edge, Firefox and Safari on desktop and mobile, and for screen readers including NVDA, JAWS and VoiceOver. Older browsers may display Kubo without some visual effects; page transitions simply don’t animate where they aren’t supported.
How we assessed Kubo
We reviewed Kubo with keyboard-only navigation, browser accessibility tooling, automated browser tests covering keyboard menus, narrow 320–375 pixel layouts and reduced motion, and manual visual review of every page. This statement was last reviewed on October 21, 2026.
Feedback and help
If you find a barrier on the Kubo website, in the dashboard, or in Kubo on a business’s website, please tell us at hello@swiidtech.com with “Accessibility” in the subject. Include the page or business, what you were trying to do, and the device, browser and assistive technology you use if you can.
We aim to reply within 5 business days, and we’re happy to provide information in another format or help you complete a task another way.
If you are not satisfied
If you are not happy with our response, please reply and ask for it to be reviewed by someone else on the team. You may also have the right to contact an enforcement or disability rights body where you live. See also our privacy policy and terms of service.