Accessibility statement

Zome wants everyone to be able to use zome.io, including the free AI report, whatever their abilities and however they browse. This statement explains what we aim for, what the site does today, where we know it falls short and how to tell us about a problem.

Our target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across zome.io. The site hasn't yet been independently audited against WCAG 2.2, so we don't claim full conformance. We check pages as we build them and fix problems as we find them.

What the site already does

Page structure. Every page sets its language to English and has a "Skip to content" link as the first thing you reach with the keyboard. Pages use a header, navigation, main content area and footer, and our build checks confirm that every page has exactly one main heading.
Keyboard use. Menus open and close as buttons that tell assistive technology whether they're expanded, and the Escape key closes them. Links, buttons and form fields show a visible outline when they have keyboard focus.
Reduced motion. If your device is set to reduce motion, the site shortens or turns off animations and scroll effects. It also stops auto-advancing panels, rotating headline words and video, and shows example screens in their finished state.
Video. Video clips on the site are silent and decorative, and they're hidden from screen readers. They load only when needed and pause when they scroll out of view.
Images. Our build checks confirm that every image has a text alternative. Photos that carry meaning are described, and decorative images and icons are hidden from screen readers.
Forms. Form fields have labels or accessible names. On the demo form, success and error messages are announced to screen readers.

Known limitations

We know about these issues and are working on them:

Moving content. Some homepage panels advance on their own, some headlines rotate words, some example screens replay their animation, and some pages have looping silent video. The tabbed panels have previous and next controls, and everything stops when your device asks for reduced motion, but not every moving element has its own pause button yet.
Business name suggestions. On the report page, you can choose a suggested business with the arrow keys, Enter and Escape, but screen readers may not announce the suggestions. You can type your business name and continue without choosing one.
Report progress and results. The report page may not tell screen reader users when a scan starts or finishes. When the report is ready, the results appear at the top of the page.
Field hints on the report page. Some report fields use placeholder text as their only visible label, so the hint disappears once you start typing. Each field still has a label for screen readers.
Scroll effects. Some pages use scroll-linked effects and sections that stay in place while you scroll. These can be harder for some people to follow. Setting your device to reduce motion removes most of them.
Other services. If you choose to message us on Instagram, Instagram's accessibility is outside our control.

Websites and pages we build for businesses

We apply the same WCAG 2.2 AA target to the websites, booking pages and other pages we build for businesses as those features roll out. Content that businesses add, such as photos and descriptions, also affects accessibility, and we help our customers get it right.

Report a problem

If something on zome.io is hard to use, please tell us through our contact page. It helps if you include:

the address of the page
what you were trying to do
what went wrong
the device, browser and any assistive technology you use

If you can't use a form on the site, contact us another way listed on the contact page and we'll help. For example, we can run your free AI report with you on a call. We'll use what you send us only to look into the problem and reply to you.

Keeping this statement current

We review this statement when we make significant changes to the site, and we'll update the date at the top when we do.

Questions about this page? Contact us.