Platform Notes
Drupal Webform Accessibility
Drupal Webform is common on Drupal-based council sites. Here's what we've observed from auditing forms built with this module.
About Drupal Webform
Drupal Webform is an open-source module that enables form building, submission collection, and results analysis within Drupal. It's actively maintained and widely used by government agencies, councils, and enterprises worldwide.
Official Resources
- Webform Module – Official project page
- Issue Queue – Report bugs and request features
- Documentation – Official docs and guides
Support Open Source
Webform is free and open-source, maintained by the community. If you rely on it, consider supporting the project.
Donate or sponsor developmentAbout this guide
This guide is based on Drupal core accessibility guidance and recurring Webform accessibility issues raised in the Webform and Drupal issue queues.
What you'll learn
Where Webform is typically strong
Standard HTML patterns
Common issues we've observed
Based on real audits
How to audit Webform forms
URL and HTML upload methods
Recommendations for authors
Quick fixes and best practices
What Drupal Webform Typically Does Well
When built with care, Drupal Webforms can be very accessible because they are based on standard HTML form controls and progressive enhancement.
Key strengths
- Semantic HTML form structure
- Clear labels and help text patterns
- Semantic fieldset grouping
- Strong validation (when Inline Form Errors enabled)
Common Issues We've Observed
Based on audits of Drupal Webform implementations, we commonly see:
| Issue | Frequency* | Severity |
|---|---|---|
| Labels hidden without accessible name fallback | Common | High |
| Help text not programmatically linked | Common | Medium |
| Required fields rely on visual marker only ('*') | Common | High |
| Checkbox/radio groups missing fieldset/legend | Occasional | Medium |
| Generic error messages | Occasional | Medium |
| Missing input type hints (email, phone) | Occasional | Low |
| Autofill blocked or missing autocomplete tokens | Occasional | Medium |
| CAPTCHA with no accessible alternative | Occasional | High |
*Observed frequency based on audits reviewed by our team.
Important note
These issues are often caused by configuration choices, theming, or add-on widgets (like Select2/Chosen), not limitations of Drupal Webform itself.
How to Audit Drupal Webforms
Option 1: Audit by URL
Paste the form URL directly into auditmyform.com. Most Drupal Webforms render server-side and work well this way.
This is the fastest method for public forms.
Option 2: Audit by HTML Upload
Use this when the form is behind a login, on a staging site, or if 403 blocks automated requests.
- 1Open form in browser and login if needed
- 2Navigate to the form step you want to audit
- 3Right-click → "Save As" (HTML Only)
- 4Upload the HTML file to auditmyform.com
Multi-step forms
If your Webform uses a wizard (multiple pages), audit each step separately. Issues often appear on later steps where conditional logic and validation rules kick in.
Recommendations for Form Authors
Add clear field descriptions
Explain what information is needed and in what format.
Mark fields as required properly
Use the required attribute, not just visual indicators.
Use specific input types
Email, phone, and date inputs provide better mobile keyboard hints.
Customise error messages
Make error messages specific and actionable, not generic.
For Site Builders
Site builder toggles to check first
- Inline Form Errors module enabled
- Required indicator explanation present
- Autocomplete token support enabled
- Prefer Honeypot over CAPTCHA
- Avoid Select2/Chosen unless tested
- Theme preserves core form patterns