I believe the actual selector needs a <label> element also.
From WCAG guidelines: "If a form control does not have a properly associated text label, the function or purpose of that form control may not be presented to screen reader users."
Found these potential solutions to make sure it's accessible to screenreaders:
a <label> element with a for attribute value that is equal to the id of a unique form control
a <label> element that surrounds the form control, does not surround any other form controls, and does not reference another element with its for attribute a non-empty title attribute
Related to #68.
I believe the actual selector needs a
<label>
element also.From WCAG guidelines: "If a form control does not have a properly associated text label, the function or purpose of that form control may not be presented to screen reader users."
Found these potential solutions to make sure it's accessible to screenreaders:
<label>
element with a for attribute value that is equal to the id of a unique form control<label>
element that surrounds the form control, does not surround any other form controls, and does not reference another element with its for attribute a non-empty title attribute