Re: Combine 79, 78, and 74 SCs? (was Re: Mechanism Disclaimer)

+1 with removal of "those". Not needed. 😀

> On Jan 22, 2017, at 7:23 PM, David MacDonald <david100@sympatico.ca> wrote:
> 
> A little tweak so that its not an all or nothing SC that allows authors to ignore it if the Browser doesn't allow ALL those modifications...
> 
> For those web technologies that allow user agents to change *any or all* of the following: 
> - foreground and background colors, 
> - font family​, 
> - spacing between characters, words, lines, or paragraphs, 
> nothing is done in the content to prevent these modifications. 
> 
> Cheers,
> David MacDonald
>  
> CanAdapt Solutions Inc.
> Tel:  613.235.4902
> LinkedIn 
> twitter.com/davidmacd
> GitHub
> www.Can-Adapt.com
>   
>   Adapting the web to all users
>             Including those with disabilities
> 
> If you are not the intended recipient, please review our privacy policy
> 
>> On Sun, Jan 22, 2017 at 6:04 PM, Katie Haritos-Shea GMAIL <ryladog@gmail.com> wrote:
>> +1. I like it!
>> 
>>  
>> 
>> ​​​​​* katie *
>> 
>>  
>> 
>> Katie Haritos-Shea 
>> Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
>> 
>>  
>> 
>> Cell: 703-371-5545 | ryladog@gmail.com | Oakton, VA | LinkedIn Profile | Office: 703-371-5545 | @ryladog
>> 
>> NOTE: The content of this email should be construed to always be an expression of my own personal independent opinion, unless I identify that I am speaking on behalf of Knowbility, as their AC Rep at the W3C - and - that my personal email never expresses the opinion of my employer, Deque Systems.
>> 
>>  
>> 
>> From: David MacDonald [mailto:david100@sympatico.ca] 
>> Sent: Sunday, January 22, 2017 3:32 PM
>> To: Gregg C Vanderheiden <greggvan@umd.edu>; Jason J White <jjwhite@ets.org>
>> Cc: GLWAI Guidelines WG org <w3c-wai-gl@w3.org>; Jonathan Avila <jon.avila@ssbbartgroup.com>; public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
>> Subject: Re: Combine 79, 78, and 74 SCs? (was Re: Mechanism Disclaimer)
>> 
>>  
>> 
>> I think it's getting better... this seems the easiest to understand 
>> 
>>  
>> 
>> For those web technologies that allow user agents to change the foreground and background colors, font family​, ​or the spacing between characters, words, lines, or paragraphs, nothing is done in the content to prevent these modifications. 
>> 
>>  
>> 
>>  
>> 
>> On Sun, Jan 22, 2017 at 2:41 PM Gregg C Vanderheiden <greggvan@umd.edu> wrote:
>> 
>>  
>> 
>> On Jan 22, 2017, at 2:26 PM, White, Jason J <jjwhite@ets.org> wrote:
>> 
>>  
>> 
>> Features of the technologies relied upon by the content are not used in a way that would restrict the ability, if any, of user agents to change foreground and background colors, font family​, ​or the spacing between characters, words, lines, or paragraphs
>> 
>>  
>> 
>>  
>> 
>> I think this is the best of the lot — but it still is hard to interpret if you don’t know in advance what it is trying to get at -  AND why it is written with so many clauses…. 
>> 
>>  
>> 
>>  
>> 
>> Here is an explanation (as far as I understand it) for what we are saying and why. 
>> 
>>  
>> 
>> Not all technologies have a way for users to change the foreground and background colors, font family​, ​or the spacing between characters, words, lines, or paragraphs.  But for those that do, such as HTML for text content, the Author should not use features in a way that would prevent these modifications. 
>> 
>>  
>> 
>> Hmmmm
>> 
>>  
>> 
>> how about.
>> 
>> aaFor those web technologies that allow user agents to change the foreground and background colors, font family​, ​or the spacing between characters, words, lines, or paragraphs, nothing is done in the content to prevent these modifications. 
>> 
>>  
>> 
>> OR 
>> 
>> Web content technologies are not used in a way that would prevent users from changing the foreground and background colors, font family​, ​or the spacing between characters, words, lines, or paragraphs, where the technologies used can allow such changes. 
>> 
>>  
>> 
>>  
>> 
>> g
>> 
>