SC 3.3.2: Labels or Instructions needs another example for failure when a <select> element lacks a visible label

[amberhinds]

I'm moving my comment on #3808 to a new issue. I believe that we need another failure example for a pattern like this.

Another example of this that doesn't include an image:

two selects with default options (filter by category and date and a filter button, without visible labels for the selects

<div class="alignleft actions">
				<label for="filter-by-date" class="screen-reader-text">Filter by date</label>
		<select name="m" id="filter-by-date">
			<option selected="selected" value="0">All dates</option>
		<option value="202508">August 2025</option>
		</select>
		<label class="screen-reader-text" for="cat">Filter by category</label><select name="cat" id="cat" class="postform">
	<option value="0">All Categories</option>
	<option class="level-0" value="1">Uncategorized</option>
</select>
<input type="submit" name="filter_action" id="post-query-submit" class="button" value="Filter">		</div>

This has screen reader-only labels, but no visible labels for sighted people once an option is selected. Many would consider this a failure, but there's no explicit example either way as a fail or a sufficient technique.

Also worth noting that these would fail Label in Name since the visible text doesn't match the accessible name.

@aardrian has another example (with voice control testing results):
https://cdpn.io/aardrian/debug/MYadEmB

Full pen:
https://codepen.io/aardrian/pen/MYadEmB

[detlevhfischer]

I raised a similar issue a while ago: #2484