brad
February 27, 2026, 4:42pm
1
I am not sure if they are valid or if I am doing something wrong.
Example 1: I have a select field where what would be in the label is in the first defualt option.
<select id="selectJobLocation" class="form-select mt-5 form-select-sm" dmx-bind:options="filter_locations.data.query" optiontext="JOJobCity" optionvalue="JOJobCity">
<option value="">Showing All Locations</option>
</select>
Example 2: This is a iput field where what would be in the label is in the place holder text
<input id="search_productions" name="search_productions" type="search" class="form-control form-control-sm" placeholder="Title Search">
In both cases the label was left off on purpose to save space and design.
Cheese
February 27, 2026, 4:58pm
2
Would be helpful, in this case, to have an 'Ignore Warning' button maybe?
brad
February 27, 2026, 6:57pm
4
If this is a valid warning, we need a way to add the .visually-hidden class to the label in the UI.
brad
February 27, 2026, 7:15pm
6
Wow, I would have never looked way down there. Thanks @Quy ! That totally fixed it. I am happy that this is not a bug. And I learned something new to boot. Much appreciated.
1 Like
ben
February 27, 2026, 10:35pm
7
To add to this discussion, inputs that do not require labels
<input type="hidden"> -- ignored by assistive tech.<button> elements -- the button text itself is the labelIcon-only buttons -- must still have an accessible name, but not a <label>
Decorative or disabled controls that are not interactive
These controls must have labels:
Text inputs (name, email, phone, etc.)
Textareas
Select dropdowns
Checkboxes
Radio buttons
Date, number, and other semantic input types
Search fields (even if the label is visually hidden)
You could use floating labels instead
1 Like
system
March 2, 2026, 8:09am
9
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
