Accessibility Statement

We want Jettson.dev to be usable by everyone, including people with disabilities. This page describes our current accessibility posture, known gaps, and how to reach us.

1. Standards

We aim to meet WCAG 2.1 Level AA where reasonably feasible across the marketing site, docs, dashboard, and key product flows. We treat accessibility as a product quality concern, not an afterthought.

2. Implemented today

• Semantic HTML landmarks (<nav>, <main>, <footer>) on every page.
• Single <h1> per page; logical heading hierarchy.
• :focus-visible focus rings on all interactive controls.
• Color contrast targets WCAG AA on body text against the dark background.
• prefers-reduced-motion is honored — entrance and scroll animations are disabled when the OS requests reduced motion.
• 44×44px minimum tap targets on mobile.
• Keyboard navigation across the marketing site, docs, signup, login, and console.
• Skip-to-content patterns where the page has heavy header chrome.
• viewport-fit=cover with safe-area-inset padding so iPhone notch / home indicator do not cover content.

3. Known gaps (honest list)

• Dashboard data tables — keyboard navigation across some long tables is not yet ideal; we are improving column-header semantics.
• Code blocks in docs — some syntax-highlighted blocks rely on color alone to indicate token types.
• Loading spinners and progress — some lack accessible labels.
• Form validation messaging — most fields announce errors via aria-describedby, but a few legacy forms still rely on visual cues only.
• The hero video on the landing page autoplays without explicit user opt-in; we provide a CSS-only fallback for users who block video, but the page does not yet expose a play/pause control.

We are working on these. If something specific blocks you, please tell us — see Section 5.

4. Assistive technology

The product has been spot-tested with VoiceOver on macOS and iOS, NVDA on Windows, and screen-reader keyboard navigation. We have not yet completed a third-party accessibility audit.

5. Reporting an accessibility issue

If you encounter an accessibility barrier, please email customertek@rwxtek.com with subject "Accessibility" and include:

• The page URL or area of the product.
• A description of what's blocking you.
• Your assistive technology and browser/OS, if you know it.

We aim to respond within two business days and to ship fixes for confirmed AA-level barriers within a reasonable timeline.

6. Ongoing improvement

We treat accessibility as ongoing work, not a one-time project. Significant updates will be reflected on this page with a new "Last updated" date.

7. Contact

Accessibility: customertek@rwxtek.com.