Back to Rooftop
Accessibility

Accessibility.

We design Rooftop and rooftopos.io to work for everyone — including users of assistive tech. Here's where we are and where we're going.

Standard

WCAG 2.2 Level AA.

We target WCAG 2.2 Level AA across rooftopos.io and the Rooftop platform UI. Where we know we don't meet it yet, we say so — the honest gaps are listed below, not hidden behind a generic statement.

What we've built today

Concrete a11y wins.

Six things you can verify on the live site right now.

Semantic HTML

Real headings, lists, articles, and navigation landmarks. No div soup for layout where a section, article, or nav element does the job.

Keyboard navigation

Every interactive element is reachable by tab. Focus rings use the brand-lime token at 2px ring width with offset, visible on every page background.

Reduced motion respected

prefers-reduced-motion: reduce disables the cinematic dolly-out, scroll-driven animations, twinkling stars, and the rooftop glow breathe.

Color contrast

Body copy meets the 4.5:1 minimum on every page. Brand-lime text uses a darkened light-mode value to stay readable on bg-brand-soft.

Screen reader labels

aria-hidden on decorative icons, aria-label on icon-only buttons, aria-live="polite" on the ROI calculator output region so changes are announced.

Form labels

Every input has a paired Label. Required fields are announced. Error messages are programmatically associated with their input.

Known gaps

Honest list.

  • Some module page mockups (PlayerMock, the AutoFilm thread, the AutoLabels sticker mock) use decorative animation that may distract some users — they ARE gated on prefers-reduced-motion: reduce.
  • Wide tables on the AutoCurb page are horizontal-scrollable below 640px (we made the table horizontal-scrollable rather than wrap-on-mobile, which is debatable).
  • We do not yet provide alt text for the dealership-hero photo beyond a single descriptive line. Plan: extend with a longer description before GA.
  • The pilot intake form does not yet auto-format phone numbers; users must enter the (XXX) XXX-XXXX style themselves.
Report an issue

Tell us what's broken.

Email ken@ken.cc with the page URL, a description of the issue, and what assistive tech you were using. We respond within 5 business days.

Email accessibility

Status

Last reviewed June 2026. Next review: quarterly.