Accessibility
Last reviewed 6 October 2026.
We want everyone to be able to search the directory, read a listing and send a request, including people who use a keyboard, a screen reader, zoom or high-contrast settings. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. This page describes where we are against that target; it is not a claim that every page meets it.
How we check
We run an automated audit with axe-core, an open-source accessibility testing engine, against the WCAG 2.0, 2.1 and 2.2 level A and AA rules it covers. Each run loads every kind of page on the site (directory and country pages, manufacturer profiles, guides, tools, and the contact and quote forms) at desktop and phone widths.
What is in place
- A “skip to content” link and labelled page regions, so keyboard and screen-reader users can move past the menu.
- A visible outline on whatever has keyboard focus.
- A label on every form field, and error messages written out in words, not shown by color alone.
- Data tables with captions and column headers. Wide tables can be scrolled with the keyboard.
- Text that meets the AA contrast ratio, and pages you can zoom on any device.
- No accessibility overlay or widget. We fix the pages themselves.
Recent fixes
Our 6 October 2026 audit found, and we fixed:
- Small labels on manufacturer listings, such as “Operations”, were slightly below the contrast minimum.
- The dosage-form summary on country pages was marked up so screen readers announced it as an empty list.
- The conversion and capsule tables on two tools scrolled sideways on phones but could not be reached by keyboard.
Known limitations
- Automated testing finds many problems but not all of them. It cannot judge whether a page makes sense when read aloud or whether its order is logical. We have not yet had the site reviewed by someone who uses a screen reader every day.
- Company names, addresses and operations come from public registries in the form the registry publishes them, which sometimes means capitals, abbreviations or codes that read awkwardly aloud.
- Payment for a Featured listing happens on Stripe’s checkout page, which Stripe builds and maintains, not us.
Report a barrier
If something on the site does not work for you, tell us. Include the page address and what happened. We read every report, and fixing a barrier comes before new features. If you need information from a listing in another format, ask and we will send it.