Repository navigation
Clarification needed on identical title and placeholder text for form controls without a visible label #5440
Replies: 1 comment
|
Please note that since I would consider the double announcement of the accessible name that you mention which might occur in some environments, for example, when a title uses the same identical text string as the accessible name, an AT issue. Arguably, redundant output may not be considered a clear fail anyway in cases where the accessible name is correct. It is a bit of a grey area, especially in cases where accessible names get super-long. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I would like clarification on how WCAG 2.x should be applied when a visible
<label>element cannot be used and a form control has identicaltitleandplaceholdervalues.For example:
The title attribute is used as the accessible name, while the placeholder attribute displays text inside the input field.
In this example:
I am not asking whether
titlecan be used as a fallback accessible name when a<label>element cannot be used.The question is whether authors are expected to address the duplicate announcement caused by using the same text for both attributes.
Should authors:
Would using identical values still be considered conforming if it causes redundant announcements for screen reader users?
If this is considered a WCAG failure, which Success Criterion would apply?
I would appreciate clarification on the expected authoring practice for this situation.
Related WCAG resources:
H65: Using the title attribute to identify form controls when the label element cannot be used.
Success Criterion 3.3.2: Labels or Instructions.
All reactions