Re: WCAG 2.2 - tightened requirements approach

Michael Gower wrote:
> where a requirement builds directly upon another, in ALL situations they are at different levels. That's why I think that considering moving Focus Visible to level A is advisable.

That would be more consistent at least. Thanks for doing that comparison, the way it was almost always AAA building on A/AA was striking.


> It's tough to tackle this entirely in an email, so my feeling is it would be useful to have a focused discussion on aspects of this.

Yep, I’m trying to make a survey about that this afternoon, for next week.

Sailesh wrote:
> Perhaps newly defining "visible keyboard focus indicator" is another way of getting it into normative requirements for WCAG 2.2 and onwards without adding a new SC or changing levels.

I worry that it might seem ‘sneaky’ to increase a requirement by defining something within the current SC differently. I would much rather see the change in SC text, however we do that.

To support thinking through different approaches I’ve added another version of the SC text to the doc:
https://docs.google.com/document/d/1g9_WBgfhViWAaRFIWWt10CP5rBsEVIWm3vT1vWqrHvI/edit


So it includes an A + AA variant.

Cheers,

-Alastair