Skip to main content

Accessibility and compliance

How Walnut helps teams build accessible demos, playlists and deal rooms: styling control, keyboard navigation, narration, translations and mobile views.

Updated Nov 16, 2026

Accessibility and compliance

Overview​

Walnut gives your team full control over every visual and interactive element of the buyer experience. That means you can build demos, playlists and deal rooms to your organization's accessibility standards.

This guide covers the controls Walnut provides, how each one supports accessible experiences, and a checklist to use when you build or review a demo.


Full control over styling​

Every color, font, size and button your viewers see can be set to your standards.

Brand themes. A theme sets colors, fonts, buttons, dim intensity and interactions in one place. Apply it to your templates and demos so every experience follows the same accessible palette, and update it once to change every demo that uses it. Playlists and deal rooms can apply a theme too. See Brand themes.

Text size and contrast. Set text size, text color and background color in guides and on captured content. Use these controls to align text size and color contrast with WCAG AA or AAA contrast guidance. See Edit the background color of any element.

Button styles. Mark the main action on a guide step as Primary (filled) and the others as Secondary (outlined), so viewers can tell at a glance which button moves them forward. See Make a guide button Primary or Secondary.

Global CSS for captured screens. In Template Settings > Custom Code > Global CSS, apply styling to all captured HTML in a template. Common uses:

  • Larger base font sizes and line height
  • Higher contrast for text, buttons and links
  • Stronger visible focus states for interactive elements
  • Clearer spacing and layout

Captured text and heading structure. Edit captured text and adjust headings and text structure with Walnut's HTML and text editors, without recapturing. See Editing captured content.

Global Edits. Make a change once and apply it to matching elements across the whole template, including screens you add later. See Apply global edits.


Multiple ways to consume content​

Keyboard navigation. In linear guided demos, viewers can move forward and back through steps with the keyboard (for example, the arrow keys).

Text-to-Speech narration. Generate spoken audio for guide steps, so instructions can be heard as well as read. Translated guides can be narrated too, in supported languages, so viewers hear the language they are reading. See Add text-to-speech audio to guide steps.


Multilingual​


Semantics preserved​

The Walnut Chrome Extension keeps your application's HTML semantics, including structural markup and ARIA attributes, exactly as they were at the time of capture. The accessibility work your product team has already done carries into your demos.


Any device​

  • Mobile view: turn on View On Mobile for a mobile-optimized experience on phones and tablets. See Mobile-friendly demos.
  • Display modes: choose Dynamic Size, Proportional Fit, Fixed Width or Fixed Size to control how screens scale on each device. See Screen display settings.
  • Preset screen sizes: capture with the Chrome Extension's device presets so screens match real viewing conditions.

Admin experience​

Walnut users can choose Light, Dark or System appearance for the Walnut app. This is a personal setting for each Walnut user. It does not change your demos or anything your viewers see. See Dark mode.


Accessibility optimization checklist​

Use this list when you build or review a demo.

Start from an accessible source

  • Review key flows in your application with a screen reader and keyboard-only navigation before you capture.

Style for readability

  • Apply a brand theme with accessible colors and fonts.
  • Use Global CSS to raise base font sizes, improve contrast and strengthen focus states.
  • Check guide text and buttons against WCAG AA/AAA contrast ratios.

Write clear guides

  • Keep guide text short and simple.
  • Use linear guided demos where you can, and test forward and back keyboard navigation.
  • Add Text-to-Speech to critical steps and make sure the audio controls are easy to find.

Reach every audience

  • Add guide and screen text translations for your core languages, and spot-check them.
  • Set a default language for regional audiences.

Check every device

  • Turn on View On Mobile and pick a display mode that keeps text legible without zooming.
  • Test on phones and tablets in portrait and landscape.

Test before you share

  • Preview in at least two browsers, such as Chrome and Edge.
  • Test keyboard navigation from start to finish and spot-check with a screen reader.

Accessibility scope​

Captured screens inherit the accessibility of the source application, and Walnut preserves it as captured. Text inside static images and videos is not exposed to screen readers, so we recommend using captured HTML or adding guide text for that content. As with any embedded experience, behavior can vary by browser and assistive technology, so we recommend including your demos in your standard accessibility review.

Was this helpful?