A11y Check

KWCAG 2.2 · 7.4.1

How to test Labels for inputs

How to evaluate the KWCAG 2.2 checkpoint “Labels for inputs”. Automation catches part of it; the rest needs a person.

Which standards this maps to

Korean standard (KWCAG 2.2)
7.4.1 Labels for inputs
Understandable
International standard (WCAG 2.2)
3.3.2 Labels or Instructions (A) ↗1.3.1 Info and Relationships (A) ↗

How to test it

Automated checks verify labels exist; confirm they describe the purpose and placeholders aren't used as labels.

What automation covers

9 automated rules judge this checkpoint. Each comes with remediation guidance.

  • Form elements must have labels label

    Associate a label element (or aria-label) with every input; placeholder is not a label.

  • Select elements must have an accessible name select-name

    Provide a label or aria-label for select elements.

  • Form elements should have a visible label label-title-only

    Provide a visible label instead of relying on the title attribute.

  • Form fields should not have multiple labels form-field-multiple-labels

    Use one label per field; add descriptions via aria-describedby.

  • Buttons must have discernible text button-name

    Icon-only buttons need aria-label or visually hidden text.

  • Input buttons must have discernible text input-button-name

    Provide a value attribute for input buttons.

  • summary elements must have an accessible name summary-name

    Give summary elements descriptive text.

  • ARIA input fields must have an accessible name aria-input-field-name

    Name custom ARIA input widgets via aria-label/labelledby.

  • ARIA toggle fields must have an accessible name aria-toggle-field-name

    Name ARIA toggle widgets (checkbox, switch, radio).

See how your own site does

Enter a URL and we will check this checkpoint along with the other 32. One page can be audited without signing in.

Run a free check

Related checkpoints