Test mode

Payments use Stripe test mode. No real payment is collected.

Build accessibility into your form.

Use visible labels, linked errors, keyboard controls and publication checks, then test the actual page in context.

How it works

Keep the basics present

The renderer connects questions with visible labels and instructions, groups choice controls and returns useful error guidance. The built-in themes protect focus visibility, control boundaries and target sizes.

  • A linked error summary leads back to the affected answer
  • Keyboard controls support the form and its choice groups
  • Text and button-label contrast checks use 4.5:1; control boundaries use 3:1

Review before replacing the live form

Publication reruns server checks and requires an author review of questions and instructions. Blocking results can be saved as draft work for correction without replacing the current public version.

  • Check narrow layouts, long labels and error states
  • Use a private keyboard test of current edits without creating entries or emails
  • Test current edits inside the intended page's actual WordPress theme

Keep a record of what was tested

The accessibility test record stores the form revision, tester and reported keyboard, screen-reader and zoom/layout results. Relevant changes can make an earlier record out of date.

  • Leave unperformed tests marked Not tested
  • Keep the browser, assistive technology and intended page in the record
  • Pro steps, conditions, answer comparisons and final review use the same core safeguards

Review an accessibility barrier report

A form intended to report a barrier needs a usable reporting path of its own.

  1. Check the wording

    Explain what happened and where, without requiring unnecessary personal information.

  2. Use the keyboard

    Move through controls, submit missing required answers and follow each linked error back to its question.

  3. Test the published page

    Repeat the checks with the real theme, magnification and the assistive technology available to your team. Record only tests you performed.

An example workflow. Configure and test it in your own WordPress site.

Free and Pro for this workflow

Feature reference: Free 1.4.0 and Pro 1.3.2. Check published downloads for the version you can install.

Included in Free

  • Visible labels, linked validation and keyboard behavior
  • Contrast checks and four built-in themes
  • Private previews, required author review and manual test records

With Pro

  • The same safeguards across advanced form behavior
  • Custom appearance subject to the core contrast checks
  • Polite announcements for conditional changes and an editable final review
See the complete comparison

Plan your setup

  • The plugin does not certify a form or an entire website as WCAG, Section 508 or legal compliance.
  • Your questions, theme, custom CSS and other plugins affect the final experience. Test on the intended page.
  • Private previews do not test actual email delivery, spam verification, saved progress or real attachments. Use a normal staging test for those.
Follow the practical guide

Common questions

Is accessibility a paid feature?

The core authoring, rendering and publication safeguards are included in Free. Pro extends that same foundation.

Does a saved test record prove compliance?

No. It records the checks a person reports for a particular revision and context. It is neither certification nor a substitute for a complete assessment.

Browse all questions