Contact Form Accessibility Checker
Contact forms are the primary communication channel for many websites. Scan yours for accessibility barriers that prevent people with disabilities from reaching you.
No signup required. Results in under 60 seconds.
Why Contact Form Accessibility Matters
Contact forms are one of the most common interactive elements on the web and one of the most frequently cited in accessibility complaints. If someone cannot fill out your contact form, they literally cannot contact you to report accessibility issues — creating a frustrating catch-22 that regulators and courts take seriously.
Form accessibility failures are easy for automated tools to detect and for plaintiffs to document, making them a prime target in ADA lawsuits. In 2024, over 35% of ADA demand letters cited inaccessible forms as a primary violation. With the European Accessibility Act and ADA Title II deadline of April 24, 2026 in effect, every contact form on every website must be accessible to users with visual, motor, cognitive, and auditory disabilities.
Common Contact Form Accessibility Issues
Contact forms combine text inputs, textareas, select dropdowns, checkboxes, and submit buttons — each with specific WCAG requirements. CompliScan detects these issues across form implementations:
- Placeholder-only labels — using placeholder text instead of
<label>elements. Placeholders disappear on focus, leaving screen reader users and people with cognitive disabilities without context for what to enter. - Missing error identification — form validation that highlights fields visually (red borders) without providing programmatic error descriptions via
aria-describedbyor inline error text associated with the field. - Inaccessible CAPTCHA — image-based CAPTCHAs that have no audio alternative, and reCAPTCHA implementations that require precise mouse interaction. CAPTCHA is the single most-complained-about accessibility barrier on forms.
- Custom-styled form controls — CSS-hidden native checkboxes and radio buttons replaced with
<div>elements that lackrole,aria-checked, and keyboard toggle support.
How to Fix Contact Form Accessibility
Run a free CompliScan scan on the page containing your contact form. The scanner evaluates the form's HTML structure, label associations, ARIA attributes, and keyboard operability.
For labels, ensure every form control has a <label> element with a for attribute matching the input's id. Visual labels are preferred; use sr-only (or visually-hidden) only when a visible label would be redundant with surrounding context. For errors, add aria-invalid="true" to invalid fields, link error messages with aria-describedby, and provide an error summary at the top of the form using role="alert".
For CAPTCHA, switch to reCAPTCHA v3 (invisible) or hCaptcha's accessibility cookie, which provides a CAPTCHA-free experience for assistive technology users. CompliScan's Shield plan ($49/mo) monitors your forms weekly for accessibility regressions after plugin updates.
WCAG Requirements for Web Forms
WCAG 2.1 AA includes multiple success criteria directly applicable to forms: 1.3.1 Info and Relationships (labels and field grouping), 1.3.5 Identify Input Purpose (autocomplete attributes), 3.3.1 Error Identification (what went wrong), 3.3.2 Labels or Instructions (clear guidance), and 3.3.3 Error Suggestion (how to fix errors).
The ADA Title II April 2026 deadline and European Accessibility Act both reference WCAG 2.1 AA, making these form requirements legally binding. Courts have consistently ruled that inaccessible forms constitute a denial of access to services.
Automated tools detect approximately 30-40% of WCAG form-related criteria. CompliScan specifically checks for missing labels, empty form controls, ARIA attribute validity, and contrast on form elements. Manual testing is needed to verify error flow, focus order, and the usability of complex form interactions.
Frequently Asked Questions
Are placeholder attributes enough for form accessibility?
No. Placeholders are not labels. They disappear when the user starts typing, leaving no visible indication of what the field requires. Screen readers may not announce placeholder text. Always use a label element with a for attribute matching the input's id.
Is reCAPTCHA accessible?
reCAPTCHA v2 (checkbox) has an audio alternative but is still challenging for many users with disabilities. reCAPTCHA v3 (invisible, score-based) is the most accessible option as it requires no user interaction. If you must use v2, ensure the audio challenge works with screen readers.
How should form validation errors be announced?
Errors should be announced in three ways: an error summary at the top of the form (using role='alert' or aria-live='assertive'), inline error messages linked to fields via aria-describedby, and aria-invalid='true' on the invalid field. Move focus to the error summary on submit.
Do required field indicators need to be accessible?
Yes. A red asterisk alone is not sufficient — it conveys requirement through color only. Add 'Required' text (can be sr-only), use aria-required='true' on the input, and include a note at the top of the form explaining that asterisks indicate required fields.
Can CompliScan test form error states?
CompliScan scans the form as rendered on the page, checking label associations, ARIA attributes, and contrast. For error state testing, submit the form with invalid data first, then scan the page showing errors. The Shield plan provides ongoing monitoring that catches form structure issues automatically.
More Free Tools
Check Your Website Now
Enter your URL below and get a free accessibility report with AI-powered fix suggestions in under 60 seconds.
No signup required. Results in under 60 seconds.