Accessibility at Pulseware

Last updated: 27 May 2026

Pulseware wants to be the survey maker that respects every respondent's time — including the time of respondents using screen readers, keyboard-only navigation, or assistive tech. This page describes our accessibility commitments and what we have, and don't yet have, in place.

§1 Our target

WCAG 2.2 Level AA. We aim to meet AA on every public marketing page, the survey builder, and the public survey runner that respondents use. The internal dashboard is a secondary priority but moving toward AA as well.

§2 What works today

• Keyboard navigation across the builder and runner
• Visible focus rings
• Screen-reader labels on all interactive controls
• Touch targets at least 44×44 px on mobile
• Sufficient text contrast (AA-rated) for body copy and CTAs
• Skip-to-content link in the marketing site header (planned)

§3 What we're still working on

• Full screen-reader QA on every question type
• ARIA live-region announcements for response submission
• High-contrast theme preset
• Reduced-motion preference respected on the marketing site (mostly done)

§4 What survey creators can do

Pulseware doesn't make every survey accessible automatically — your survey is only as accessible as you build it. We provide: clear labels on every question type, alternative text on logo uploads, and warnings when your custom theme drops below AA contrast. Use them.

§5 Reporting an issue

If you hit an accessibility barrier on any Pulseware page — public or in-product — tell us via the in-product feedback channel marked ACCESSIBILITY. We treat these as priority and acknowledge within 2 business days.

§6 Status

This page is a public commitment, not a certification. Pulseware does not hold a formal WCAG audit at launch. We will publish audit results when we have them.