TechnSols
Advertisement

Accessible Form Tester

Test form accessibility online for free. Check labels, associations, and inline contrast fast, with no install and no sign-up.

Be the first to rate this tool

Paste an HTML form to test it.

What Is Accessible Form Tester?

Accessible Form Tester is a free online tool by TechnSols that reads pasted HTML form markup and checks every field for the things that make a form usable: a label, a real link between the label and the field, and colours with enough contrast. You paste the form, and the tool lists each field with its label status, flags the ones with no label, and warns about placeholder-only fields and missing fieldset legends. It is the fastest way to see whether a form works for everyone.

Advertisement

Forms are where accessibility fails most often, because a form is where a visitor must act, not just read. The WebAIM form guide explains that every form control needs a label that assistive technology can announce, and that the label must be tied to its field, not just placed near it. Large audits keep finding the same gap: a third of form inputs have no proper label at all.

The tester checks each input, select, and textarea for a label element with a matching for attribute, a wrapping label, an aria-labelledby reference, or an aria-label, and it flags fields that rely on placeholder text alone. If the markup is hard to read, the HTML Beautifier tool tidies it first, so each label is easier to trace back to your code.

People use it to check a checkout form before launch, to review a contact or registration form, and to show a developer exactly which fields are broken. It works on the HTML you paste, so it sees exactly the fields in that markup. It cannot test error messages that appear only after a failed submission, because those need the live form and its scripts.

How To Use Accessible Form Tester?

Here is how to test form accessibility online in three quick steps. Using Accessible Form Tester is simple. There is no software to install and no account to make. Paste the form, read the field list, and fix the flagged fields. If the markup is compressed, the HTML Minifier tool is the reverse step.

Step 1: Paste Your HTML Form

Copy the HTML of the form you want to test and paste it into the box. A whole form works, and so does a single fieldset or a single field group. The tester reads every input, select, and textarea in the markup, so nothing in the form is missed.

Step 2: Read The Field List

The tool lists each field with its label status: labelled, with the method that labels it, or no label, with a flag. It also lists fieldsets without a legend, and fields whose inline colours fail the AA contrast ratio. Read the list field by field, because one missing label can block a whole form.

Step 3: Fix The Flagged Fields

Give every flagged field a real label: a label element with a matching for attribute is the safest choice, and a wrapping label works too. Replace placeholder-only fields with labelled ones, and add a legend to every fieldset. Then paste the fixed form and test again. When the text is ready for a ticket, the HTML Entity Encoder tool encodes special characters so the report stays valid.

The whole job takes a few minutes for most forms. Test early, while the form is still easy to change, and test again after every fix, because one change to a label can affect the fields around it.

Why Accessible Form Tester?

A form with an unlabeled field is a locked door: a screen reader user hears edit text, with no name, and has no idea what to type. A sighted user reads the text beside the field, but that text is invisible to assistive technology unless it is tied to the field properly. This tester finds every unlocked door in one paste. The HTML to Markdown Converter tool turns the same markup into docs for the fix ticket.

The rule behind the test is one of the clearest in WCAG. The WCAG labels rule requires that labels or instructions are provided when content requires user input. This tester applies that rule to your form field by field, so the requirement becomes a list you can work through.

Placeholder Text Is Not A Label

Placeholder text disappears the moment a user starts typing, and many screen readers do not announce it as a label at all. A field with only a placeholder leaves a screen reader user guessing, and leaves a sighted user with no label once they type. The tester flags every placeholder-only field, so they get real labels.

A Label Must Be Tied To Its Field

Text sitting beside a field is not a label unless the markup connects them: a for attribute that matches the field id, a wrapping label element, or an aria reference. Without that link, assistive technology cannot tell which text belongs to which field, and a form with many fields becomes a guessing game. The tester checks the link, not just the text.

Groups Need Names Too

Radio buttons and checkboxes come in groups, and a group without a fieldset and legend has no name to announce. A screen reader user hears a list of options with no idea what they are choosing between. The tester flags every fieldset without a legend, so each group gets a name.

What Can You Do With Accessible Form Tester?

Form tests fit anywhere a form is built or reviewed. These are the jobs this tester handles best.

Check A Checkout Form Before Launch

Paste the finished checkout form and read the field list from the first field to the submit button. The Colour Contrast Checker tool checks the contrast of the form text and labels at the same time. A checkout with every field labelled is ready to take orders from everyone.

Review A Registration Or Contact Form

Registration and contact forms are often the first thing a visitor meets, and an unlabeled field there turns a new user away. Paste the form and fix the flagged fields in one pass. That is how a site stops losing signups to a markup mistake.

Show A Developer Which Fields Are Broken

A developer who cannot see the problem cannot fix it. Run the test, copy the field list, and send it with the ticket. The list names each field and the exact fault, so the fix is a markup change, not a long investigation. When the report needs a PDF copy, the Text to PDF tool turns the field list into a PDF.

Advertisement

Quality And Settings

The tester checks each field for all five ways a label can be tied to it, and it flags the three most common faults: no label, placeholder only, and a fieldset with no legend. The Character Counter tool counts the characters in the test report when you paste it into a ticket.

  • Every input, select, and textarea listed with its label status.
  • Five label methods recognised: for attribute, wrapping label, aria-labelledby, aria-label, and title.
  • Placeholder-only fields flagged, because placeholder text is not a label.
  • Fieldsets without a legend flagged, so groups get a name.
  • Inline colour contrast checked where both colours are present.

There are no settings to tune, because the rules come from WCAG itself. Paste the form, read the list, and fix the flagged fields from the top. If a field seems wrongly flagged, check its label link in the markup before dismissing it.

How Accessible Form Tester Works

The tester parses your HTML in the browser and walks every form field, checking for a label element with a matching for attribute, a wrapping label, an aria-labelledby reference, an aria-label, or a title attribute, in that order. The Word Counter tool counts the words in the test report the same way, entirely in the browser.

Two limits are worth knowing. The tester reads the markup you paste, so error messages that appear only after a failed submission are not seen, and it can only check inline colours for contrast, because the live page styles are not in the paste. Use it to find the structural faults, then test the live form with a keyboard and a screen reader.

Privacy

Your pasted HTML never leaves your device. The test runs in your browser with JavaScript, so the markup is read, checked, and reported on your own computer. Nothing is uploaded to a server, nothing is stored, and nothing is shared with anyone.

Because no account is needed, there is no name, email, or history tied to what you check. Closing the tab ends the session, and the browser clears the input from memory. That is the same protection on every tool here: your work stays yours, and nothing about it is kept, shared, or sold.

Tips

A few habits make Accessible Form Tester work smoother, whether you are checking one page or working through a whole site.

  • Label every field: a label element with a matching for attribute is the safest choice.
  • Never rely on placeholder: it vanishes when the user types, and many readers ignore it.
  • Group with fieldset and legend: every radio and checkbox group needs a name.
  • Mark required fields clearly: say which fields are required, in text, not just with a star.
  • Test after edits: a replaced field often loses its label, so re-run the test.

When the field list is clean, save the report with the date, so the next change has a baseline to compare against. If the report needs a PDF copy, the Case Converter tool changes the case of the text for tickets and docs.

More Tools For The Same Job

These tools handle the same kinds of jobs: reading, cleaning, and fixing the markup and text a form is built from.

  • HTML Beautifier: tidies messy HTML so form labels are easier to trace.
  • HTML Minifier: shrinks HTML for live pages once the form fixes are in.
  • HTML Entity Encoder: encodes special characters so pasted markup stays valid.
  • HTML to Markdown Converter: turns tested HTML into clean Markdown for docs.
  • Colour Contrast Checker: checks the contrast of form text and labels.
  • Character Counter: counts the characters in a form test report.
  • Word Counter: counts the words in a form test report or ticket.
  • Case Converter: changes the case of form test text for reports and tickets.
  • Text to PDF: turns a form test report into a PDF to share.
  • User Agent Parser: reads a browser user agent string when a form bug only shows in one browser.

FAQ

Common questions about testing form accessibility, answered plainly.

Is Accessible Form Tester by TechnSols Free?

Yes, Accessible Form Tester by TechnSols is completely free to use, with no account, no sign-up, and no usage limit. You can test as many forms as you like, and every test runs in your browser, so nothing you paste is uploaded or stored anywhere.

Why Is Placeholder Text Not Enough As A Label?

Placeholder text disappears when the user starts typing, and many screen readers do not announce it as a label, so the user loses the instruction exactly when they need it. A real label stays visible and is announced by assistive technology, which is why WCAG requires labels or instructions for every field that needs input.

What Is The Best Way To Label A Field?

A label element with a for attribute that matches the field id is the safest choice, because every browser and screen reader supports it. A wrapping label element works too. Use aria-label only when no visible label exists, such as a search box with a magnifying glass icon and no text.

Does This Tester Check Error Messages?

No, this tester reads the static markup you paste, so error messages that appear only after a failed submission are not seen. To test errors, submit the live form with bad data and check that each error is announced and tied to its field with aria-describedby, then fix the markup the live test reveals.

What Should A Fieldset Legend Say?

A legend should name the group in a few words, such as Delivery address or Payment method, so a screen reader user knows what the grouped fields are for before hearing them. Every fieldset needs a legend, and the legend should be the first element inside the fieldset.

Paste the form, label every field, and test again. A form that works for everyone is a form that takes orders, signups, and messages from everyone, and the test takes only a few minutes.

Follow TechnSols on Google
Add TechnSols as a preferred source to see more of our tools in Google Search.
Add to Preferred Sources
Advertisement