-
Notifications
You must be signed in to change notification settings - Fork 26
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
HTML-AAM: @abbr should be part of name calculation #16
Comments
Interestingly, HTML5.1 defines the abbr attribute as an "alternative label for the header cell" and that it is "typically an abbreviated form of the full header cell, but can also be an expansion, or merely a different phrasing." My experience is the opposite: it's typically an expansion. Either way, it's an interesting question. In my view, adding the value of the abbr attribute to the header element's contents as accessible name will lead to unnecessary verbosity. And if the abbr can be either an expansion, or an abbreviation, or just some alternative phrasing, how do we decide when or how it should participate in the name calculation? (This is where Steve chimes in with his grep about how abbr is used in the wild ;) Is it something to leave to ATs, or an AT user preference? What about accessible description? For instance, when browsing an actual header cell whose abbr is an expansion, it might be useful to get that expansion as an accessible description, but when navigating table cells, it might be nicer to just get the shorter header cell's contents. |
From @jnurthen on March 16, 2016 3:39 I can tell you how we use it. When we have sort controls within a table header then we use abbr to provide a version of the table header without the extraneous sorting control information to be used as the table header when reading cells in the table. For example Last Name sort ascendingsort descedingRegards,
|
Thanks @jnurthen. Looks like VO is using the abbr value when navigating cells, although I can't see how that's mapped using Accessibility Inspector. FF exposes the abbr as object attributes on the header cell. NVDA doesn't seem to read the abbr in FF, but JAWS does in IE and FF when navigating table data cells, but not when reading the actual header cell itself. Seems that preference then is to have abbr replace the header cell contents when navigating cells, but not when calculating name of the header cell itself? |
@cookiecrook Accessibility Inspector with Safari Tech Preview shows value of |
For |
Thanks.
Ok. The AAM currently says, rightly or wrongly, to map From your comment, I'm assuming that mapping
Chrome not exposing |
Such is the challenge with normalizing ~ten accessibility APIs into one. 😀 I'd guess the Chrome mapping is just left over from when they forked WebKit into Blink. A lot of the smaller WebKit accessibility fixes since that time never made it to Blink.
Ditto here. Yes, please use AXExpandedTextValue as the mapping. |
@cookiecrook Thanks, as always, for the feedback. I will update mappings for One last question: Any chance you have a link to publicly available documentation listing/describing AXExpandedTextValue? |
Addressed in ef2ad72. Closing. |
I don't think so. @fleizach? |
On Jun 1, 2017, at 10:08 PM, James Craig ***@***.***> wrote:
One last question: Any chance you have a link to publicly available documentation listing/describing AXExpandedTextValue?
No it's not an attribute in the public Accessibility API yet
… I don't think so. @fleizach <https://github.com/fleizach>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALmBA8VjqE0iApOW0u0G3eUorh0lZS7Fks5r_5jagaJpZM4KUUlD>.
|
From @cyns on January 12, 2016 23:15
abbr should replace (or maybe add to?) the inner text of the element, and participate in name calculation.
Copied from original issue: w3c/aria#181
The text was updated successfully, but these errors were encountered: