- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Sat, 22 Oct 2022 15:45:08 +0100
- To: John Foliot <john@foliot.ca>, Sailesh Panchang <sailesh.panchang@deque.com>
- Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>, Bryan Garaventa <bryan.garaventa@levelaccess.com>, Adam Cooper <cooperad@bigpond.com>
On 22/10/2022 14:19, John Foliot wrote: > Sailesh writes: > > > Developers tasked with making content accessible should not > ordinarily delve into the depths of the accessible name computation > algorithm and rely on less preferred fallback mechanisms to compute a > name for an element. The question isn't though if developers should or shouldn't. It's whether or not the behaviour of browsers to use the fallback (documented in the accessible name computation algorithm) to expose an accessible name counts as passing 4.1.2 Name, Role, Value. Nominally, I'd say it does. Whether it's good or bad practice is a separate discussion. 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 Saturday, 22 October 2022 14:45:23 UTC