Accessibility Statement

Primary standard: Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.

Additional references: EN 301 549 (European public sector), Section 508 (US federal), ADA Title III (US private sector).

The marketing site at www.optimizepilot.com is partially conformant with WCAG 2.2 AA. We run automated scans on every deploy and a manual audit quarterly.

Known areas under active remediation:

• Some animated transitions do not yet respect the prefers-reduced-motion preference. Targeted fix: Q2 2026.
• Certain decorative SVG charts lack aria-hidden attributes. Targeted fix: next release.
• The pricing toggle has a focus order that skips one interactive element on keyboard nav. Targeted fix: next release.

We test with the following combinations on every major release:

• NVDA 2024.x + Firefox (Windows)
• JAWS 2024 + Chrome (Windows)
• VoiceOver + Safari (macOS 14+, iOS 17+)
• TalkBack + Chrome (Android 13+)

If you use other assistive technology and encounter a barrier, please let us know — we treat assistive-tech compatibility as a bug class, not a wishlist.

Email accessibility@optimizepilot.com. Include:

• The page URL or product screen where you encountered the issue.
• A short description of what happened.
• Your assistive technology and browser, if relevant.

We acknowledge within one business day and provide a remediation timeline within five. Critical blockers (prevents a user from accessing a feature) are treated as Sev-1 incidents.

Automated: every deploy. Axe Core, Lighthouse, and our own accessibility scan run in CI. Regressions block merge.

Manual: quarterly full-site audit. Third-party audit annually. Full report available to Enterprise customers on request.

Targeted improvements for the next two quarters:

• Q2 2026: full prefers-reduced-motion support.
• Q2 2026: AAA contrast on all primary surfaces (currently AA).
• Q3 2026: third-party WCAG 2.2 AA audit + published report.
• Q3 2026: EN 301 549 gap analysis for EU public-sector customers.

We maintain an Accessibility Response Team of three engineers on rotation. Any reported issue is triaged within one business day and categorized into: Sev-1 (prevents feature access), Sev-2 (significant friction), or Sev-3 (cosmetic or redundant path).

Sev-1 issues are fixed in the next release (typically within two weeks). Sev-2 issues ship within four weeks. Sev-3 issues are scheduled transparently.