Accessibility Statement

Our target, our current status, and an honest list of exactly what's not there yet.

WillIFit.ai exists to keep drivers from finding out the hard way that their vehicle doesn't fit. That only works if the site itself doesn't put up its own barriers. This page says exactly where we stand — the same way we label a clearance reading "imported" instead of dressing it up as verified.

Conformance target

We aim for WCAG 2.1 Level AA. Current status: fully conformant, per our own assessment — an initial audit turned up 47 issues; a same-day remediation pass fixed both Critical findings and the large majority of the Serious and Moderate ones, and a follow-up pass on August 23 closed the last four. "Per our own assessment" is doing real work in that sentence: this is a self-evaluation, not a certified audit, and the claim only covers what code review can see. Nothing gets quietly dropped from this list — it just moves to "fixed."

Target: WCAG 2.1 AA Status: Fully conformant (self-assessed) Last reviewed: September 1, 2026
August 16, 2026 — remediation pass. Following the audit below, we fixed both Critical findings and most of the Serious ones in the same session: the city picker (search, ZIP/address lookup, browse-by-state) is now fully keyboard-operable; status updates, load states, and form results are announced to screen readers; all dialogs and the detail panel manage focus correctly; the color-only fit indicators now carry a non-color signal too; the contrast failures we measured are corrected; and the mislabeled link repeated across all 226 city pages is fixed. What didn't get fixed yet is listed honestly below, not hidden.
August 23, 2026 — remaining items closed. The four items left open after the August 16 pass are now fixed: the app has a real heading hierarchy (modal titles and the detail panel's name and section headers are proper <h2>/<h3> elements, not styled <div>s), the vehicle-preset button no longer claims to open an ARIA menu it doesn't provide (it's an honest disclosure button now), the icon-only clear buttons carry explicit aria-labels instead of relying on title, and the data tables on the clearance guide and Lowest Bridges pages have <caption> elements.
September 1, 2026 — disclaimer contrast fix. The warning text inside the red alert box on the Disclaimer page measured 4.41:1 against its background — just under the 4.5:1 WCAG AA minimum for normal text. The text color for that warning was changed to a lighter red (now well above 4.5:1) while keeping it clearly a safety warning.

How this was assessed

This is a self-evaluation: an internal code review against WCAG 2.1, originally done by four focused passes covering semantic structure, keyboard and focus behavior, color and contrast, and page content — not a certified third-party audit, and not tested with real assistive-technology users. Automated and code-level review catches real, citable issues, but it can miss things only a person using a screen reader or switch device day-to-day would notice. If something here is wrong or incomplete, tell us — that's more reliable than any review we can do of our own code.

What's solid

Not all of this is new — some held up well from the start. Some of it is exactly what changed today:

✓ The city picker — search, ZIP lookup, address lookup, and browse-by-state — is fully keyboard-operable, with proper button semantics and a screen-reader label on every result row.
✓ Status updates reach screen readers: result counts, loading/error states, geolocation status, and all three report forms' submit results now announce through live regions.
✓ All five dialogs (the welcome screen, city picker, and three report forms) are marked as dialogs with a real accessible name, and the city picker's tabs use proper tab/tabpanel semantics.
✓ The garage detail panel now manages focus correctly: it moves focus in on open, restores it to the right place on close — even after the list has re-rendered underneath it — and is removed from the tab order and accessibility tree while closed, via inert.
✓ A real focus trap on every modal — Tab and Shift+Tab wrap correctly, Escape closes the top one first, and focus returns to whatever opened it.
✓ The "fits / tight / won't fit" color coding now carries a non-color signal too (a ✓ / ~ / ✗ mark on every badge, plus a spoken verdict in its accessible name) — color-vision deficiency no longer makes two different verdicts look identical.
✓ Every color pairing we measured as failing — badge borders, map-marker text, the "won't fit" label, UI borders site-wide — now clears its WCAG contrast minimum, checked with calculated ratios, not eyeballed.
✓ A working skip link that actually moves focus (not just scrolls), one clear page heading, and a visible focus ring everywhere — no component silently disables it.
✓ Body text contrast is strong throughout (15:1+ on the main text, 5:1+ on secondary text).
✓ Reduced-motion, reduced-transparency, and increased-contrast preferences are all respected — including the map's own pan/zoom animation, which needed an explicit check since CSS alone can't reach it.
✓ Every page — all 226 city pages included — has a language attribute, one clear heading, a descriptive unique title, and a <main> landmark.
✓ No unlabeled images anywhere on the site, because the site doesn't use any.

Known issues

Every item from the four-pass audit — both Critical findings, the Serious and Moderate ones, and the last four Minor items — is now fixed. We don't currently have an open, known WCAG issue to list here.

That is not a claim of perfection: this is a self-evaluation, and code review can't catch what only a person using a screen reader or switch device day-to-day would notice. When something new is found — by us or by you — it will be listed here while it's open, the same way the items above were.

What we're doing about it

The audit backlog is clear, so the work now is keeping it that way: new features get checked against the same criteria before they ship, and we'll keep updating this page as things change, not just when new findings show up.

Report a problem

If you hit an access barrier anywhere on the site — something above, or something we missed — we'd genuinely rather hear about it than not:

Read more about who builds this and why, or go back to the map.