Skip to the content

Accessibility

Last updated

What this site does to meet WCAG 2.2 AA, and honestly where it falls short.

On this page
  1. What we aim for
  2. What is in place
  3. Where it falls short
  4. Tell us
In short

  • We aim at WCAG 2.2 AA and get most of the way there.
  • Everything works with a keyboard; the editors are the part still being improved.
  • If something blocks you, write to us and we will fix it rather than explain it.

What we aim for

Zeoob is built to meet WCAG 2.2 level AA. That is a target, not a certificate: this page says honestly where the site meets it and where it does not.

What is in place

  • Every control is a real button, link or form field, reachable and operable with a keyboard, with a visible focus ring.
  • Body text meets 4.5:1 contrast, and large text 3:1, against its background.
  • Tap targets on phones are at least 44 × 44 px.
  • Headings run in order, and every page has one h1 and a skip link to the main content.
  • Images that carry meaning have alt text; decoration is hidden from screen readers.
  • Animation respects prefers-reduced-motion; nothing moves if you have asked it not to.
  • Layouts reflow to 320 px wide and to 200% zoom without losing content.
  • The site does not depend on colour alone to tell two things apart.

Where it falls short

We would rather name these than let you discover them.

  • Editing on the preview is the heart of the tools, and it is visual. Every field also has a matching control in the panel beside it, which is the keyboard and screen-reader path, but the preview itself is not a good screen-reader experience.
  • The phone split studio can be resized by dragging the divider. There are buttons for the same thing, but the drag is the discoverable one.
  • Downloaded images are images. They carry no text layer, so a mockup you publish needs its own description from you.
  • Third-party ads are not under our control and may not meet the same standard.

Tell us

If something here stops you doing what you came to do, write to support@zeoob.com and say what you were using — browser, assistive software, phone or desktop. We treat access bugs as bugs, not as feature requests.