RE: Plugins as SC - thread was: Visual Indicators

Hi Stefan,

 > This is the standard scenario in large companies creating UI frameworks and for content builder tools, something that should be treated with more priority within the WCAG group, INHO. 

My point was that the documentation for different organisations and/or frameworks about *their* most effective way to be accessible would be different. The documentation we do for each organisation is different, even though it uses the requirements from WCAG as the baseline.

However, WCAG needs to work across different organisations and approaches, we cannot be opinionated about that.

 > Let's put my question different: *How many WCAG requirements* do currently strictly *require* the usage of 3rd party tools (exception: screen readers) to have the desired effect (with described SC met) for users with disabilities?

The guidelines are written to be about the content, so the relationship is rarely direct. There are quite a few that primarily benefit screenreaders but also benefits others in other scenarios.

Trying to keep to your point though, these come to mind (at level AA): 
- Orientation (physical cradles)
- Identify input purpose (icons set additions).
- Text spacing (Font or CSS overrides in various forms)
- Content on hover (magnification).
- Character key shortcuts (voice input)
- Label in name (voice input)

The more user-requirements we aim for, the more likely it is that we expand beyond current browser/AT features.

 > Saying "browsers won't implement that, therefore you can and have to use external tools" removes all the pressure from the browser vendors. 

As a working group, we have no direct influence with browser vendors and I can't comment on their priorities or approaches.

What we can do is write criteria that can be fulfilled by either authors or user-agents. Language such as  "a mechanism is available" can be author or user-agent fulfilled. 

As another example, if the browsers all implemented highly visible focus styles (or even an option to enable that) then the new focus-visible SC would be fulfilled without the author having to do anything. 



Received on Monday, 20 April 2020 09:59:17 UTC