Accessibility at PulseFormCreator

Last updated: 23 September 2026

People fill in PulseFormCreator forms with screen readers, keyboard-only navigation and other assistive technology. Here is what we aim for, what is in place and what is not yet.

1. Our target

WCAG 2.2 Level AA. We aim to meet AA on every public page of this website, the form editor, and the forms respondents fill in. The dashboard is a lower priority, but it is moving toward AA as well.

2. What is in place

A “Skip to content” link is the first thing you can tab to on every page of this website and the dashboard.
The editor and the forms work with a keyboard, and controls show a visible focus ring.
The site menu’s links and a form’s own buttons are at least 44 px tall.
Text, links and buttons on this website meet the WCAG AA contrast ratio of 4.5:1.
Forms keep their text readable on any theme: buttons and hints use text that stands out against your colors, and the colors you picked are never changed.
Name, email, phone, address and website questions tell the browser what they ask for, so people can fill them in automatically.
Grid questions use standard radio buttons and checkboxes, labeled with their row and column. On a narrow screen each row becomes its own card, so nothing scrolls sideways.
This website and the forms follow your device’s “reduce motion” setting.

3. Known limitations

These are the gaps we know about. We have not yet tested every question type with a screen reader.

Signature. Drawing needs a mouse, a finger or a stylus. Anyone can choose “Type instead” and sign by typing their name.
Ranking. Dragging needs a pointer. With a keyboard, use the up and down buttons on each item, or the Up and Down arrow keys on a focused item. Each move is announced to screen readers.
File upload. Dropping a file onto the form needs a mouse. The upload area also opens with Enter or Space, and each file’s progress is announced.
Grids. A grid that takes several answers per row, or text in every cell, has one stop per cell when you move with the Tab key, so a big grid takes a while.
Logos. A form’s logo is treated as decoration, so screen readers skip it. If your organization’s name matters, put it in the form’s title or description.
Videos and embeds. Captions and player controls for YouTube, Vimeo and Loom videos, and the content of an embed block, come from those services.
Language. The words a form itself shows respondents, such as its buttons and error messages, are in English only.

4. Tips for form creators

PulseFormCreator can’t make every form accessible by itself: a form is as accessible as the questions in it. Five things help most:

Describe every image. Image blocks have an Alt text field, and each picture in a picture choice has a description. The editor warns you when a picture has neither a label nor a description, because a screen reader would only read out its number.
Use the matching question type. Name, Email, Phone, Address and Website questions let browsers fill in the answer. A short-text box can’t.
Write links that say where they go. In a paragraph, “Read our privacy policy” tells a screen-reader user more than “click here”.
Pick an accent color with strong contrast. The form chooses readable button text for you, but a mid-tone accent can fall short of 4.5:1 whatever text sits on it, and nothing can fix text over a busy background image.
Try it with the keyboard. Open Preview (the eye icon in the editor) and press Tab through your form before you share it.

How to create a form walks through every step of building one.

5. Reporting an issue

If you hit an accessibility barrier on any PulseFormCreator page, public or in the product, tell us with the accessibility form on the contact page. You don't need to sign in. We treat these as a priority and aim to acknowledge them within 2 business days.

6. Audit status

This page is a public commitment, not a certification. PulseFormCreator has not had a formal WCAG audit yet. We will publish the results when it has.