Re: Aria-labelledby for button: AT support when button is self-identified

Hi. Screen readers much rely on accessible name when they announce the
control. So if screen reader doesn't read something as expected then
it's likely browser bug. However some screen readers do "a little bit
more" than plain accessible name announcement, that's where the
difference comes from.

1. @value of HTML:input@type="button" is part of name computation,
nothing else is provided so the name should be picked up from @value
in this case (http://rawgithub.com/w3c/html-api-map/master/index.html).
The accessible name should be "Select Policy Whole Life Policy 1"
2. nothing but text is provided so the accessible name should be
"Select Policy Term Policy 1" in this case.

Thanks.
Alexander.

On Tue, Sep 24, 2013 at 9:19 PM, Sailesh Panchang <spanchang02@yahoo.com> wrote:
> Hello,
>
> 1. On tabbing to the button neither NVDA nor JAWS (in FF or IE)  read the aria-labelledby attribute when it refers to its own  "value" attribute. Both screen readers read the "value" text.
> The aria-label works best in this situation based on current AT support.
> <h3 id="policy2">Whole Life Policy 1</h3>
> <input type="button" id="sbtn2" value="Select Policy" aria-labelledby="sbtn2 policy2" />
> JAWS does read aria-labelledby when one uses quick-nav to move to the button.
> ===
> Question: AT should expose the aria-labelledby i.e. the h3 text and the value attribute of the button in the above example, right?
>
> 2. When the aria-labelledby for a BUTTON element  refers to visible button text within , only JAWS reads it.
> NVDA  only reads visible button text.
>
> <h3 id="policy1">Term Policy 1</h3>
> <button id="sbtn1" aria-labelledby="sbtn1 policy1">Select Policy</button>
>
> In this case I suppose  this will be considered an NVDA bug, right?
>
> Thanks,
> Sailesh Panchang
>
>
>

Received on Wednesday, 25 September 2013 13:38:12 UTC