Skip to main content

Open navigation menu

Beta policy — legal review pending

Accessibility

We want the Lifeisgood Beta to be usable with a keyboard, screen reader, zoom, high contrast preferences, and reduced motion. This statement describes engineering goals and testing; it is not a certification of full conformance.

Effective July 14, 2026

Beta policy — legal review pending
This document is a good-faith Beta disclosure, not a claim of legal approval. It must be reviewed by qualified U.S. and Canadian counsel before general availability or any paid launch.

Accessibility target

The product target is WCAG 2.2 Level AA for the supported Web experience. Automated checks are combined with keyboard, focus, screen-reader, zoom, reduced-motion, responsive, and visual review because automation alone cannot establish conformance.

Designed interaction support

  • Skip links, semantic headings, landmarks, labels, validation summaries, and visible keyboard focus
  • Keyboard alternatives for selection, dialogs, milestone ordering, and primary actions
  • Status and error announcements that do not rely only on color
  • Responsive layouts reviewed at 390, 1024, and 1440 CSS pixels
  • Reduced-motion support and text contrast designed for Level AA targets
  • Markdown and PDF export designs intended to preserve a clear reading order

Browsers and assistive technology

The release test matrix covers current Chromium, Firefox, and WebKit engines. Assistive-technology behavior can vary by browser and operating system, so a passing automated test does not guarantee every combination.

Known Beta limitations

The product is still a Beta. A complete independent accessibility audit, a public issue-response SLA, and a named accessibility contact have not yet been completed. AI-generated wording may also be unclear even when the surrounding interface is accessible.

Getting help

If an available Beta support channel was provided with your invitation, describe the route, control, browser, operating system, assistive technology, and expected behavior. Do not include passwords, authentication tokens, or private journey text. No public accessibility email is currently offered.

Updates

This statement will be updated when manual audit coverage, known limitations, or the public contact channel changes. Material accessibility defects remain launch blockers rather than being treated as accepted Beta behavior.