Accessibility Statement

Party Genius AI is designed to be usable by as many people as possible, including people who use screen readers, keyboard-only navigation, screen magnifiers, voice control, or reduced-motion settings. We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. We are a two-person team, so accessibility is an ongoing practice rather than a finished project. This page documents where we stand today, what we know we still need to fix, and how to reach us if you hit a barrier we have not caught yet.

The entire site — including the planner, all 25 tools, the dashboard, and every form — is designed to be usable with a keyboard alone. What this means in practice: • A visible "Skip to main content" link appears at the top of every page when you tab into it. • Tab order follows the visual flow of each page. • Every interactive element has a visible focus ring (high-contrast outline). • Modal dialogs trap focus while open and return focus to the triggering element on close. • Menus, popovers, and dropdowns open and close with Enter, Space, and Escape as expected. If you find a page where keyboard navigation breaks — a trap, a missing focus indicator, an interactive element that a screen reader cannot reach — please report it using the contact info in §8.

We actively test with: • VoiceOver on macOS (Safari) and iOS (Safari). • NVDA on Windows (Firefox, Chrome). What we do to support screen readers: • Semantic HTML (heading hierarchy, landmarks, lists) instead of divs-everywhere. • ARIA labels only where semantic HTML is insufficient — never as a replacement for correct markup. • Alt text on all content images describing what matters to the reader, not just "image". • Form controls labeled explicitly; error messages linked to the relevant input with aria-describedby. • Loading, progress, and status messages announced via ARIA live regions where appropriate. We do not claim 100% coverage — if you hit an unlabeled control or a confusing announcement order, flag it.

Typography and color choices are designed to meet WCAG 2.1 AA contrast ratios (4.5:1 for body text, 3:1 for large text). • Body text uses our design system's text-secondary or stronger token — never disabled-grey that would drop below 4.5:1. • Minimum font size is 14px in app UI, 16px in marketing content, 12px only for labels that appear alongside larger primary text. • Focus rings are high-contrast and never hidden. • Dark mode is a first-class experience, not an afterthought. All contrast checks apply in both modes. • Layouts reflow cleanly down to 320px viewport width. If you rely on browser zoom, custom stylesheets, or high-contrast mode, the site should remain usable — if it does not, please report.

We use animation sparingly — mostly for subtle entry transitions and confirmation feedback. • All non-essential animations respect the prefers-reduced-motion browser setting. When you opt into reduced motion, parallax effects, auto-playing animations, and decorative transitions are disabled. • We do not autoplay video with sound. • We avoid content that flashes more than three times per second (photosensitive epilepsy trigger). If you see an animation that does not respect your reduced-motion preference, treat it as a bug and report it.

Honest inventory of barriers we know exist and are actively working on: • A handful of older tool pages still use placeholder icons without adjacent text labels; we are in the middle of adding accessible names to every icon-only button. • The Remotion-generated party recap video does not currently include captions. For now, the video is purely visual and decorative; we plan to add caption tracks when we ship v2 of the recap. • Some third-party embeds (Stripe checkout, for example) are governed by their own accessibility conformance which we cannot directly control. • We have not yet completed a formal independent VPAT audit — one is planned once the product stabilizes post-BSIS migration. If you encounter a barrier not listed here, please report it — "we know about it" should never be a reason we surprise you.

Primary test matrix: • VoiceOver (macOS Safari, iOS Safari). • NVDA (Windows Firefox, Windows Chrome). • Full keyboard-only navigation on all supported browsers. • Chrome Lighthouse accessibility audit (target score ≥ 95 on every public page). • axe DevTools manual spot-checks on high-traffic pages. Not yet systematically tested but planned: • JAWS on Windows. • TalkBack on Android. • Dragon NaturallySpeaking for voice control. If you use an assistive tech we have not tested, we would especially like to hear about your experience.

Email accessibility@partygeniusai.com with: • The page URL. • What you were trying to do. • What went wrong. • Your browser, operating system, and assistive tech (screen reader, magnifier, etc.), if relevant. We aim to acknowledge accessibility reports within 3 business days and will tell you honestly whether the fix is same-week, within the current sprint, or parked behind a larger rework. If you prefer, you can also use the general feedback widget at the bottom right of any page — reports are routed to the same inbox.