RE: Plugins as SC - thread was: Visual Indicators

Hi Alastair,

Thanks for the kind explanation. I also get this better now.

The fundamental thing why I feel queasy about the entire requirement behind is that it is basically a "don't get in my way" requirement where "my" denotes either stylesheet, bookmarklet, extension, or external tool/application to set the values.

Apart from the need for users to use external tools for getting the desired result (which IS a burden):

I mean, this is a requirement that can be demanded for quite a few of all WCAG requirements, isn't it? 
So it is about "Don't do the following".

For instance, I understand well that https://www.w3.org/WAI/WCAG21/Techniques/failures/F104 basically say: don't use fixed with/height since else text will be truncated. 

But then why are the whole prerequisites for the text spacing requirement also not part of https://www.w3.org/TR/WCAG21/#reflow?


Same story with truncation and abbreviation of labels using "..." because the content does not push. Often, the full text is given in a tooltip which is not fully accessible (https://sarahmhigley.com/writing/tooltips-in-wcag-21/) and so on.

I have the feeling that there are multiple WCAG requirements dealing with effects arising *from the very same origin* but not saying explicitly so. It is on the implementers to detect these hidden relationships among them and react appropriately, a thing hopefully to be solved better in Silver. I mean the trick is finding the root of all evil for common violation cases and naming it, then digging into different effects with recommended techniques.

Again, I am late to the show and therefore I am grateful for any explanations, even if they crunch your valuable time. But maybe it is worth the invest 😉

Best Regards
Stefan 



-----Original Message-----
From: Alastair Campbell <acampbell@nomensa.com> 
Sent: Friday, April 17, 2020 6:18 PM
To: Schnabel, Stefan <stefan.schnabel@sap.com>
Cc: w3c-wai-gl@w3.org
Subject: RE: Plugins as SC - thread was: Visual Indicators

Hi Stefan,

For me, this section of the understanding document answers that question:

"User Responsibility
The ability to read and derive meaning from the overridden spacing rests with the user. The user may choose to exceed the spacing adjustments in the SC. If the increased spacing causes loss of content or functionality, the user will adjust or return to the author’s original spacing or spacing within the bounds of the SC. Regardless, the user needs the flexibility to adjust spacing within the bounds set in the SC without loss of content or functionality. Such changes may be achieved via user stylesheet, bookmarklet, extension, or application."

So essentially yes, the ambiguity is intended because there are various ways a user could apply the changes.

Kind regards,

-Alastair


-----Original Message-----
From: Schnabel, Stefan <stefan.schnabel@sap.com> 
Sent: 17 April 2020 16:37
To: Alastair Campbell <acampbell@nomensa.com>
Cc: w3c-wai-gl@w3.org
Subject: RE: Plugins as SC - thread was: Visual Indicators

Hi Alastair,

Accepted, but this is not the point nor does change it. 

https://www.w3.org/WAI/WCAG21/Understanding/text-spacing.html


is not written in a way that it classify bookmarklets as pure test tools, not means to fulfil the SC.

I don't know if this ambiguity is intended. 

Kind Regards
Stefan

Received on Sunday, 19 April 2020 08:35:14 UTC