A site every operator can use.
I want every operator who lands on this site to find what they need, regardless of how they browse the web. That includes people using screen readers, keyboard navigation, voice control, or any other assistive technology.
01 · My commitment
Operator's Bench is committed to making this site accessible to as many people as possible. Accessibility is an ongoing practice here, not a one-time checklist. As the site grows, every new page is built and reviewed against the standards below.
02 · Conformance standard
This site is built to conform with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. Level AA is the standard recommended by the U.S. Department of Justice for compliance with the Americans with Disabilities Act (ADA), and the standard used by comparable laws in Canada, the UK, and the EU.
Specific things implemented across every page:
- Visible keyboard focus indicators on every interactive element.
- Skip-to-main-content link as the first stop when tabbing through the page.
- Color contrast of at least 4.5:1 for body text and 3:1 for large text and interface elements.
- Programmatically associated labels on every form field, with appropriate input types and autocomplete attributes.
- Semantic HTML landmarks (header, nav, main, footer) so screen readers can navigate the page structure.
- Mobile-responsive layout tested down to 320px wide with no horizontal scroll.
- Animations that respect the prefers-reduced-motion setting in your operating system.
- Mobile hamburger menu with focus management: focus moves to the first link when the menu opens, and back to the trigger when it closes. Escape key closes the menu.
- FAQ accordion and interactive 7-point assessment list operable with mouse, touch, and keyboard.
03 · Date of last review
This site was audited and updated for WCAG 2.2 Level AA conformance in May 2026. Re-reviews happen any time the site changes meaningfully, and at minimum every quarter.
04 · Known limitations
Honest list of where the site is short of perfect, so you know what to expect:
-
The interactive 7-point assessment list on the home page is keyboard
operable and announces its state to screen readers, but each row
uses ARIA
role="button"on a list item rather than a native button element. The behavior is correct in testing, but some assistive tech may announce these as list items with button-like behavior rather than buttons. Switching to native buttons is on the list. - Some uppercase monospace labels (the small eyebrow text above section headings) are 11 to 12px. This is intentional for the visual rhythm of the brand. The text is letter-spaced for legibility and contrast meets AA at that size, but if you'd prefer larger text, browser zoom (Ctrl/Cmd and plus, or Ctrl/Cmd plus scroll) works smoothly without breaking the layout.
- The contact form currently relies on browser-native validation messages. Custom error messaging that's slightly more descriptive is in the queue.
- Any third-party tools added later (calendar booking, payment forms, embedded media) are accessibility-reviewed before they ship, but their conformance ultimately depends on the vendor.
05 · How to report an accessibility issue
If anything on this site prevents you from getting what you need, please tell me. I take these reports seriously and will work to fix the issue quickly.
When you write, please include:
- The page you were on (the URL helps).
- The device and browser you were using.
- The assistive technology, if any (screen reader, voice control, etc.).
- A short description of what went wrong.
I will respond within 5 business days and let you know the plan for resolving it.
06 · Formal complaints
If you're not satisfied with my response, you have the right to file a complaint with the U.S. Department of Justice through the ADA website at ada.gov, or with the equivalent regulator for your country or state. I'd much rather hear from you first and fix the issue directly, but I want you to know that option exists.
Questions about this page? Email us.