Guides
Accessibility conformance report
Ridgetop in-app guides and surveys, against the Web Content Accessibility Guidelines (WCAG) 2.2, levels A and AA, in the format of a VPAT 2.5 WCAG edition. Report date: 2026-10-15.
What it covers
The Ridgetop guide runtime: the modals, tours, tooltips, banners, slideouts, hotspots, in-app surveys and checklist launchers that the Ridgetop snippet shows inside a customer's product. Checklists, posts and the resource center open in the Ridgetop Messenger, and the Ridgetop app where people build guides is separate; neither is covered by this report.
Guides are written by Ridgetop's customers. The runtime enforces what it can (images and animations need alt text before a guide is saved, and the designer shows contrast for every color pair and can block publishing when it fails), but the words, colors, images and videos a customer chooses also decide whether a guide conforms. So does anything a customer builds with custom HTML or JavaScript blocks (Enterprise), which this report can't assess.
How it was evaluated
- Automated checks with axe-core 4.13 (rules tagged WCAG 2.0, 2.1 and 2.2 A and AA) against the production runtime bundle, rendering a modal, a multi-step tour with a tooltip, a slideout, a banner, a hotspot and an NPS survey in Chromium. No violations were found inside the guides; color contrast, names, roles, ARIA attributes and target size were evaluated and passed with the default theme.
- Scripted keyboard checks: focus moves into modals and tooltips and stays there on Tab, Escape closes every dismissible guide when focus is inside it, and focus returns to where it was when a modal closes.
- Layout checks at 320 CSS pixels wide (equivalent to 400% zoom on a 1280 pixel window): no guide causes horizontal scrolling.
- Code review of the runtime for roles, names, focus handling, reduced motion, language and status messages.
- Not yet done: testing with screen readers (JAWS, NVDA, VoiceOver, TalkBack) by people who use them, and a third-party audit. Ratings that depend on them say so.
Summary
Of 55 success criteria: 33 supported, 9 partially supported, 0 not supported and 13 not applicable.
| Criterion | Level | Conformance | Remarks |
|---|---|---|---|
| 1.1.1 Non-text Content | A | Supports | Images and animations can't be saved without alt text. Videos carry their title as their name, the hotspot beacon is labelled, and decorative icons are hidden from assistive technology. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Partially supports | The runtime plays videos authors add from YouTube, Vimeo, Loom or a file. Alternatives for that media come from the author; the runtime doesn't check for them. |
| 1.2.2 Captions (Prerecorded) | A | Partially supports | Captions come from the video host or file the author chose. Hosted players show their own captions controls. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Partially supports | Depends on the author's video and the text around it. |
| 1.2.4 Captions (Live) | AA | Not applicable | Guides don't show live media. |
| 1.2.5 Audio Description (Prerecorded) | AA | Partially supports | Depends on the author's video. |
| 1.3.1 Info and Relationships | A | Supports | Headings are heading elements, guides are dialogs or labelled regions, survey questions are fieldsets with legends, scales are radio groups, and form fields are labelled by their questions. |
| 1.3.2 Meaningful Sequence | A | Supports | Reading order follows the step's rows and columns, which is also the visual order. Columns stack in the same order on small screens. |
| 1.3.3 Sensory Characteristics | A | Supports | Runtime instructions don't rely on shape, position or sound. Authors' text may refer to what's on screen. |
| 1.3.4 Orientation | AA | Supports | Guides adapt to the screen in either orientation; none locks it. |
| 1.3.5 Identify Input Purpose | AA | Not applicable | The runtime doesn't ask people for their own details; survey answers are opinions, not personal information with an input purpose. |
| 1.4.1 Use of Color | A | Supports | A chosen answer is marked with aria-checked as well as a filled background, and the checklist launcher states its progress in text. |
| 1.4.2 Audio Control | A | Supports | Videos show a poster and play only when the person chooses to. |
| 1.4.3 Contrast (Minimum) | AA | Partially supports | The default themes pass. Authors can choose any colors; the designer shows each pair's contrast ratio and warns when it fails, and a workspace can make that a block on publishing. |
| 1.4.4 Resize Text | AA | Supports | Guides scale with browser zoom and reflow rather than clipping. |
| 1.4.5 Images of Text | AA | Supports | The runtime renders text as text. Authors could add an image that contains text. |
| 1.4.10 Reflow | AA | Supports | Checked at 320 CSS pixels: modals become full-width sheets, tooltips without room dock as cards, and no guide scrolls sideways. |
| 1.4.11 Non-text Contrast | AA | Partially supports | Focus outlines are a 2 pixel blue line. The contrast of borders and control edges against each customer's page hasn't been measured, and authors choose button and border colors. |
| 1.4.12 Text Spacing | AA | Partially supports | Guide panels grow with their content rather than fixing heights, but this hasn't been tested with text-spacing overrides applied. |
| 1.4.13 Content on Hover or Focus | AA | Supports | Guide steps don't appear on hover. A hotspot opens on click or Enter, stays until dismissed, and closes with Escape. |
| 2.1.1 Keyboard | A | Supports | Every control is a native button, link or input. Ranking questions move items with buttons rather than dragging. |
| 2.1.2 No Keyboard Trap | A | Supports | Focus stays inside a modal on purpose and leaves when it closes, by its buttons or Escape. A guide the author makes impossible to dismiss still advances with its buttons. |
| 2.1.4 Character Key Shortcuts | A | Not applicable | The runtime has no single-character shortcuts. |
| 2.2.1 Timing Adjustable | A | Supports | Steps never advance on a timer; they wait for the person. |
| 2.2.2 Pause, Stop, Hide | A | Partially supports | Hotspot pulses and looping Lottie animations stop when the person's system asks for reduced motion, but there's no on-screen pause control for them. |
| 2.3.1 Three Flashes or Below Threshold | A | Supports | The runtime doesn't flash. Authors' videos and animations are their own. |
| 2.4.1 Bypass Blocks | A | Not applicable | Applies to pages; guides are components inside the customer's page. |
| 2.4.2 Page Titled | A | Not applicable | Applies to pages. |
| 2.4.3 Focus Order | A | Supports | Modals and tooltips take focus and give it back when they close. Banners, slideouts and surveys follow the page in focus order and are announced when they appear; embedded guides sit where they're placed. |
| 2.4.4 Link Purpose (In Context) | A | Supports | Runtime controls are named. Link and button text is the author's. |
| 2.4.5 Multiple Ways | AA | Not applicable | Applies to sets of pages. |
| 2.4.6 Headings and Labels | AA | Supports | Each guide is named by its heading, or by its step name when it has none. |
| 2.4.7 Focus Visible | AA | Supports | Buttons, answers, inputs and the beacon show a 2 pixel focus outline. |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Partially supports | Banners push the page down, and steps keep clear of fixed headers, the Messenger launcher and cookie banners. A slideout or tooltip can still cover part of a page element that has focus. |
| 2.5.1 Pointer Gestures | A | Supports | Everything works with a single tap or click. |
| 2.5.2 Pointer Cancellation | A | Supports | Actions run on click, which completes on release. |
| 2.5.3 Label in Name | A | Supports | Buttons are named by their visible text. |
| 2.5.4 Motion Actuation | A | Not applicable | Nothing responds to device motion. |
| 2.5.7 Dragging Movements | AA | Supports | Ranking questions reorder with up and down buttons; nothing requires dragging. |
| 2.5.8 Target Size (Minimum) | AA | Supports | Runtime controls meet 24 by 24 CSS pixels (axe-core target-size passed). |
| 3.1.1 Language of Page | A | Not applicable | The page's language is the customer's. |
| 3.1.2 Language of Parts | AA | Supports | A translated guide is marked with the language it's shown in, and right-to-left languages with their direction. |
| 3.2.1 On Focus | A | Supports | Focusing a control never changes the step. |
| 3.2.2 On Input | A | Supports | Choosing an answer selects it; the person moves on with Next or Submit. |
| 3.2.3 Consistent Navigation | AA | Not applicable | Applies to sets of pages. |
| 3.2.4 Consistent Identification | AA | Supports | Close, Next, Back, Skip and Submit behave and are named the same way in every guide. |
| 3.2.6 Consistent Help | A | Not applicable | Applies to sets of pages. |
| 3.3.1 Error Identification | A | Supports | A required question keeps Next unavailable until it's answered, so no error state arises. |
| 3.3.2 Labels or Instructions | A | Supports | Every question and field is labelled by its prompt. |
| 3.3.3 Error Suggestion | AA | Not applicable | Answers aren't validated in ways that produce errors. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Not applicable | Guides don't take legal or financial commitments. |
| 3.3.7 Redundant Entry | A | Supports | Surveys never ask for the same information twice in one response. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Not applicable | Guides don't sign people in. |
| 4.1.2 Name, Role, Value | A | Supports | Dialogs, regions, radio groups and radios expose their names, roles and states (axe-core ARIA rules passed). Screen reader testing is still to be done. |
| 4.1.3 Status Messages | AA | Supports | A banner, slideout or survey that appears without taking focus is announced through a polite live region with its heading or question. |
To report an accessibility problem in a guide, contact the company whose product shows it. Customers can reach Ridgetop support from the app.