Re: WCAG 2.2 - tightened requirements approach

On 11/07/2019 00:30, Sailesh Panchang wrote:
> Much as I would like to see SC 2.4.7 (present form) as a Level A SC,
> it is now moot.
> Most accessibility laws and  court decisions require at least Level
> AA, so one has to meet all Level AA Scs including SC 2.4.7 whether at
> Level A or Level AA.

The main point of keeping 2.4.7 as is but moving it to A is so that it 
doesn't look odd from a structural point of view if WCAG has two SCs 
that essentially cover the same thing, with the new one being more 
precise/stricter. The intent isn't to make it now apply to more sites 
that only test up to A, but rather not to have developers wondering why 
there's two AAs that overlap so much.

> Content that has focus visible today under WCAG 2.0(AA)   will not
> pass a modified SC text if the page is re-evaluated because of content
> changes.

However, that is in line with the idea of backwards compatibility in 
WCAG 2.1 https://www.w3.org/TR/WCAG21/#requirements-for-wcag-2-1

On a general note, the problem with "focus visible" has always been that 
it does not normatively define what "visible" actually means, making it 
one enormous loophole

P
-- 
Patrick H. Lauke

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

Received on Thursday, 11 July 2019 00:33:56 UTC