- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Thu, 2 Jan 2025 10:41:56 +0000
- To: w3c-wai-ig@w3.org
On 31/12/2024 20:23, Audrey Frank wrote: [...] > We have been using a workaround for JAWS users and here’s why – if a > JAWS user tabs to the reveal buttons and presses enter, JAWS stops > reading as soon as they hit Enter. This sounds more like a problem with how the reveal functionality has been implemented. Does it use live regions when each bit is revealed? Are the buttons implemented as actual disclosure widgets, or just a button that then (silently) just shows a container of content somewhere? I'd say try and fix this part (maybe even with scripting that monkey-patches the output of Captivate, if that's what the problem is), rather than trying to route around the core problem with hacky solutions. (and as a short answer to the original question, it doesn't fail 2.4.11 because the focused element isn't obscured/covered by some other content ... by design, there IS no visible content, and it's not being overlaid/covered, so 2.4.11 doesn't apply) P -- Patrick H. Lauke * https://www.splintered.co.uk/ * https://github.com/patrickhlauke * https://flickr.com/photos/redux/ * https://mastodon.social/@patrick_h_lauke
Received on Thursday, 2 January 2025 10:42:05 UTC