- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 14 Oct 2020 08:11:47 +0100
- To: w3c-wai-ig@w3.org
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 07:12:03 UTC