Form Accessibility Checker

Paste form HTML to audit labels, ARIA attributes, autocomplete, fieldsets, and error patterns. Click an example below or paste your own code.

πŸ“‹ Load example form with issues β†’ Click to populate the editor with a sample form containing common accessibility problems.

Frequently Asked Questions

What form accessibility issues does this check?

This tool checks for: missing labels on inputs, missing fieldset/legend on radio and checkbox groups, placeholder used as the only label, missing autocomplete on common fields, buttons without accessible names, missing form landmarks, required fields without ARIA indication, and inputs without proper type attributes.

Why is placeholder not a sufficient label?

Placeholder text disappears when the user starts typing, so they lose context about what the field is for. It also has poor color contrast by default. Screen readers may or may not announce placeholder text depending on the browser. Always use a visible <label> element associated via the for attribute.

When should I use fieldset and legend?

Use <fieldset> and <legend> to group related form controls, especially radio buttons and checkboxes that share a common question. The legend provides a label for the entire group, which screen readers announce when users navigate into the fieldset.

What is the autocomplete attribute for?

The autocomplete attribute (WCAG 1.3.5) helps browsers and assistive technologies identify the purpose of common form fields like name, email, address, and phone. It enables auto-fill and helps users with cognitive disabilities complete forms faster.

Is my data stored?

No. Everything runs in your browser. Nothing is sent to any server.