Re: Confusion with spec name for "Accessible Name Computation"

> On May 12, 2016, at 12:56 PM, Rich Schwerdtfeger <richschwer@gmail.com> wrote:
> 
> We can discuss. This impact the SVG AAM as well. On Windows systems name is the appropriate term and it was first introduced in 1995.

Right, but the reason we chose "label" in ARIA was because:
- it more closely matched the HTML convention <label>
- it did not include the baggage of the platform-specific API "name" which means something different in HTML and on other OS Accessibility APIs

> I would need to reeducate a lot of people at IBM too. 

I'm asking for a prose-only change to match the ARIA spec "label"... There is no web code associated with "accessible name" so you should not have to re-educate anyone.

> Can you give us a link to where you found the concerns?

There's no link, but there have been emails and private conversations with people from both authors and implementers from a few different companies. The feedback could be summarized as, "ARIA uses 'label' but this other spec uses 'name'. What's the difference. Are they the same? If not, how do they differ?" 

Since "accessible name" and "accessible label" are the same, we should standardize the language to avoid further confusion.

Thanks,
James

> Thanks,
> 
> Rich
> 
> Rich Schwerdtfeger
> 
> 
>> On May 12, 2016, at 2:31 PM, James Craig <jcraig@apple.com <mailto:jcraig@apple.com>> wrote:
>> 
>> 
>> I've heard some confusion recently that the spec name for "Accessible Name Computation" does not match the property usage ("aria-label", "aria-labelledby", HTML <label>, etc.) The concern is that "name" means different things in some accessibility APIs and @name means something else entirely in HTML.
>> 
>> Will you consider changing the spec title to one of the following:
>> 
>> - "Accessible Label Computation" 
>> - "Text Alternative Computation"
>> 
>> Or another spec title that doesn't have associated baggage of "Name."
>> 
>> Thanks,
>> James Craig
>> 
>> 
>