121 CollaborativeFoundation Beta

Accessibility

Accessibility statement.

We are working toward full WCAG 2.1 AA conformance. Accessibility is part of the dignity of the product, not a polish pass after the fact.

Current status

As of June 24, 2026, 121 Collaborative should be treated as partially conformant with WCAG 2.1 AA. We target WCAG 2.1 AA across the public web experience, and we will claim full conformance only for surfaces with current automated, keyboard, and named assistive-technology evidence. Companion, authenticated account workflows, and native Quill assistive-technology verification remain tracked before public full-AA language.

Surfaces reviewed

  • Homepage
  • Eleanor
  • Eleanor Constitution
  • Pricing
  • Companion chat
  • Trust Center
  • Changelog
  • Quill
  • Beta
  • Signup
  • Sign in
  • Notification settings
  • Privacy
  • Terms

Known gaps

  • Companion chat has live-region and keyboard support, but still needs assistive-technology user testing before we call it fully conformant.
  • Quill native keyboard extensions are in scaffold/prototype state; iOS VoiceOver, Dynamic Type, Switch Control, and Reduce Motion must be verified on device before public release.
  • Some authenticated account/settings workflows need a deeper keyboard and screen-reader pass once production account state is available.

What we have fixed

  • Added a skip-to-content link on shared public layout.
  • Added stronger shared keyboard focus indicators for links, buttons, and form fields.
  • Improved Companion transcript live-region semantics for incoming Eleanor responses.
  • Improved Companion provenance inspector labeling for keyboard and screen-reader users.

Report an accessibility issue

If something blocks you from using 121 Collaborative, please contact us at accessibility@121collaborative.ai. Include the page URL, what you were trying to do, your browser or device, and any assistive technology you use if you are comfortable sharing it.

You can also use the site feedback control or visit Feedback. We will treat accessibility reports as product-quality issues and track fixes through the public changelogwhen they ship.