label-not-descriptive
Rule Severity : Serious
Description
Labels must clearly describe the purpose of the associated form field. This ensures that users, especially those relying on assistive technologies, can understand the context and function of each field without ambiguity. Descriptive labels are crucial for accessibility and usability, as they provide necessary information to complete forms accurately.
The label-not-descriptive
rule aligns with WCAG Success Criterion 2.4.6: Headings and Labels (Level AA), which requires that labels describe the topic or purpose accurately. This helps users understand the purpose of the fields in a webpage and interact with them effectively.
Examples
In the following example, the label “Info” is not descriptive enough to convey the purpose of the field, violating the label-not-descriptive
rule.
In the following corrected example, the label is updated to “Full Name,” which clearly describes the purpose of the field:
How to fix?
To fix violations of the label-not-descriptive
rule, follow these steps:
- Review all labels associated with form fields on your webpage.
- Ensure that each label clearly and accurately describes the purpose of the field.
- Avoid using vague or generic terms like “Info,” “Details,” or “Input”.
- Use specific, meaningful labels that provide context and clarity to users.
Reference
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!