Accessibility · filed 2026.06
Built to be used.
the wingman project makes loud, color-soaked, animated work. None of that is worth much if you can’t read it, reach it, or tab through it. This page says plainly what we do for access, what we don’t do yet, and how to tell us when something gets in your way.
fig. 01: the focus ring, never hidden
Our commitment
We think accessibility is craft, not compliance paperwork. A page that only works for some visitors is an unfinished page. So access is part of how we build (in the design system itself, not bolted on after) and every new page we ship is held to the standards below.
We won’t pretend the work is done. It isn’t. But here is exactly where it stands.
What’s in place today
- 01
Skip link & landmarks
Every page starts with a “skip to content” link that appears the moment it receives keyboard focus, and the content lives in a proper
mainlandmark with the document language declared. - 02
Reduced motion, respected
The site is animation-forward by design, and motion sits behind your system’s
prefers-reduced-motionsetting. Our stylesheets (navigation included) carry reduced-motion rules that switch animation off when you’ve asked for calm. - 03
Visible keyboard focus
Where we style focus, we use
:focus-visibleso keyboard users get a clear ring: the navigation menu and the contact form carry custom focus states, and we never strip the browser’s focus indicator sitewide. - 04
Tap targets you can hit
Navigation links, buttons, and form controls are built to a minimum 44-pixel touch target. Thumbs are not precision instruments and we design like we know that.
- 05
Labeled forms, real headings
Every field on our contact form has a programmatically associated label (no placeholder-as-label tricks) and pages use semantic heading hierarchies rather than styled divs.
- 06
A floor under mobile type
Our type scale is fluid, and the pages we’re building now hold body and label text to an 11-pixel rendered minimum on small screens.
Where we fall short, honestly
This site is visually rich on purpose: painted fields, dense drawings, a lot of motion. That ambition creates real accessibility work, and some of it is still in front of us:
- The site leans hard on animation. We keep it behind the reduced-motion preference, but if you don’t have that preference set, some pages are busy. That’s a trade-off we’ve made consciously, and the escape hatch is real.
- Some decorative micro-captions on older pages run smaller than the 11-pixel floor we now hold ourselves to. We’re sweeping them as pages get rebuilt.
- We draw hundreds of bespoke illustrations, and we have not yet finished a full audit of alternative text across every illustration-heavy page.
- Custom focus styling exists where it matters most (navigation and forms) but isn’t yet uniform across every interactive flourish on every page.
The goal
We are working toward WCAG 2.2 AA across the site. That phrasing is deliberate: we’re not claiming a conformance certification, and we won’t until the claim would be true everywhere, not just on our best pages. The standard is the direction of travel, checked against real pages every time we rebuild one.
Found a barrier? Tell us.
If anything on this site is hard to read, hard to reach, or hard to operate (with a screen reader, a keyboard, a switch, your thumbs, anything) we genuinely want to know. Write to us and describe what happened and where. We will respond, and if it’s something we can fix, we’ll fix it.
hello@thewingmanproject.com