Accessibility — Undercut

An honest statement, not a certificate.

Our target for this site (getundercut.sh) is WCAG 2.1 Level AA. We've fixed the specific issues an audit found, and we're saying plainly what we have and haven't checked. This is not a claim of full conformance, a VPAT, or sign-off from an accessibility audit firm — none of those exist for this site.

What's been verified and fixed

The first two rounds were spot fixes on the landing page alone. A later pass went through every page in the site — the homepage, About, Developers, Privacy, Terms, 404, and every per-agent landing page (Claude Code, Codex, Copilot, Cursor, OpenCode, Windsurf, Gemini CLI, Amp, Devin, Junie) — checking every distinct text/background color pairing, every form control, heading order, link text, focus styling, image and icon alt text, and interactive target size. It found and fixed:

• Muted-gray text on the wrong background. The site uses two "muted" grays — one tuned for dark panels, one for light ones — and in dozens of places across the homepage and every per-agent page they'd been swapped: light-panel gray on a dark hero/terminal block, or dark-panel gray on a cream/white section. Both read around 2.2–3.3:1, below the 4.5:1 minimum. Every instance was matched to the gray built for its actual background.
• Signal-green and escalate-amber text. Beyond the calculator and vendor-comparison rows fixed in round 3, the same under-contrast green/amber turned up in the homepage's competitor-comparison table, the GSM8K/HumanEval benchmark tables, and the Teams waitlist confirmation and error copy. Same fix as before: the darker text-only variants (#00959c, #c26e12) now carry those instances; button backgrounds and large/bold headline uses were left alone.
• An unreadable placeholder character. The "not applicable" em dashes in the homepage's feature-comparison table were set in the border color itself (1.3:1) — effectively invisible. They're now the same readable gray as the rest of that table's muted text.
• Accessible names for repeated "Copy" buttons. Every per-agent install page has three or four separate "Copy" buttons for different shell commands; each now has an aria-label naming the specific command it copies, so they're distinguishable out of context (a screen-reader button list, for instance) and not just four identical "Copy" buttons.
• Decorative icons hidden from assistive tech. Inline SVG agent-logo icons and the small "›" flow-arrows in the "how it works" diagrams sit next to their own visible text label and add nothing when announced separately — they're now aria-hidden="true", matching the pattern already used for the equivalent <img> icons.
• One undersized tap target. The homepage's "dismiss" button on the GitHub-star callout was 22×22px; it's now 24×24px, meeting the 2.5.8 minimum.
• Heading order, link text, and focus visibility were checked page by page — no skipped heading levels, no vague "click here"-style links, and no CSS anywhere removes the browser's default focus outline without replacing it. No changes were needed there.

Round 3's earlier fixes — accessible names on the homepage's calculator/waitlist form inputs, and native <button>/<a> elements instead of clickable divs — are still in place and were re-checked, not redone.

A follow-up pass took a closer look at the two real lead-capture forms (the Teams waitlist and the cost-audit email form) and the savings calculator. It found and fixed genuine gaps beyond what the full-site sweep above caught:

• Orphaned form labels. The "Who's this for?" individual/team toggle and the "Primary model vendor" control had <label> elements with no for/id tie to their controls. They're now <span>s wired via aria-labelledby, including a self-referencing label on the toggle so its accessible name reflects the current state.
• Missing pressed-state on vendor buttons. The Anthropic/OpenAI/Gemini selector buttons didn't expose which one was active to assistive tech. They now carry aria-pressed and an explicit type="button".
• Unannounced validation errors. Both lead-capture email inputs lacked required/aria-required, and their client-side error text had no programmatic link to the input. Errors are now tied in with aria-describedby and aria-invalid, and the error text itself is a role="alert" element, so a screen reader announces it when validation fails.

Separately, a keyboard-only pass through the homepage's interactive elements — the agent picker, the individual/team toggle, the FAQ accordion, and the companion pages' copy-to-clipboard buttons — confirmed they're all native, keyboard-operable controls needing no fix. The one real gap: the floating GitHub-star callout could only be dismissed by tabbing all the way to its small × button. Escape now dismisses it too.

What hasn't been formally audited

This is a small team shipping fixes as they're found, not a completed compliance program. Specifically not yet done:

• Full screen-reader testing (VoiceOver, NVDA, JAWS) across every page and interactive flow. (The lead-capture forms now announce validation errors via role="alert", but that's implementation, not screen-reader testing.)
• A full keyboard-navigation walkthrough of every page. The homepage's interactive elements have been checked individually and are keyboard-operable, but focus order and trap avoidance haven't been walked end to end, page by page, with a keyboard alone.
• Testing with browser zoom, reduced-motion settings, or assistive input devices.
• A formal WCAG 2.1 AA conformance audit by a third party, or a VPAT. Neither exists for this site — everything above is a self-audit, not independent verification.

Report an issue

If something on this site is hard to use with a screen reader, keyboard only, or any other assistive technology, tell us — open a GitHub issue. We'll treat accessibility bugs like any other bug.

Updated 2026-09-04. Back to Undercut · Privacy · Terms