RE: accessible name computation & changing button labels

Thanks Patrick. 

Do you mean that the omission of dynamic changes of name from the algorithm is conceptually solid?

In this case, how is it possible that the following aspect of SC4.1.2 can be ever satisfied?

"notification of changes to these items is available to user agents, including assistive technologies"

Cheers,
Adam 

-----Original Message-----
From: Patrick H. Lauke [mailto:redux@splintered.co.uk] 
Sent: Wednesday, 14 October 2020 6:12 PM
To: w3c-wai-ig@w3.org
Subject: Re: accessible name computation & changing button labels

On 14/10/2020 07:59, Adam Cooper wrote:
> Hi all … working on a project at the moment with buttons whose label 
> changes when pressed .. can’t get a screen reader to announce the 
> changed label in situ (i.e., when focus remains on the button).
> 
> Adding aria-live to the button or somewhere else on the screen just 
> seems like an ugly hack from yesteryear and it causes unnecessary 
> repetition.
> 
> Just wondering, first, what the accessible name computation algorithm 
> says about this case or what the spec behaviour should  be, and, second, 
> whether anyone has any tips on how to resolve this?

This seems to come down to different browser/AT combinations. The 
accname algorithm doesn't say anything about dynamic changes, and the 
approach is conceptually solid. Just that some browser/AT combos don't 
check/announce a dynamic change like that / bother to check. 
Unfortunately, this may indeed require some hacking like using a live 
region, or unfocusing and refocusing the control programmatically. Or 
putting it down to a browser/AT bug and not doing anything.

P
-- 
Patrick H. Lauke

https://www.splintered.co.uk/ | https://github.com/patrickhlauke
https://flickr.com/photos/redux/ | https://www.deviantart.com/redux
twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Wednesday, 14 October 2020 21:49:29 UTC