The Drupal Accessible Forms Module for Permit, Records, and Contact Requests
A keyboard user tabs into a form field, gets no visible focus indicator, submits it wrong, and the error appears in red text a screen reader never announces. Accessible Forms hardens your Webform and Form API markup across the whole chain: labels, focus, error identification, and live-region announcements.
Government Forms Carry the Most Legal Risk on the Whole Site. Many Are Built Wrong.
Permit applications, records requests, and contact forms are where residents most need to complete a task, and where inaccessible fields cause the most friction. Placeholder text used as a label, color-only error indication, and unlabeled required-field asterisks show up even on sites built with Webform, which is otherwise one of the better-behaved form systems in any CMS.
This module installs on any Drupal 10.6+ or Drupal 11 site with Composer, and pairs with WPPersona's WCAG 2.1 AA compliance approach. No CMS migration required.
3.3.1
WCAG success criterion requiring every form error to be identified in text, not color alone
What Accessible Forms Actually Checks
Every feature below maps to a specific WCAG 2.1 success criterion, not a vague accessibility claim. Here's exactly what changes on your Drupal site.
Programmatic label association
Every element gets a real label tied to its input, so a screen reader announces the field’s purpose instead of silence or a guessed placeholder, including composite Webform elements.
Announced inline errors
Validation errors render in text next to the field and are pushed through an ARIA live region, so a screen reader user hears what went wrong without hunting the error summary.
Error prevention on legal and financial fields
Webforms involving payments, legal commitments, or permit submissions get a review step before final submit, matching the WCAG requirement for reversible or reviewable actions.
Full keyboard operability
Every field, checkbox, date element, and multi-step wizard control works with Tab, Shift+Tab, and Enter alone, with no mouse-only interaction anywhere in the flow.
Required indication beyond color
Required fields carry the word required in text in addition to any visual marker, and the requirement is announced programmatically to assistive technology.
From composer require to Fixed, in Four Steps
Point it at your forms
The module hooks into Webform and Form API rendering, so existing forms are hardened in place without rebuilding them from scratch.
Test the keyboard path
A keyboard-only preview mode lets you tab through an entire form exactly as a keyboard user would, before it goes live.
Configure error and review behavior
Set which forms need a review step and customize the error text that gets announced to screen readers, all stored in config.
Publish and monitor submissions
A report flags any form where users abandon at a specific field repeatedly, often a sign an accessibility issue is still slipping through.
“A resident using a screen reader had been unable to submit a records request Webform for over a year. We didn’t know until she called. That call doesn’t happen anymore.”
City Clerk, Small City Government
Common Questions About Accessible Forms
Does this replace Webform?
No. It works with Webform and the core Form API, adjusting the rendered markup and behavior to fix label association, error announcement, and keyboard operability. You keep building forms the way you already do.
What does WCAG require for form error messages specifically?
WCAG 3.3.1 requires that an error be identified and described to the user in text. 3.3.3 requires a suggestion for fixing it when known. Color alone, like a red border with no text, does not meet either criterion.
Can residents using a screen reader complete a multi-step Webform wizard?
Yes. Wizard pages announce the current step number and total steps, and focus moves to the top of each new step automatically, so a screen reader user always knows where they are in the process.
Get Accessible Forms on Your Drupal Site
There's no self-serve checkout yet. Submit the form and our team confirms your license tier, sends pricing, and gives you private Composer repository access with installation instructions within 1 business day.
- Drupal 10.6+ or Drupal 11, PHP 8.1+, integrates with Webform and the core Form API
- License covers updates and support for 12 months
Need more than one? See the full Accessibility Suite bundle.
Request to Purchase
Tell us which modules you need. We'll send licensing and setup details.
Pairs Well With
Looking for the deeper compliance picture? Read how these modules fit into WCAG 2.1 AA compliance for government websites, or browse our accessibility resources hub for guides on ADA Title II deadlines.
See Your Agency's PDF Risk in 2 Minutes
Enter your government website URL. We crawl every page, scan every PDF, and deliver a full ADA compliance risk report. No account. No credit card.
Run Free AuditTalk to Someone Who Speaks Government
Our team understands government procurement, ADA compliance timelines, and what it takes to migrate a government website. Free 20-minute demo. No hard sell.
- Full platform walkthrough for your agency type
- Answers to procurement and security questions
- Honest timeline and migration assessment