- From: Michael Livesey <mike.j.livesey@gmail.com>
- Date: Tue, 11 Jul 2023 20:34:20 +0100
- To: "Patrick H. Lauke" <redux@splintered.co.uk>
- Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
- Message-ID: <CAJOTQEKz8sKZgMO+J=yGYc-y6JPHQgaZ4jMb8v87jMyLd=4CVA@mail.gmail.com>
We both know that the lowest standard often becomes the standard. Thus by setting the bar extremely low, to the point of being a worse UX for visually impaired users, it follows that the WCAG is encouraging the obliteration of focus-visible behaviour. Something you even said yourself was a hard fight to win. So on winning the fight for focus-visible, you set a standard that tells developers that they can ignore it and still get AA accreditation??? What is interesting about my position? That I want visual impaired users to actually be able to see what they have clicked? That I want focus-visible to work if they set it to show focus on click. I am not sure that is particularly interesting. On Tue, Jul 11, 2023 at 8:25 PM Patrick H. Lauke <redux@splintered.co.uk> wrote: > On 11/07/2023 20:15, Michael Livesey wrote: > > > Thus it follows that the WCAG wording in 2.4.7 actually encourages a > > worse UX for a accessible users than either focus or focus-visible, the > > browser default behaviour. > > WCAG does not encourage anything of the sort. WCAG sets a baseline > lowest limit of what sites must do in order to comply. > > If you're concerned that WCAG's baseline is too low and should be > raised, then I suggest you propose a new, stricter Success Criterion, > and get that approved by both the working group and the various > stakeholders involved in ratifying WCAG. > > > Your position is very interesting, Patrick. > > And so is yours, Michael. > > 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 19:34:36 UTC