You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Hiding label text section of the Labeling Controls forms tutorial uses duplicate accNames for two different controls that are part of the same form.
WCAG Notes
This has caused confusion about what is the visible label for the text box in the context of the following SCs:
2.5.3 Label in Name for believing the text box meets it thanks to the button label (as opposed to N/A),
3.3.2 Labels or Instructions because the text box has no visible label and devs want to extrapolate to other fields.
I am using the passive voice with "has caused confusion" because these SCs and comments came my way from non-practitioners more than once, each from assorted places (clients).
Interaction Bits
With voice control, when a user tries to select the Search button they are prompted to choose whether they meant the input or the button.
Screen reader elements lists at least disambiguate between buttons and text fields.
Suggested Change(s)
Change the accName of the text fields to "Keywords".
Code Changes
So Approach 1 (why is that part of the heading CSS generated content anyway?):
I am pretending Approach 4 does not exist. Not very mature of me, but whatever.
Maybe Language Changes
Adjust the guidance to qualify that as a search form it gets some allowance on missing visible text from the commonly understood pattern. Or don't use a search form.
Identify the button label as not the same as the text box.
Identify that the text field would not pass 2.5.3, but instead 2.5.3 does not apply.
The text was updated successfully, but these errors were encountered:
Issue
The Hiding label text section of the Labeling Controls forms tutorial uses duplicate accNames for two different controls that are part of the same form.
WCAG Notes
This has caused confusion about what is the visible label for the text box in the context of the following SCs:
I am using the passive voice with "has caused confusion" because these SCs and comments came my way from non-practitioners more than once, each from assorted places (clients).
Interaction Bits
With voice control, when a user tries to select the Search button they are prompted to choose whether they meant the input or the button.
Screen reader elements lists at least disambiguate between buttons and text fields.
Suggested Change(s)
Change the accName of the text fields to "Keywords".
Code Changes
So Approach 1 (why is that part of the heading CSS generated content anyway?):
Would become:
Approach 2 would go from:
To:
And Approach 3 would go from:
To:
I am pretending Approach 4 does not exist. Not very mature of me, but whatever.
Maybe Language Changes
The text was updated successfully, but these errors were encountered: