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: Best Practice: Form <input> elements should have a visible label
<input>elements may be given a title using the
aria-describedbyattributes (but not both). These attributes are used to provide additional information such as a hint.
aria-describedbyattributes are used to provide additional information such as a hint. Hints are exposed to accessibility APIs differently than labels and as such, this can cause problems with assistive technologies.
When form inputs such as text entry fields, radio buttons, check boxes, and select menus contain no labels other than
aria-describedbyattribute values, screen readers interpret the content as advisory information only. Labels created by the
aria-describedbyvalues are not sufficient to create a true label that can be determined programmatically from the code to convey the purpose of the input form element.