- From: James Craig <jcraig@apple.com>
- Date: Sun, 29 Jan 2017 17:54:12 -0800
- To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>, Joseph Scheuhammer <clown@alum.mit.edu>
- Cc: Dominic Mazzoni <dmazzoni@google.com>, Alice Boxhall <aboxhall@google.com>, Marco Zehe <marco.zehe@gmail.com>, Alexander Surkov <asurkov@mozilla.com>, David Bolter <david.bolter@gmail.com>, Accessible Rich Internet Applications Working Group <public-aria@w3.org>
FWIW, I confirmed the bug affects WebKit, too. https://webkit.org/b/167567 > On Jan 29, 2017, at 8:05 AM, James Craig <jcraig@apple.com> wrote: > > Firefox’s behavior is correct. @aria-label yields a white space string, which is then trimmed to an empty string, and the calculation continues to the element contents. > > I don’t think the name computation needs to be updated. These are just bugs in IE11 and Chrome. > > Joseph, do you agree? > > Bryan, will you file bugs in the Chromium and IE bug trackers? Does Edge have the same bug? > > PS. If you can reproduce the same bug in iOS or macOS, will you please file a bug the WebKit tracker, too? http://webkit.org/new-ax-bug Thanks! > > >> On Jan 27, 2017, at 2:40 PM, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> wrote: >> >> Hi, >> I've recently been updating my naming calculation tests, and the following is not consistent so I wanted to ask what is the expected behavior. >> >> Markup: >> >> <a href="#" aria-label=" ">test</a> >> >> In IE11 and Chrome, the accessible name is " ", which is nonsensical. >> >> In Firefox however the name is "test" which does make sense. >> >> So which is technically valid and how should browsers be doing this correctly? >> >> Thanks, >> Bryan >> >> >> >> Bryan Garaventa >> Accessibility Fellow >> SSB BART Group, Inc. >> bryan.garaventa@ssbbartgroup.com >> 415.624.2709 (o) >> www.SSBBartGroup.com >> >> >
Received on Monday, 30 January 2017 01:54:53 UTC