RE: 2.4.7 Focus Visible

There are many things I can think of that should be browser  features and/or exposed through APIs in browsers that could improve accessibility, but filing bugs and waiting seems to be a laborious way to do it ... is there any value in a W3 specification that defines how browsers should handle this or that aspect of things like CSS and what is the responsibility of *authors*?


-----Original Message-----
From: Patrick H. Lauke <redux@splintered.co.uk> 
Sent: Tuesday, July 11, 2023 9:44 AM
To: w3c-wai-ig@w3.org
Subject: Re: 2.4.7 Focus Visible

On 11/07/2023 00:07, Patrick H. Lauke wrote:
> 
> On 10/07/2023 23:42, Michael Livesey wrote:
>> Even Patrick appears not to appreciate how it operates, suggesting on 
>> Firefox a single keyboard use will trigger it for subsequent mouse 
>> clicks.
> 
> Patrick does appreciate how it was implemented in Firefox 
> https://bugzilla.mozilla.org/show_bug.cgi?id=1445482#c19, but Patrick 
> must have missed a recent change that tweaked that behaviour.

And now these repressed memories are finally coming back to me ... here are the bugs I filed back in the day about getting browsers to implement an override switch to allow :focus-visible to always kick in even after mouse/pointer interaction. Boosting this/lobbying browsers to do this has, in my view, a much greater chance to provide a simple solution that then satisfies all different constituencies/stakeholders, and again puts the control back in users hands/preferences (rather than pushing/advocating for one solution for everybody)

https://bugzilla.mozilla.org/show_bug.cgi?id=1742284

https://bugs.chromium.org/p/chromium/issues/detail?id=1272296

P
--
Patrick H. Lauke

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

Received on Tuesday, 11 July 2023 00:05:00 UTC