Accessibility Statement
Last updated July 2026
We want every respondent to be able to complete an assessment with confidence. Ascent is designed to meet WCAG 2.1 AA, and accessibility is part of how we build.
1.Standards
We target WCAG 2.1 AA across the respondent experience and the builder, and test with keyboard-only navigation and screen readers.
2.Keyboard & screen readers
Every question type — including sliders, rankings, and matrix grids — is operable by keyboard and exposes proper roles, labels, and states to assistive technology.
3.Contrast & motion
Color choices meet contrast requirements, and all motion respects the prefers-reduced-motion setting, disabling non-essential animation.
4.Alternative outputs
Reports are available as accessible web pages and as editable Word documents, so results can be consumed in the format that works best for each reader.
5.Compatibility
We test against current versions of major browsers on desktop and mobile, and with widely used screen readers including NVDA, JAWS, and VoiceOver.
6.Ongoing improvement
Accessibility is never finished. We audit new features before release, fold assistive-technology testing into our process, and treat reported barriers as priority fixes.
7.Feedback
Found a barrier? Email accessibility@ascent.app and we'll prioritize a fix. Your input directly improves the platform.