+1Affiliate —See how it works →
SENKU
Start free

Accessibility

Last updated: May 25, 2026

Senku is built to be usable by everyone, including people who navigate with a keyboard, use a screen reader, prefer reduced motion, or have low vision. We’re aiming for WCAG 2.1 Level AA conformance. We’re not all the way there yet — this page documents both what’s done and what we know is still incomplete.

What we have shipped

  • Skip-to-content link at the top of every page (tab to reveal).
  • :focus-visible rings on every interactive element — keyboard users see a clear focus indicator; mouse users don’t get a stray outline.
  • Single <h1> per page with a sensible heading hierarchy on marketing pages.
  • HSTS, X-Frame-Options, and CSP headers — no clickjacking, no mixed-content surprises.
  • Light and dark theme support; theme persists across sessions.
  • Form inputs use <label> elements (not placeholder-as-label patterns).
  • Native <button> elements for interactive controls (not <div onClick>).
  • System fonts and font-display: swap — no text invisibility while fonts load.

Known gaps

We’re tracking these honestly so you know what to expect:

  • Some dashboard data tables (revenue, leads) are read-only on small screens — full filter UI requires desktop.
  • Map components (job locations, GPS clock-in) use Leaflet; screen-reader support there is minimal. We’re looking at adding a text-list alternative.
  • The PDF estimate output renders text and layout but doesn’t include tagged structure for screen readers. The HTML version in the customer portal is fully accessible.
  • The customer-portal signature pad is touch/mouse only; no keyboard alternative yet.

Send us a barrier report

If you hit an accessibility issue, email accessibility@senkulab.com with:

  • The page URL.
  • What you were trying to do.
  • What blocked you (screen reader name + version, keyboard, voice control, etc.).
  • If possible, a screenshot or recording.

We acknowledge reports within two business days. Critical barriers (you can’t complete a core workflow at all) jump the queue.

Standards we follow

  • WCAG 2.1 Level AA — current target.
  • ARIA Authoring Practices — for composite widgets.
  • Section 508 — we don’t sell to US federal agencies today, but the conformance overlap with WCAG AA means we get most of this for free.

Re-audit cadence

We re-audit accessibility every quarter and after any major UI ship. This page is updated when the “Known gaps” list changes.