Accessibility statement

We target conformance with WCAG 2.1 Level AA. Our deeper goal: a site that's pleasant to use with keyboard, screen reader, or low vision — not just one that passes audit checks.

• Skip-to-content link at the top of every page, visible on focus.
• Keyboard navigation across nav, search (⌘K), forms, CTAs, and the chat widget.
• Semantic landmarks — every page has a main element with a stable ID, proper heading hierarchy.
• Focus-visible rings on interactive elements with a coral ring that meets contrast.
• Prefers-reduced-motion respected on the typing headline, activity ticker, and most scroll animations.
• Dark mode + light mode, both audited for contrast on text and UI states.
• Form labels on every input. Error states are announced and visible.

• The hero's auto-cycling placeholder swap may distract some users. We have a plan to add a pause-on-focus toggle.
• The activity ticker pauses when the tab is backgrounded but doesn't yet expose a manual pause control.
• Per-page OG images aren't a11y blockers but lack textual alt equivalents in the metadata.
• We haven't run a full SR audit against the chat widget on iOS VoiceOver yet. On the roadmap.

We take a11y reports seriously. Email accessibility@aliansoftware.net with the URL and what you ran into. We'll respond within 5 business days and tell you when (or if) we plan to ship a fix.

• Keyboard-only navigation on Chrome, Safari, Firefox
• macOS VoiceOver (latest)
• NVDA on Windows 11
• axe-core + Lighthouse a11y audits per release