- From: <bugzilla@jessica.w3.org>
- Date: Fri, 19 Dec 2014 00:18:00 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27294 --- Comment #20 from Alice Boxhall <aboxhall@chromium.org> --- (In reply to Alice Boxhall from comment #19) > (In reply to James Craig from comment #10) > > (In reply to Alice Boxhall from comment #2) > > > I'm slightly unconvinced about the name 'computedLabel' as to me it sounds > > > like it might return an HTMLLabelElement. Would 'computedName' work? > > > > "name" is ambiguous because it means different things across different > > accessibility APIs and even in host languages. For example, in HTML @name is > > like a non-unique @id. > > > > ARIA uses the term "label" consistently, so I'm not convinced this would be > > a point of confusion for authors. It's consistent with the meaning used in > > <label>, @aria-label, @aria-labelledby, and other API uses. > > The algorithm to compute the string which would be returned from this method > is called the "Accessible Name Calculation" algorithm > (http://www.w3.org/TR/wai-aria/roles#namecalculation) so I don't think it's > really all that consistent. > > Both "name" and "label" are fairly overloaded at this point, and I think > "name" better represents this concept - see also the general accessibility > concept of Name (in the context of Name, Role, State and Value), e.g. > http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html Also, the "nameFrom" property in the ARIA spec. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 19 December 2014 00:18:02 UTC