New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understanding Label in Name #352
Comments
From @devarshipant on March 19, 2018 19:30 Hi, Some observations:
Here, First Name is a visible label and also the name. I think the Understanding section needs to mention that visible text label is the accessible name in many cases. And there are instances where visible text 'Matches' the accessible name.
|
From @mbgower on April 11, 2018 21:34
I wanted to clarify that placeholder text is not considered a replacement for a label in the HTML5.2 specification
or in aria:
Use of the TITLE attribute or accessible hover text for a label is allowed (but discouraged) in WCAG, and its value is taken into account in the accessible name specification. It does not stand as an example of a non-visible label, since it is visible (and so could potentially be found and announced by someone using speech recognition) , just not persistent.
If a "search" button appeared after an input with no label, then I agree that aria-label="search" is a possible solution; however, the chances for the engine getting confused between whether the user wants to activate the search button or reposition to the search input field seems heightened (depending on how the user references the control with different speech affordances such as "move to" or "select"). So my take would be that issues with missing labels (or sub-par workarounds) will likely fail existing WCAG 2.0 requirements -- and so need to be rectified, regardless of the new Label in Name SC. |
From @mraccess77 on April 11, 2018 23:44 In my opinion a title attribute could not be used as the sole source of a visible label under SC 3.3.2 because most user agent implementations don't expose it on keyboard focus. I would imagine that finding a title attribute for speech input user would be difficult and it would not be visible on mobile. Title attributes could be used to meet SC 1.3.1 or 4.1.2 if the provide they same meaning as what is covered with presentation. |
From @mbgower on April 12, 2018 14:43 @mraccess77 yes, especially given that many speech users have mobility issues (i.e., are using the speech control to compensate for an inability to use a pointer and/or keyboard), title with only user agent behaviour seems like a sub-par solution. I just wanted to flag that I think TITLE is part of the accessible name formula, and so enters into the discussion for meeting this SC. |
From @devarshipant on April 13, 2018 15:23
You are correct--spec does say so. Correct me if I am mistaken here--the value of placeholder attribute becomes the accessible name if no other primary accessibility attribute exists (label, aria-label etc.). In that case, and functionally too, placeholder is no different than the title.
The approach could be sub-par if the end user expierence is not great. There could be instances where the placeholder by itself gives the meaning of the control, not merely the hint. It is unorthodox, but does the following fail WCAG 2.1? |
From @awkawk on April 13, 2018 15:30
If someone found that the placeholder text was exposed by the accessibility API even after text was entered into the control it might be regarded as passing 4.1.2, but as soon as someone filled it in there would be no label available so unless there was a redundant text label it would fail 2.4.6 in WCAG 2.0. This is not encouraged, obviously. |
From @mraccess77 on April 13, 2018 15:36 In my opinion placeholder text is fallback content just like the src attribute might be on an image without alt and therefore fallback content should not be considered as part of the accessible name. I would fail this for both visual labels and programmatic labels because the visual label goes away when the field has data. |
From @mbgower on April 13, 2018 16:1
There are no occurrences of |
From @devarshipant on April 13, 2018 17:0
Agreed. Sorry, but I am only questioning -- why does title attribute get preferential treatment over placeholder? Title attribute disappears too. And it's implementation is widely misunderstood w.r.t how screen readers process it. This is how I arrived at this conclusion where placeholder gets calculated as the acc name. It checks out with JAWS and NVDA, but I don't know if vendors are reading the Acc Name algorithm to calculate placeholder. Or reading it at all. HTML 5 says "User agents should present this hint to the user, after having stripped line breaks from it, when the element's value is the empty string and the control is not focused (e.g. by displaying it inside a blank unfocused control)." Hint = "value of placeholder" Tie that in with the following Acc Name Cal: G. Otherwise, if the current node is a Text node, return its textual contents. [1] Text Node = "value of placeholder on the input element" To my mind the hint that user agents give (which is the value of the placeholder) is the innertext being computed in G.
|
From @mbgower on April 13, 2018 23:15
Title is not considered a great implementation; I can't find it right now but there's a note somewhere cautioning against its use. That said, the way user agents display the value of the title attribute is not visibly persistent but it is visibly consistent: hovering your mouse over the item will always redisplay the value. In the case of placeholder, once the input field has any value populated, the ability to view the value of placeholder is lost. |
From @mbgower on April 17, 2018 5:3 Thanks @jake-abma |
From @devarshipant on April 17, 2018 13:58
Great points. However, the number of controls and meaningful context around the controls makes a difference when recommending title or placeholder. Here is a mock up showing Log in page using placeholder text.
It can be viewed on pressing the escape key. But you are correct, it is not as helpful as title. |
From @lseeman on April 22, 2018 16:55 Can we add that
|
From @ITakora on May 1, 2018 16:4 Can you please tell me if this would be a good or bad practice for this criterium? |
The button X question was also asked here: https://twitter.com/stevefaulkner/status/1080436758679035904 |
Looks like the understanding document doesn't answer this question. (https://www.w3.org/TR/WCAG21/#label-in-name). It hinges on whether the "X" is regarded as text. Text is defined as "sequence of characters that can be programmatically determined, where the sequence is expressing something in human language". Is the "X" expressing something in human language, or is it just a symbol? |
as mentioned on twitter (https://twitter.com/patrick_h_lauke/status/1080442831179796480), i'd go even further and ask about punctuation, brackets, etc. i.e. would |
Why should it fail if aural output is without punctuation?
Sent from phone
… Am 02.01.2019 um 20:46 schrieb Patrick H. Lauke ***@***.***>:
as mentioned on twitter, i'd go even further and ask about punctuation, brackets, etc. i.e. would <button aria-label="Close">[Close]</button> or <button aria-label="More">More ...</button> fail?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Because aural output has nothing to do with whether or not the visible text (or image of text) is present in the accessible name or not, which is the nominal criterion to decide whether this would pass or fail? Practically, it depends here if we expect voice users to speak the punctuation (i.e. if a user said "open square bracket close close square bracket" or similar, which likely wouldn't trigger the button if its accessible name set by |
Granted, but in the cases quoted, my understanding was that regarding the acccessible name, the visible label (with punctuation) would be replaced by the content of the aria-label attribute, which is without.
Sent from phone
… Am 02.01.2019 um 22:02 schrieb Patrick H. Lauke ***@***.***>:
Why should it fail if aural output is without punctuation?
Because aural output has nothing to do with whether or not the visible text (or image of text) is present in the accessible name or not, which is the nominal criterion to decide whether this would pass or fail?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
and that's the point: is this a failure? According to the letter of the SC, yes (as the accessible name now doesn't match the visible text - if by text we also mean the punctuation). But in practical terms, I would argue that no, it's not (as voice users would likely not say the punctuation out loud, so it would make no difference in real-world usage). |
Am 03.01.2019 um 10:57 schrieb Patrick H. Lauke:
Granted, but in the cases quoted, my understanding was that
regarding the acccessible name, the visible label (with
punctuation) would be replaced by the content of the aria-label
attribute, which is without.
and that's the point: is this a failure? According to the letter of
the SC, yes (as the accessible name now doesn't match the visible text
- if by text we also mean the punctuation). But in practical terms, I
would argue that no, it's not (as voice users would likely not say the
punctuation out loud, so it would make no difference in real-world usage).
Fully agree, I would pass this. An all-too-close reading of the SC text
would miss the point here. As to the X question, it would be good to
have some evidence what speech users would do - is it conceivable that
they'd try "click X"? I would imgagine they might alternatively try
"click close" since this is a fairly conventional accName for that
symbol in a dialog context (often, alas, missing) - or resort to
bringing up the numbers to then say "click [number]" (if the developer
cared to make this a proper button or link).
…
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#352 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/AJhtPz5u2PMTfTnF3o_2vP_0fWtxm4RQks5u_dPxgaJpZM4Ukqtb>.
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
|
as an aside: Eric Wright did some testing for the "X" close https://twitter.com/ewaccess/status/1080626915160002560 ... it seems that, at least in Dragon 15, both "click close" and "click X" work at least |
On the punctuation / spacing aspect, should this example fail?
|
Hi Gang, I just reviewed this discussion and I'm happy to say that the most recent version of the Understanding document (adopted by the WB) addresses all these points and also they are re-addressed in some techniques. A summary of where I ended up in the rewrite: PlaceholdersPlaceholders are included in the accessible name calculation. They are also a likely candidate to be used as a string by a speech-input user in the event there is no other candidate label. I have included language to this effect in the Understanding doc, with lots of cautionary language around it. TitleTitle is also in the accessible name calculation. The Understanding doc does not specify that a title value serves as a visible label, but it does indicate that using title to programmatically provide a name (or reinforce a label) is acceptable. Punctuation and symbolsBoth tackled. The X close button example is covered by this. In that scenario, the X is not a word but a symbol. We don't treat it as meaningful text, and thus providing an aria-label of "close" is fine and not a failure of Label in Name. @michael-n-cooper I just had a glance at the current version of the Understanding doc, and although it looks like all the main content is there, all the subheadings have been stripped out of the Intent section. Is that a glitch? I wanted to direct folks over to the updated version, but without those subheadings, it's a tougher slog!! |
On 12/04/2019 4:44 p.m., Mike Gower wrote:
@michael-n-cooper <https://github.com/michael-n-cooper> I just had a
glance at the current version of the Understanding doc, and although
it looks like all the main content is there, all the subheadings have
been stripped out. Is that a glitch?
Headings have to be in <section> elements. I pushed a fix:
8d0eae3
Michael
|
This issue looks to be inactive, so I'm closing it. Please re-open if necessary. |
From @awkawk on March 2, 2018 15:22
The 2.4.12 Label in Name (A) SC has draft Understanding content that can be viewed at Understanding Label in Name.
Please review the Understanding document and submit a comment on this issue for any changes that are needed to the content.
Copied from original issue: w3c/wcag21#788
The text was updated successfully, but these errors were encountered: