RE: AccName question

Thanks, so do you have any objection to me adding that to the prototype?


Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com

-----Original Message-----
From: Joanmarie Diggs <jdiggs@igalia.com> 
Sent: Tuesday, September 11, 2018 11:09 AM
To: Bryan Garaventa <bryan.garaventa@levelaccess.com>
Cc: ARIA Working Group <public-aria@w3.org>
Subject: Re: AccName question

Hey Bryan.

The HTML-AAM covers HTML-specific name calculation. See the rules beginning here:
https://w3c.github.io/html-aam/#accessible-name-and-description-computation


HTH.
--joanie

On 09/11/2018 01:52 PM, Bryan Garaventa wrote:
> Hi,
> I received the following feedback, and I wanted to confirm we covered these in our review of AccName 1.1 during the review.
> 
> . Your script doesn't seem to provide an acc name for input type 
> submit with no value attribute supplied.  Browser's default to "submit".  The same might be true for other buttons like reset. . I believe when value is set on input type buttons it is also not shown by your script.
> . No accessible name is shown for the span element.
> 
> The last one seems clear to me, as with div, divs and spans with no role have no accessible name as we discussed.
> 
> What about the others? The type attribute is not part of the AccName spec, nor is the value attribute, yet browsers are using these regardless.
> 
> Thanks,
> Bryan
> 
> 
> 
> Bryan Garaventa
> Accessibility Fellow
> Level Access, Inc.
> Bryan.Garaventa@LevelAccess.com
> 415.624.2709 (o)
> www.LevelAccess.com
> 
>

Received on Tuesday, 11 September 2018 18:31:27 UTC