Accessibility — Our Standard, Our Gaps, How to Tell Us | Zolley

Accessibility

Built to be used by everyone.

We build websites to WCAG 2.1 Level AA, and we hold this site to the same standard we sell. That means contrast that is measured rather than guessed, every control reachable from a keyboard, structure that reads correctly in a screen reader, and motion that respects the setting you already chose. Below is what we do, where we know we fall short, and how to tell us if something stops you.

Report a barrier Open a support ticket
built in, not retrofitted
  • Contrast, measuredEvery text pair checked against its background — and against the lightest stop where that background is a gradient
  • Keyboard operableEvery link, button, form field and disclosure reachable and usable without a mouse, with a visible focus ring
  • Skip to contentThe first thing a keyboard lands on, so the navigation is never a wall
  • Motion respects your settingIf your system asks for reduced motion, animation and smooth scrolling stop

These are checks on this site, not a certification. Last tested October 2026: every page, desktop and phone, against WCAG 2.1 AA. The honest limits are below.

The standard we build to.

WCAG 2.1 Level AA is the benchmark most accessibility law points at. Here is what meeting it actually involves, rather than a badge.

Text you can readBody text at 4.5:1 against its background, large text and interface elements at 3:1. On a gradient we measure against its lightest stop, because that is where it fails.
Structure that means somethingOne h1 per page, headings in order, landmarks, lists that are lists. A screen reader reads the outline, not the styling.
Images that carry their meaningAlternative text where an image says something, and an empty alt where it is decoration — announcing a background texture is noise, not access.
Forms that explain themselvesEvery field labeled, errors described in words rather than color alone, and no time limit that punishes a slower reader.
Targets you can hitInteractive controls sized for a thumb rather than a stylus, with spacing that forgives a near miss.
Nothing that only works one wayNo information carried by color alone, no control that needs a hover, no flow that only completes with a mouse.

We build client websites to the same standard. Where a client supplies content after launch — photos, documents, video — keeping it accessible is a shared job, and we say so in writing rather than after the fact.

Where we know we fall short.

A statement that claims everything is fine is worth nothing. These are the gaps we are aware of on this site today.

  • Third-party embeds. Some booking, payment and chat components come from platforms we do not control. We test them, we choose the more accessible option where there is one, and we raise defects with the vendor — but we cannot rewrite them.
  • Video captions. Every client video testimonial on this site is captioned, and so is every one we add. If you find a video without captions, that is a defect — tell us and we will fix it.
  • Documents. A PDF is only as accessible as the file it came from. Anything we produce ourselves is tagged; older documents may not be.
  • Automated testing is not a person. Tooling catches contrast, labels and structure. It does not catch whether a page makes sense. If something reads as nonsense to you, that is a defect even if every checker passes.

If something on this site blocks you, tell us.

You do not need to know why it is broken or what to call it. Describe what you were trying to do and what happened.

By phone

(888) 503-3750, weekdays 9–5 Eastern.

By email

[email protected] — read by a person, answered by the next business day.

With a ticket

Open a support ticket and you get a number on the spot, so there is something to follow up on.

Tell us the page, what you were trying to do, and what got in the way. If you use assistive technology, naming it helps us reproduce the problem — but it is not required.

Hold us to it.

This statement describes zolley.com and the standard we build client sites to. If you are weighing us up for a build, accessibility is not an upgrade we quote separately — it is part of what building a website means here.

How we build websites Ask us anything
Book a call