Accessibility

Learning should work for everyone.

Upsoma aims to meet WCAG 2.2 AA across core learner, support, account, and marketing experiences.

Current commitments

Accessibility is treated as a product requirement, not a final QA pass. These are the standards each core flow should satisfy.

  • Keyboard first

    Primary navigation, drawers, forms, tabs, feedback, and learning controls must be reachable and visible on focus.

  • Readable contrast

    Text, chart labels, status pills, focus rings, and disabled states should meet WCAG 2.2 AA contrast expectations.

  • Responsive by default

    Learner, support, account, and marketing flows must preserve labels, hierarchy, and actions across mobile and desktop.

  • Motion with restraint

    Decorative motion should stop when a user requests reduced motion, while state changes remain understandable.

Support

Accessibility support

Include the page, assistive technology, browser, device, and what blocked you. Upsoma should treat access problems as product bugs, not user preferences.