Accessibility at PulseFormCreator
Last updated: 27 May 2026
People fill in PulseFormCreator forms and surveys with screen readers, keyboard-only navigation and other assistive technology. This page describes our accessibility target, what is in place and what is not.
§1 Our target
WCAG 2.2 Level AA. We aim to meet AA on every public marketing page, the form builder, and the public form that respondents fill in. The internal dashboard is a secondary priority but moving toward AA as well.
§2 Implemented
Verifiable today across the marketing site, builder, and runner:
- Skip-to-content link on every marketing and in-app page (first focusable element on the body)
- Keyboard navigation across the builder and runner
- Visible focus rings on interactive controls
- Touch targets at least 44×44 px on mobile
- Sufficient text contrast (AA-rated) for body copy and CTAs
§3 In progress
Work is underway on these. We will not list them as done until they are verified:
- Screen-reader labels on every interactive control (partial today; full QA pending)
- 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 form creators can do
PulseFormCreator cannot make every form accessible automatically. Your form is 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.
§5 Reporting an issue
If you hit an accessibility barrier on any PulseFormCreator 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. It is not a certification, and PulseFormCreator has not had a formal WCAG audit. We will publish audit results when we have them.