Accessibility and inclusion

Decision practice only works if everyone can actually use it. Accessibility is a design input, not a retrofit.

What we build for

  • Semantic structure with keyboard navigation and visible focus states throughout.
  • Readable typography, generous spacing, and color contrast that meets WCAG-minded targets.
  • Meaning never carried by color alone; scenario states are always labeled in text.
  • Plain-language writing. Animated pathway introductions ship with a full text transcript, play/pause controls, and a static reduced-motion version.
  • Responsive layouts for phones, tablets, Chromebooks, and desktops.

Inclusion commitments

Scenarios welcome families of every structure, including divorced, separated, never-married, blended, kinship, and guardian households, and never treat one structure as the default. Communication style, dialect, disability, and neurodivergence are never treated as risk or misconduct.

Known limits and feedback

Accessibility work is ongoing. If something blocks you, tell us through the contact page and we will treat it as a defect, not a suggestion.