Accessibility statement.

Our target standard

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines explain how to make web content more accessible to people with visual, auditory, cognitive, and motor impairments.

We review our conformance regularly and treat accessibility issues as high-priority bugs.

What we have implemented

The following are built into the site:

• Semantic HTML with a correct heading hierarchy on every page.
• Keyboard navigability — every interactive element is reachable and operable by keyboard alone.
• Descriptive alternative text on all meaningful images.
• Contrast ratios that meet or exceed the WCAG AA minimums: 4.5:1 for body text and 3:1 for large text.
• A visible focus indicator on every interactive element.
• Labels on icon-only controls, including the menu, the language switcher and the WhatsApp button.
• Motion that respects the prefers-reduced-motion setting, which disables every animation on the site.
• No flashing or strobing content.
• English, Spanish and Portuguese, each served with the correct language attribute.
• A responsive layout that holds at any viewport size and at browser text zoom up to 200%.
• Form inputs with associated labels and clear error messages.

Technical approach

The site is built with plain HTML, CSS and JavaScript — no framework that introduces accessibility barriers. Interactive components are implemented with standard DOM APIs and keyboard event handlers.

The consent banner, the language switcher, the FAQ accordion and the finder all support keyboard operation. Static content works without JavaScript, with progressive enhancement for the interactive parts.

Known limitations

We are aware of the following and are working to improve them:

The finder uses focus management that may not be optimal in every screen reader and browser combination. We are testing and improving it.

Decorative illustrations are hidden from screen readers. Where an illustration carries a figure, we are reviewing whether that figure should also appear as text.

We want to hear from you

If you run into a barrier on this site, please tell us — your feedback is what makes it better.

Include a description of the issue, the page or feature affected, and the assistive technology and browser you use, if you know them. We will acknowledge your message within two business days and work toward a resolution.

Third-party content

Some functionality relies on third-party services, including Google Fonts and Google Analytics. We aim for these to be accessible but cannot fully control their implementation, and we have selected services that publish their own accessibility statements.

Google Fonts provides the Poppins typeface used throughout the site. The typeface is designed for legibility and includes a full Latin character set.