Re: user-adaptation SCs

Hi All,
I have been thinking about this too. I am not convinced that all DOM based
HTML will allow these style changes. Looking to the future, there is a lot
of need to encapsulate web components from outside influence -- protect
them from conflicts with author choices. I think we need identify some
necessary accessibility holes in web component encapsulation.  We may even
need to identify a protocol for communication.

WCAG WG did not understand the importance of alternative visual
presentation as an accommodation. The result was that access to visual
presentation was left unprotected. Here are some negative consequences:


   - Background images included important content. (Not protecting the need
   for color choice)
   - No semantic markup (Like an ARIA role "semantic-style") indicating
   that style is being used for the author's private semantics.
   ​ ​
   - ​No ARIA support for identifying visually hidden.​
   - ​Screen magnification by itself was considered accessibility support.
   - There was no to fill out forms enlarged that reflowed​

​Contrast that with the case of Meaningful Sequence. This encouraged the
CSS WG to implement Flex Box with the following limitation: *Authors must
use order <https://www.w3.org/TR/css-flexbox-1/#propdef-order> only for
visual, not logical, reordering of content. Style sheets that use order
<https://www.w3.org/TR/css-flexbox-1/#propdef-order> to perform logical
reordering are non-conforming.*

Emphasis was provided by CSS WG.

The lesson here is that access that is protected by normative language
influences decisions and if WCAG doesn't mention it in normative language
then developers will find many innocent ways to interrupt access.

​One last proposal. All style access should be at the element level. There
is good reason to have different styles applied at different levels. We
need to define a new visual semantic for our individuals.

​
​That is too much for now.​


​Wayne​