Accessibility statement

PraxTalk targets WCAG 2.1 Level AA conformance across the public marketing site, the visitor chat widget, and the operator dashboard. We track against this standard because it is referenced by the EU Accessibility Act (2025), Section 508 (US federal procurement), and the AODA (Ontario), which together cover the most common procurement requirements we encounter.

• Skip-to-main-content link as the first focusable element on every page (WCAG 2.4.1).
• Visible focus ring on every keyboard-focusable element via *:focus-visible (WCAG 2.4.7), accent-coloured for contrast against both paper and ink backgrounds.
• Reduced-motion support — @media (prefers-reduced-motion: reduce) disables the hero gradient animation, console glow, slot-pulse, and typing-dot animations (WCAG 2.3.3).
• Semantic landmarks — every page wraps its primary content in <main id="main"> so screen readers and the skip-link both reach it (WCAG 1.3.1, 2.4.1).
• Decorative images marked aria-hidden — every social icon and presentational SVG (WCAG 1.1.1).
• Form labels — every input on /setup, /login, /sign-up, /contact, and /book-demo uses the <label> + <input> pattern (WCAG 1.3.1, 4.1.2).
• Keyboard nav for the mobile menu, cookie consent banner, and approval-decision dropdowns — all interactive elements are reachable with Tab and actionable with Enter / Space (WCAG 2.1.1).

PraxTalk has not yet completed an external accessibility audit. Internal review surfaced these areas where AA conformance is not yet verified end-to-end:

• Color contrast verification — The muted text color (rgba(15, 26, 18, 0.58) on the paper background) measures around 4.5:1, the WCAG AA minimum for normal text. Border-line; an external auditor may flag specific instances under bright conditions.
• Operator dashboard (/app) — Inbox row keyboard navigation, conversation pane focus management, and the activity feed have not been formally screen-reader tested with NVDA / VoiceOver / JAWS.
• Visitor widget — runs inside a shadow DOM with its own CSS reset; assistive-technology behaviour with the embedded widget on customer sites has not been formally tested.
• Booking page (/book/:slug) — slot picker uses keyboard-actionable buttons but the layout is dense; an auditor may recommend explicit ARIA grouping.
• Animated screenshots and PDFs — None are currently shipped, but if/when they are, captions + transcripts will be required (WCAG 1.2.1, 1.2.2).

A formal VPAT 2.4 / Accessibility Conformance Report (ACR) by an independent auditor is on the v1.0 roadmap. Until that ships, this page is the most current statement of conformance posture; it's reviewed quarterly and updated whenever a known gap is closed.

If you encounter an accessibility barrier on PraxTalk — broken focus order, an image without alt text, contrast below AA on a specific element, anything — email hello@praxtalk.com with the page URL and a short description. We aim to respond within 2 business days and ship a fix (or a documented workaround) within 30 days for AA-blocking issues.

This statement is reviewed by the PraxTalk team on a quarterly cadence. Last reviewed May 3, 2026.