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


For an SVG element and within SVG, using the term text alternative is too
close to image alt text for folks not to get confused. Within a graphics
document (inline, embed or iframe SVG - just not image element) we want to
expose a rich document to the user. I think in the Graphics Module we talk
about semantic text or semantic text equivalent - specifically so folks
realize that there may be a whole hierarchy of information and an element
is not trying to summarize the entire graphic in one label.

    Fred Esch                                                 
 Watson, IBM, W3C                                             
 IBM Watson       Watson Release Management and Quality       

From: Cynthia Shelly <>
To: Rich Schwerdtfeger <>, James Craig
Cc: ARIA Working Group <>
Date: 05/12/2016 09:12 PM
Subject: RE: Confusion with spec name for "Accessible Name Computation"

I’d prefer “Text Alternative Computation.” I find “Accessible Label
Computation” even more confusing that “Accessible Name Computation” since
it has inputs that are <label> aria-label, aria-labelledby, and also inputs
that are not labels at all. It has 2 outputs, and description is not a
label at all. Text Alternative is accurate, and not taken by anything else.

From: Rich Schwerdtfeger []
Sent: Thursday, May 12, 2016 12:57 PM
To: James Craig <>
Cc: ARIA Working Group <>
Subject: Re: Confusion with spec name for "Accessible Name Computation"

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. I would need to
reeducate a lot of people at IBM too.

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



Rich Schwerdtfeger

      On May 12, 2016, at 2:31 PM, James Craig <> 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."

      James Craig

Received on Friday, 13 May 2016 13:06:59 UTC