Accessibility checking

Rocket Validator looks for accesibility violations on your pages using the axe-core accessibility engine, hosted on our own servers and integrated into our web crawler. You don't need to buy an additional license, everything's already included in your Pro account at Rocket Validator.

WCAG: 1.3.1, 4.1.2: Form <input> elements must have labels

Each form element must have a programmatically associated label element.

Effective form labels are required to make forms accessible. The purpose of form elements such as checkboxes, radio buttons, input fields, etcetera, is often apparent to sighted users, even if the form element is not programmatically labeled. Screen readers users require useful form labels to identify form fields. Adding a label to all form elements eliminates ambiguity and contributes to a more accessible product.

When labels for form elements are absent, screen reader users do not know the input data expectations. Screen readers cannot programmatically determine information about input objects without an established label relationship (or redundant text serving as a label).

The absence of labels prevent fields from receiving focus when read by screen readers, and users with impaired motor control do not get the benefit of a larger clickable area for the control since clicking the label activates the control.

Learn more about this accessibility rule at Deque University >>

Validate accessibility and HTML5 on large sites, starting at $24/week. Start here