Interfaces and CSSChecked through WebDiag API

Form Accessibility Analyzer

Review programmatic control names, label/ARIA relationships, fieldset/legend, and static grouping signals without submitting the form.

  • input, select, textarea, button
  • Labels and ARIA references
  • No data entry
Online tool

Try the tool

Enter a URL: WebDiag will run a safe network check and show the result.

Page URL

Network check through backend

For HTTP/SEO tools, the URL is sent to the WebDiag API, where SSRF protection, DNS/IP policy, and redirect limits are applied.

Reviewed: 2026-07-17
01

How to use it

  1. 1

    Enter the URL of a page containing a form.

  2. 2

    Run the static HTML analysis.

  3. 3

    Fix unnamed controls, broken references, and weak grouping.

02

What the tool can do

  • Explicit and implicit labels, aria-label, aria-labelledby, button text, alt, and value sources.
  • Placeholder-only, title-only, duplicate ID, and broken aria-describedby signals.
  • Fieldset/legend and repeated radio/checkbox name groups.
03

Common use cases

  • Reviewing a registration or checkout form.
  • Finding placeholders used instead of persistent labels.
  • Checking fieldset/legend for option groups.
04

How it works inside

Hidden input elements are excluded from the user-control inventory.

Submit/reset inputs without value use a default-value signal, but browser localization is not modeled.

05

Questions and answers

Does placeholder count as a label?

No. The tool reports placeholder-only controls as a separate review risk.

Does it submit the form?

No. Only bounded static analysis of source HTML is performed.