Voaize
Accessibility
Voaize is designed so people can scan a product code and get an answer - whether they speak or type.
Last updated August 31, 2026
Our commitment
We want marketing pages and shopper product pages to be usable with keyboards, assistive technologies, and reduced motion. Accessibility is part of the product, not a separate mode. Store tools for invited staff are included, though they may lag the public pages.
Standard we aim for
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA on public pages. That is a target, not a certification. If something fails, tell us. We treat a concrete barrier as work to fix.
What we design for
- Keyboard access to navigation, forms, and common controls
- Text alternatives on meaningful images
- Visible focus and sufficient contrast
- Respect for reduced-motion preferences
- Typed conversation as a full alternative to voice
- Pages that work at common zoom levels, including on a phone in the aisle
Known limits
Voice requires permission from the device. Some people will prefer to type; that path is intentional. Generated answers can be long, and we continue to improve how they read with assistive technology. Store tools for staff (uploads, layout, and code management) are less polished than the public pages.
Report a barrier
Email hello@voaize.com with the page, what you were trying to do, and the browser or assistive technology you use. Please include “Accessibility” in the subject. We read those notes and will reply.