Skip to main content
Ops Automators logo

Accessibility

Accessibility Statement.

Last updated: August 12, 2026

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, and footer, so screen-reader users can jump straight to the content.
  • One h1 per page, and heading levels that descend in order without skipping one, checked by an automated pass over the home page, contact page, catalogue, ROI calculator, and this page.
  • Visible focus rings on every link, button, toggle, and form field, including the ones inside the dropdowns. The ring is 2px of brand yellow and measures at least 4.3:1 against whatever sits behind it, so you can find it on a dark panel.
  • The navigation dropdowns and the catalogue’s category filter open with Enter, move with Tab, and close with Esc, which puts focus back on the button that opened them. They are plain lists of links and buttons, so Tab is the way through them; we do not claim an arrow-key menu we haven’t built.
  • While the cookie banner is up it is the second thing Tab reaches, right after the skip link. Esc dismisses it and means exactly what its ✕ means: non-essential cookies denied. Escape never grants consent. The page also reserves the strip the banner covers while it is showing, so it can’t sit on top of a button you just tabbed to.
  • prefers-reduced-motion is mostly respected. Turn it on in your operating system and the scroll reveals stop, the drifting background gradients stop, and every hover and state transition collapses to an instant change. Two panels still animate as they appear, and section 4 says which and why. We would rather name them than let “respects reduced motion” imply more than it does.
  • Alternative text on images that carry meaning, and aria-hidden on 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. Our automated pass over the home page, contact page, catalogue and ROI calculator reports no contrast failures.
  • Text reflows without a horizontal scrollbar down to a 320px viewport, and stays readable at 200% zoom. Checked on the home page, contact page, catalogue, ROI calculator, and this page.
  • Forms with real labels, errors shown as text rather than colour alone, and no field that depends on placeholder text to explain itself.
  • Content that changes without a page load says so. Filtering the automation catalogue announces how many automations matched, and the count stays on the page afterwards so you can go back and read it again. The contact form announces both outcomes: a send that fails says why, and a send that works confirms it and moves focus into the confirmation instead of dropping you at the top of the page.
  • The charts on /roi-calculator carry a text description of what they plot, so the payback month and the year-by-year totals are available without seeing the shape. Every number in them is also written out in the stat cards above.
  • The calculator sliders announce a formatted value with its unit as you drag or arrow through them — “$48 per hour”, not “48”.

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:

  • Two panels still animate under reduced motion. The cookie banner slides up as it appears, and the catalogue’s category dropdown fades down about 4px as it opens. Both are driven by our animation library rather than a CSS transition, so the reset that stops everything else doesn’t reach them. Neither runs longer than about a third of a second, and the distances are small, but they are movements, and if you turned reduced motion on you asked for neither.
  • Links inside paragraphs. In body copy, a link is yellow where the text around it is grey, and the underline only appears on hover. Those two colours are 1.55:1 apart, under the 3:1 that colour-only differentiation needs, so if you can’t distinguish them you may not spot the link until you hover it. Fixing this means an underline in prose, which is a design change we haven’t made yet.
  • Screen-reader announcements are built and inspected, not certified. We verify the live regions, roles, and focus order that screen readers depend on, in the browser. We are not claiming to have re-run every flow through NVDA, JAWS, and VoiceOver on the current build.
  • 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 axe-core and Lighthouse’s accessibility audit over the main templates (home, contact, catalogue, ROI calculator) and re-run them after any change to the shared layout. Automated tools only catch a fraction of real problems, so those runs are backed by manual passes in a browser: tabbing a template with the keyboard alone and nothing else, reading the accessibility tree to check what a screen reader would be handed, measuring focus rings against the pixels actually drawn behind them, 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