Accessibility audits, UX fixes, and AI-ready engineering — for teams who need it done, not just documented.
Services
Try it
Drop in a URL and get a simulated WCAG 2.1 AA audit — issues mapped to POUR principles, with the fix for each. This is the kind of report we hand you, except we also do the fixing.
AI-simulated audit for demo purposes. For production audits, pair with axe-core or Lighthouse.
What WCAG involves
WCAG covers how the page is perceived, operated, and understood. These are three of the dimensions we audit and fix — the rest live in the same places: the components, the tokens, and the markup.
Headings in order, images with real alt text, form fields wired to their labels, and state changes announced — so a blind user navigating by voice gets the same page a sighted user sees, not a wall of unlabelled buttons.
Every link, menu, and modal reachable with Tab, usable with Enter and Escape, with a focus ring you can actually see and no traps you can't get out of — because a lot of people never touch a mouse.
Text at 4.5:1 against its background, interactive elements at 3:1, and meaning never carried by colour alone — so the page stays legible in sunlight, on a cheap panel, and for the one in twelve men with colour-vision deficiency.
Nielsen-heuristic UX audit, WCAG 2.1 AA remediation, and component-level React fixes.
User Experience · WCAG 2.1 AA/AAA · W3C · Figma
A page-builder WordPress site brought to WCAG 2.1 AA — fixed in the theme and the blocks, not behind an overlay.
WordPress · Child Theme · Elementor · WCAG 2.1 AA
Also in the lab
Push code. Watch it travel through GitHub, OpenAI, and back — in real time.
Craft
We don’t treat them as separate engagements. The same decisions shape both — and shipping one without the other always shows.
UX as engineering
Time-to-interaction is a UX outcome before it’s a Lighthouse number. We profile what the user actually waits for and fix the things that show up in the data — not the things that show up in a designer’s ticket.
Accessibility as engineering
Contrast in the tokens. Keyboard behavior in the component library. Screen-reader flows in the routing layer. CI gates that fail when a regression lands. Not a phase before launch — a property of the product.
What clients say
They diagnosed the issue in the first call and fixed it within a week. The dashboard hasn’t dropped a frame since.
Let's talk for 20 minutes. No pitch. Just diagnostics.
