Skip to content

Form Accessibility Analyzer

Paste HTML containing forms to check for missing labels, autocomplete attributes, fieldset groups, error associations, and other accessibility issues.

FreeNo SignupNo Server UploadsZero Tracking

We fetch the page client-side. Some sites may block external access — use "Paste HTML" as a fallback.

Enter a URL or paste HTML above to analyze form accessibility.
Embed code
<iframe src="https://wcagkit.com/embed/form-analyzer" width="100%" height="600" frameborder="0" title="Form Accessibility Analyzer - wcagkit"></iframe>
<p style="font-size:12px;text-align:center;margin-top:4px;">
  <a href="https://wcagkit.com/tools/form-analyzer" target="_blank" rel="noopener">Powered by wcagkit</a>
</p>
Attribution preview

Powered by wcagkit

How to Use Form Accessibility Analyzer

  1. 1

    Paste your HTML

    Copy the HTML source code containing one or more forms and paste it into the input area.

  2. 2

    Click Analyze

    Press the Analyze button to parse all form elements and check them against WCAG criteria.

  3. 3

    Review form scores

    Each form receives an accessibility score based on the number and severity of issues found.

  4. 4

    Fix reported issues

    Address errors like missing labels and warnings like missing autocomplete attributes, then re-analyze.

Frequently Asked Questions

This tool checks for label association (for/id, aria-label, aria-labelledby, wrapping label), required field indicators, autocomplete attributes (WCAG 1.3.5), fieldset and legend for radio/checkbox groups, error message association (aria-describedby, aria-errormessage), input type appropriateness, and placeholder-only labels.

Screen readers rely on programmatic label associations to announce what each form field is for. Without a properly associated label, screen reader users hear only the input type (such as 'edit text') with no indication of what information to enter. This makes forms unusable for many assistive technology users.

The autocomplete attribute (WCAG 1.3.5, Identify Input Purpose) tells browsers what type of data a field expects, enabling autofill and input assistance. This helps users with cognitive disabilities, motor impairments, and anyone who benefits from reduced typing. Common values include name, email, tel, and street-address.

When multiple radio buttons or checkboxes share a group label (like 'Payment method'), wrapping them in a fieldset with a legend element creates a programmatic group label. Without this, screen readers announce each option individually without context about what the group represents.

No. All form analysis is performed entirely in your browser using JavaScript. Your HTML source code never leaves your device.

Related Tools

ARIA Validator

Validate ARIA attributes

Try it

Heading Analyzer

Check heading structure

Try it

Touch Target Checker

Check touch target sizes

Try it

Keyboard Trap Detector

Detect keyboard traps

Try it

Form Accessibility: The Most Critical Interaction Pattern

Forms are where users take action on the web: signing up, making purchases, submitting applications, and providing feedback. When forms are inaccessible, entire user journeys break down. Research shows that form-related accessibility issues are among the most commonly reported barriers by users with disabilities. This tool automates the detection of the most impactful form accessibility problems.

Label Association Methods

There are four valid ways to associate a label with a form control in HTML. The explicit label uses a for attribute matching the input's id. The wrapping label encloses the input inside a label element. The aria-label attribute provides an accessible name directly on the input. The aria-labelledby attribute references the id of another element containing the label text. Each method has appropriate use cases, but the explicit for/id association is generally preferred because it provides the largest click target and is most universally supported.

Common Form Accessibility Mistakes

Using placeholder text as the only label is the single most common form accessibility error. Placeholders disappear when users start typing, leaving no visible indication of what the field expects. Other frequent mistakes include failing to group related radio buttons or checkboxes with fieldset and legend elements, omitting the autocomplete attribute on personal data fields, using generic input types when semantic types like email or tel would provide better keyboard experiences, and not associating error messages with their corresponding inputs using aria-describedby.

WCAG Success Criteria for Forms

Multiple WCAG success criteria apply to forms. SC 1.3.1 (Info and Relationships) requires programmatic label associations. SC 1.3.5 (Identify Input Purpose) requires the autocomplete attribute. SC 3.3.1 (Error Identification) requires errors to be described in text. SC 3.3.2 (Labels or Instructions) requires labels or instructions for user input. SC 4.1.2 (Name, Role, Value) requires all UI components to have accessible names and roles. This tool checks for compliance with all of these criteria.