Accessibility
Ubaby believes accessibility is a right, not a feature. This page documents all accessibility practices we implement, the tools we use for verification, and how you can customize your browsing experience.
We follow WCAG 2.1 level AA guidelines (Web Content Accessibility Guidelines), the Brazilian Inclusion Law (LBI — Law 13.146/2015, Art. 3º, III e IV) and accessible design practices. All new components and pages are verified against these standards before launch.
All components maintain a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text, per WCAG 2.1 AA. We use tools like axe-core and Lighthouse for periodic auditing.
All interactive elements are accessible via Tab, Enter and Escape. We provide skip links ("Skip to content") at the top of every page, visible focus (focus-visible) on all components, and complete navigation without a mouse.
All components use appropriate ARIA attributes (aria-label, aria-describedby, aria-expanded, aria-modal, role, aria-pressed, aria-current, aria-invalid, aria-live). Decorative images use aria-hidden; informative images have descriptive alt text.
All fields have associated labels, error messages connected via aria-describedby, required field indicators and accessible error states (aria-invalid).
Modals have focus trap (confined within the modal), Escape to close, aria-modal="true" and role="dialog". Focus returns automatically to the triggering element when the modal closes.
We respect the system `prefers-reduced-motion` preference: animations, transitions and camera movements are disabled when requested. Use the preferences panel to enable this option manually.
Minimum 16px body sizes, rem units in all layouts. The layout supports text zoom up to 200% without breaking page structure.
All images have descriptive alternative texts (or aria-hidden when purely decorative). Videos have captions and accessible poster images.
Customize font size, contrast and reduced motion in our accessibility panel. Your preferences are saved in cookie and localStorage, applied globally across all pages.
Spot audits with Lighthouse and axe DevTools, manual testing with NVDA and VoiceOver, and an automated axe-core scan of our public pages — which runs in CI alongside the end-to-end tests, every night.
Found an accessibility issue? Send your feedback to [email protected] — we respond within 3 business days. Every report is tracked and resolved with priority.
If you encountered an accessibility barrier or have a suggestion for improvement, please email us. We take every feedback seriously.
[email protected]Last updated: September 2026
