Strategy Group

Commitment

Accessibility Statement

A site nobody can use isn't finished. We build to WCAG 2.1 Level AA — on our own site and on every client site we ship.

Last reviewed: August 28, 2026

Conformance target

cwostrategy.com aims to conform to Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We consider the site substantially conformant — it meets the standard with the known exceptions listed below.

What we've implemented

  • Keyboard navigation — every interactive element is reachable and operable by keyboard. The mobile menu traps focus while open, closes on Esc, and returns focus to the button that opened it.
  • Visible focus — a high-contrast green focus ring on every focusable element. We never remove outlines without replacing them.
  • Skip link — "Skip to content" is the first focusable item on every page.
  • Semantic structure — one h1 per page, correct heading order, real landmarks, lists marked up as lists.
  • Contrast — body text and UI controls meet or exceed 4.5:1; large text meets 3:1.
  • Reduced motion — every scroll animation, the pinned horizontal rails, and all transitions are disabled when the OS reports prefers-reduced-motion: reduce. Rails become a plain vertical stack with identical content.
  • Works without JavaScript — all content is in the static HTML. If scripts fail, nothing is left invisible and the rails render as a normal stacked grid.
  • Touch targets — interactive elements are at least 44×44 CSS pixels.
  • Forms — every input has a persistent visible label, errors are announced via aria-live, and invalid fields are identified by text rather than colour alone.
  • Zoom and reflow — content reflows to a single column at 320 px and supports 200% zoom without horizontal scrolling.
  • Meaningful alternatives — decorative graphics are aria-hidden; the analytics chart carries a descriptive text alternative.

Known limitations

  • The pinned horizontal service and testimonial rails use scroll-driven motion on screens wider than 900 px. On narrower screens, and with reduced motion enabled, they render as a plain vertical stack with identical content and no motion.
  • Data tables in the client portal scroll horizontally inside their own container on very narrow screens. The page itself never scrolls sideways.

How we test

  • Keyboard-only walkthrough of every page and flow before release.
  • Automated audits with Lighthouse and axe DevTools on each deploy.
  • Screen reader spot checks with VoiceOver (macOS/iOS) and NVDA (Windows).
  • Manual checks at 320 px width, 200% zoom, and with reduced motion enabled.

Tell us if we've missed something

If you encounter a barrier on this site, we want to know. Email [email protected] with the page address and what went wrong. We aim to acknowledge within two business days and to fix confirmed barriers within 10 business days, or explain why longer is needed.

Accessibility on client work

Every site we build is developed to the same standard. Accessibility is included in the base scope, not sold as an upgrade — it's cheaper to build in than to retrofit, and it's the right thing to do.