Ops Automators LLC builds automation for operations teams, and plenty of the people doing that work use a keyboard, a screen reader, or a zoomed-in browser to do it. This page says where opsautomators.com stands, including the parts we have not finished.
1. The standard we build to
We target WCAG 2.2 Level AA. We are not claiming full conformance, because we have not had an independent audit. What we can say is that the site was built against that checklist and is tested against it, and that the known gaps are written down in section 4 rather than left for you to discover.
2. What is already in place
- A skip to main content link as the first focusable element on every page, hidden until it takes focus.
- Real landmarks:
header,nav,main, andfooter, so screen-reader users can jump straight to the content. - One
h1per page and headings that descend in order, so the outline you hear matches the one you see. - Visible focus rings on every link, button, toggle, and form field. The whole site, including the navigation dropdowns and the cookie banner, is operable from the keyboard.
prefers-reduced-motionis respected. Turn it on in your operating system and the scroll reveals, ambient gradients, and hover transitions stop.- Alternative text on images that carry meaning, and
aria-hiddenon the decorative icons and cover art so they are not announced. - Text contrast checked against the 4.5:1 minimum, and 3:1 for large headings, against the site’s dark background.
- Text reflows without a horizontal scrollbar down to a 320px viewport, and stays readable at 200% zoom.
- Forms with real labels, errors shown as text rather than colour alone, and no field that depends on placeholder text to explain itself.
3. Browsers and assistive tech
The site is built for the current and previous major versions of Chrome, Edge, Firefox, and Safari, including Safari on iOS 15.4 and later. It should work with recent versions of NVDA, JAWS, VoiceOver, and TalkBack. If you use something older or less common and hit a wall, tell us which combination and we will test against it.
4. Known gaps
Honest list, kept current as we close things out:
- Stripe Checkout. Paying a deposit hands you over to Stripe’s hosted checkout, which we do not control. If it blocks you, email us and we will invoice you directly instead.
- Our content studio at /studio. That is a third-party editing tool for our own team, not a visitor page, and its accessibility is Sanity’s.
5. How we test
We run Lighthouse’s accessibility audit over the main templates (home, blog, catalogue, ROI calculator) and re-run it after any change to the shared layout. Automated tools only catch a fraction of real problems, so those runs are backed by manual passes: navigating a template with the keyboard alone, walking the page with a screen reader, forcing reduced motion, and zooming to 200%. New templates get the same treatment before they go live.
6. Tell us what is broken
If any part of this site blocks you, we want the report. Email info@opsautomators.com with the page URL, what you were trying to do, and the browser and assistive technology you were using. Screenshots or a short recording help but are not required.
We acknowledge accessibility reports within two business days and tell you either when the fix is going out or why it is going to take longer. If the fastest route to what you needed is a person, say so and we will send the information another way or walk you through it on a call.
Prefer a form? The contact page reaches the same inbox.
7. Keeping this current
We review this statement whenever we ship a new page template, and at minimum every six months. The date at the top changes when the content does.
Ops Automators LLC · Orlando, FL · United States