Policy

Accessibility Statement

We aim for inclusive, keyboard-first access for core flows. This page documents the current target, known review areas, and how to request help.

Current accessibility commitments

We design core navigation, legal, and contact paths for keyboard and screen reader use.

Semantic landmark structure and predictable heading order.
Visible focus indicators and skip-to-main navigation on all pages.
Clear labels for form inputs, actions, and link purpose.
Reduced motion support where relevant for motion-heavy sections.

The site is designed so users who rely on screen readers can identify controls, sections, and navigation in order.

Logical flow in the main content with descriptive section headings.
High-clarity body text and status content in the main content flow.
Links and controls use readable labels instead of icon-only actions for critical flows.

Conformance target

Core conversion and contact journeys target WCAG 2.2 AA. This is a working target, not a certification claim or external audit result.

We prioritize blocking-level barriers first.
When we discover new blockers, we fix them before major release cycles.
We treat legal consent and contact paths as core and keep them keyboard accessible.

How we test and review

Recent manual review covered keyboard navigation, focus visibility, legal pages, and consent controls. Last reviewed: June 2, 2026.

Known limitations and fixes in progress

Some older browser and assistive-technology combinations can still present edge cases.

Hero media and visual interactions require continued review for non-mouse access paths.
Complex overlays or animation transitions are treated as potential barriers and simplified when they block core use.
Blocking issues in legal, navigation, and contact paths are prioritized before cosmetic work.

Report an issue

If navigation, forms, or consent controls are difficult to use with assistive technologies, email support@jabbieworld.com and include the browser, assistive tool, and page.