Best Plugins for Accessible Forms in WordPress (2026)

Forms fail accessibility more reliably than any other component on a WordPress site, and the reason is structural rather than careless. A form has labels, states, errors, and focus behaviour that all have to work together, and it is the one component where getting it wrong stops someone completing a task rather than merely inconveniencing them.

One plugin here has treated this as a first-class concern for years: Gravity Forms has been built to meet WCAG 2.1 AA since version 2.5, with proper ARIA labels, keyboard navigation, screen reader compatibility, and focus management. That is a specific, verifiable commitment rather than a marketing claim, and it is the main reason it appears first. This article compares the plugins on accessibility output rather than feature count, and covers the CAPTCHA problem that WCAG 2.2 has now made explicit.

Verified August 2026. Related: our WCAG 2.2 guide covers Accessible Authentication in more detail.

The five ways forms fail

Placeholder text instead of labels. Visually tidy and functionally broken: the placeholder disappears when typing begins, so anyone who loses their place has no way to recover what the field wanted. Screen reader support for placeholders is also inconsistent.
Errors that are not announced. A red border and a message rendered below the field tells a sighted user what happened and tells a screen reader user nothing. Errors need a live region and focus should move to the first problem.
Required fields marked only with colour. A red asterisk with no text equivalent communicates nothing to someone who cannot see it or cannot distinguish the colour.
Fieldsets missing on grouped controls. Radio buttons and checkbox groups need a fieldset and legend, or the question they answer is never announced. This is the most common silent failure.
Multi-step forms that lose focus. Moving to step two without moving focus leaves keyboard users at the top of a page they have already read, or worse, nowhere identifiable at all.

The 6 plugins compared

1. Gravity Forms

The pick where accessibility is a requirement rather than a preference, because it is the one plugin here with a stated, sustained commitment. Since version 2.5 it has been built to meet WCAG 2.1 AA, covering ARIA labelling, keyboard navigation, screen reader compatibility, and focus management as design properties rather than as options you configure.

Pricing starts at $59 a year for the Basic licence and rises to around $259 a year, with many capabilities delivered through add-ons that sit above the base tier. That add-on model is the main criticism: the headline price is rarely the price you pay once payments, conditional logic extensions, or CRM connections are involved. For a public body, a university, or any organisation where an inaccessible form is a legal problem rather than an embarrassment, that premium is straightforward to justify.

Pricing: From $59 a year, up to around $259, plus add-ons
Accessibility: Built to WCAG 2.1 AA since version 2.5
Best for: Organisations where compliance is non-negotiable
Watch out for: Add-on costs above the base licence

2. Fluent Forms

The best value in the category and the strongest all-rounder for most WordPress sites, at $79 a year or $299 once for a lifetime licence, with conditional logic included free rather than sold as an extension. Against Gravity Forms plus add-ons, the total cost of ownership difference is substantial.

Its accessibility position is less explicitly documented than Gravity Forms’, which is the honest caveat rather than a criticism of the output. The practical approach is to build your form, then test it: tab through every field, submit it empty to see how errors behave, and check that grouped controls announce their question. Most of what determines a form’s accessibility is how you configure it, and a well-built Fluent Forms form will outperform a carelessly built Gravity Forms one. The lifetime licence makes it particularly attractive for a site that will run for years.

Pricing: $79 a year, or $299 lifetime; conditional logic free
Accessibility: Less explicitly documented; test your build
Best for: Best all-round value, especially on the lifetime licence
Watch out for: Verify error announcement and fieldsets yourself

3. WPForms

The most approachable builder, with tiers at $49.50, $99.50, $199.50, and $299.50 a year. Its drag-and-drop interface is the easiest here for non-technical staff, which matters for accessibility in an indirect but real way: a form somebody understands is a form somebody can fix.

One commercial detail carries over from its payment handling and is worth restating, since forms are often used to collect money: below the Pro tier, WPForms adds a 3% platform fee on transactions on top of the payment processor’s charge. If your accessible form is also a donation or booking form, that pushes the realistic price to $199.50. On accessibility specifically it is competent rather than distinguished, and the same advice applies as to Fluent Forms: build it, then test it with a keyboard before you rely on it.

Pricing: $49.50 to $299.50 a year; 3% transaction fee below Pro
Accessibility: Competent; depends heavily on how you build
Best for: Non-technical teams who will maintain the form themselves
Watch out for: The 3% fee if the form takes payments

4. Formidable Forms

The data-heavy option, priced from around $199.50 for the first year, and distinguished by Views, which turn submissions into searchable directories, calculators, and front-end listings. Where a form is the front end of an application rather than a contact box, that capability has no real equivalent here.

For accessibility that power cuts both ways. Calculated fields updating live need to announce their changes or a screen reader user will not know the total moved, and front-end Views generate markup you should audit as carefully as any template. Neither is a reason to avoid it; both are reasons to test the finished thing rather than assume. Choose it when you need Views, and budget testing time proportionate to the complexity you are building.

Pricing: From around $199.50 the first year
Accessibility: Test live calculations and generated Views markup
Best for: Forms that power directories, calculators, and listings
Watch out for: Complexity increases your testing obligation

5. Contact Form 7 and Forminator

The free options, grouped because the accessibility advice is identical. Contact Form 7 gives you complete control of the markup, which means an experienced developer can produce a genuinely excellent accessible form and an inexperienced one can produce a disaster. Forminator, free from WPMU DEV, ships a builder with more structure and less rope.

Contact Form 7’s markup control is the interesting property here. Because you write the template, you can add fieldsets, associate error messages correctly, and control focus behaviour precisely, which none of the visual builders fully expose. For a developer building one important form, that is an advantage. For a marketing team building twenty, it is a liability. Both are free, so the cost of testing which suits your team is only time.

Pricing: Free
Accessibility: Entirely determined by how you build it
Best for: Developers who want markup control, or zero budget
Watch out for: Full control means full responsibility

6. Your spam protection

Listed as a component because it is the single most common accessibility barrier on an otherwise well-built form, and WCAG 2.2 has now made the problem explicit. The Accessible Authentication criterion says you must not require a cognitive function test, and a puzzle CAPTCHA is exactly that.

Identifying traffic lights, transcribing distorted text, or solving a puzzle are all cognitive tests, and they exclude people with a range of cognitive and visual disabilities while also annoying everyone else. The alternatives work well and mostly convert better: honeypot fields cost nothing and catch most automated submissions, timing checks reject anything completed implausibly fast, and invisible challenges such as Cloudflare Turnstile verify without asking the user to do anything. Akismet and CleanTalk filter server-side after submission with no user-facing barrier at all. If you change one thing after reading this, change your CAPTCHA.

Pricing: Free to modest, depending on the option
Accessibility: Puzzle CAPTCHAs fail WCAG 2.2 Accessible Authentication
Best for: Honeypots, timing checks, and invisible challenges
Watch out for: Third-party CAPTCHA is also a privacy processor

Comparison table

Plugin	Price	Stated WCAG commitment	Markup control	Best for
Gravity Forms	$59 to ~$259/yr plus add-ons	Yes, 2.1 AA since v2.5	Moderate	Compliance-critical organisations
Fluent Forms	$79/yr or $299 lifetime	Not explicitly documented	Moderate	Best overall value
WPForms	$49.50 to $299.50/yr	Not explicitly documented	Limited	Non-technical teams
Formidable Forms	From ~$199.50 first year	Not explicitly documented	Moderate	Directories and calculators
Contact Form 7	Free	You supply it	Complete	Developers
Forminator	Free	Not explicitly documented	Limited	Zero budget

Testing a form in ten minutes

Tab through it without touching the mouse. Can you reach every field, in a sensible order, and always see where you are? If focus disappears behind a sticky header, that is a WCAG 2.2 failure.
Submit it empty. Does focus move to the first error? Is the error text associated with its field, or floating nearby in a way only sight connects?
Check your radio and checkbox groups. Turn on a screen reader and tab into one. If you hear the option but never the question, the fieldset and legend are missing.
Zoom to 200%. Does the layout hold, or do labels detach from their fields?
Look for placeholder-only fields. Every field needs a visible persistent label. Placeholders are a supplement, never a replacement.
Try to submit with a password manager. If autofill is blocked or paste is disabled, you have an Accessible Authentication problem as well as an irritated user.

Related guides

Frequently asked questions

Which form plugin is most accessible?

Gravity Forms has the clearest stated commitment, having been built to WCAG 2.1 AA since version 2.5. In practice how you configure a form matters as much as which plugin renders it, so test the finished form regardless of what you chose.

Are placeholders really a problem?

Yes. They vanish when typing starts, screen reader support is inconsistent, and their contrast is usually poor. Use visible persistent labels and treat placeholders as optional extra hints.

Does reCAPTCHA fail WCAG?

A puzzle-based challenge requires a cognitive function test, which WCAG 2.2’s Accessible Authentication criterion addresses directly. Invisible challenges and honeypots avoid the problem and generally convert better.

How should multi-step forms handle focus?

Move focus to the new step’s heading when it appears, and announce the step change. Leaving focus where it was means keyboard and screen reader users do not know anything happened.

Do I need to avoid required-field asterisks?

Not at all, but the asterisk must not be the only signal. Mark the field required programmatically and explain the convention in text, so the requirement is conveyed by more than a red character.

Is a free plugin good enough?

For accessibility, yes, if built carefully. Contact Form 7 in the hands of someone who understands fieldsets and live regions produces excellent output. The paid plugins buy convenience and support, not inherently better markup.

The verdict

Where accessibility is a legal requirement: Gravity Forms from $59 a year. It is the only plugin here with a stated, sustained WCAG 2.1 AA commitment, and in procurement that documented position is worth as much as the output.

For most sites: Fluent Forms at $79 a year or $299 lifetime, with conditional logic included. Test the finished form yourself; that ten-minute check matters more than the badge on the vendor’s site.

On zero budget: Contact Form 7 if you have a developer, Forminator if you do not. Both can produce accessible forms, and neither will do it by accident.

And replace your puzzle CAPTCHA today. It is the most common accessibility barrier on otherwise decent forms, WCAG 2.2 addresses it explicitly, and honeypots plus an invisible challenge do the job better while annoying nobody.

ThemeAlley

Search

Recent Posts

Categories

Tag Cloud