Accessibility.

We’re building toward WCAG 2.2 Level AA. That’s a target we’re working from, not a certification we’ve earned yet — this page says exactly where things stand.

What’s in place today

Semantic structure

Every page uses real header/nav/main/footer landmarks and heading levels rather than styled divs, so screen reader users can navigate by structure.

Visible keyboard focus

Every interactive element — links, buttons, form controls — uses a single shared focus-ring style, so keyboard navigation never loses track of where you are.

Reflow without loss of information

The pricing comparison table — the page most likely to be read on a phone — switches to stacked cards below the md breakpoint instead of relying on horizontal scroll, so nothing requires two-dimensional scrolling to read.

Data table semantics

Comparison tables use scope="col"/scope="row" on header cells, so a screen reader announces which plan or column a value belongs to.

Meaningful alternative text

Logo and icon images carry descriptive alt text; purely decorative graphics are marked aria-hidden so they don’t clutter screen reader output.

What isn’t done yet

Listed here instead of left for you to find. None of it is hidden in a roadmap doc you can’t see.

  • No formal WCAG 2.2 AA audit — automated (axe/Lighthouse) or manual — has been run against the site yet. Pages have been checked visually via screenshots at two viewport sizes, which catches layout bugs, not accessibility defects.
  • No screen reader pass (VoiceOver/NVDA/JAWS) has been done across the site.
  • No "skip to main content" link exists yet.
  • The /compare page’s comparison table still uses horizontal scroll on small screens rather than the stacked-card pattern used on /pricing.
  • Color contrast has been designed against the brand kit’s intent but not independently measured against every text/background combination on every page.

Tell us what’s not working

A dedicated accessibility feedback channel isn’t set up yet. Once one exists, it will be linked from this page rather than asserted before it’s real.

Ready to try it?

    Accessibility — NUA Social