Input buttons must have discernible text

Rule input-button-name · Forms · impact critical · Static + live

↩ Back to the rules index · WCAG cross-reference

Why it matters#

An input button with no name is announced as just "button" — the user cannot tell what pressing it does. <input type="submit">/<input type="reset"> fall back to the browser defaults ("Submit"/"Reset"), but value="" erases even that.

How to fix#

Set value="…" (or aria-label) on the input. For submit/reset, either omit value to keep the browser default or give it a non-empty one.

Example#

<input type="button">

<input type="button" value="Search">

Example#

<input type="submit" value="">

<input type="submit">

WCAG success criteria#

4.1.2 Name, Role, Value — Level A#

Every UI component must expose a correct name, role, and (where relevant) state/value to assistive technology.

Understanding 4.1.2

Standards#

This rule contributes to the following standards:

WCAG A EN 301 549 Section 508 Trusted Tester ACT

References#

• WCAG — Name, Role, Value