Re: Glossary entry for Essential. WAS: Should the boxes around blocks of text in the FPWD have Sufficient contrast under the new SC. WAS: Re: CFC: Publish WCAG 2.1 FPWD

There was just one instance of a definition pointer to the WCAG 2.0 
spec. I consider it editorial on porting the proposed SC into the draft, 
so I fixed it.

I also added a clause in the introduction to say glossary entries are 
also proposed. The relevant change now reads "This draft also includes 
proposed success criteria, and supporting glossary additions, that have 
not yet been approved by the Working Group. "

This is in the name of quick edits that hopefully don't threaten the 
publication consensus. More substantial changes could be explore post 
publication.

Michael


On 2/23/2017 11:43 AM, Hakkinen, Mark T wrote:
>
> I noticed there are also two versions of the glossary entry for 
> “essential” linked in the 2.1 draft, with some instances of 
> “essential” pointing to the proposed glossary definition (which 
> includes two new examples), and some pointing to the original WCAG 2.0 
> definition.
>
> For example, existing 1.4.5 points to the new, within document 
> glossary entry and proposed 1.4.14 points to the original glossary 
> entry in WCAG 2.0 (out of document).
>
> This may be true for other entries, but I haven’t checked.
>
> In looking at the proposed entry for essential examples, they seem 
> incomplete at this stage.   I want to +1 Jason White’s earlier comment 
> in the FPWD CFC thread regarding the need in the FPWD to emphasize 
> that glossary entries are present under the same cautionary terms as 
> the Proposed SC.
>
> Mark
>
> *From:*David MacDonald [mailto:david100@sympatico.ca]
> *Sent:* Thursday, February 23, 2017 9:09 AM
> *To:* Gregg Vanderheiden RTF <gregg@raisingthefloor.org>
> *Cc:* Michael Gower <michael.gower@ca.ibm.com>; Alastair Campbell 
> <acampbell@nomensa.com>; Mike Elledge <melledge@yahoo.com>; 
> w3c-waI-gl@w3. org <w3c-wai-gl@w3.org>
> *Subject:* Re: Should the boxes around blocks of text in the FPWD have 
> Sufficient contrast under the new SC. WAS: Re: CFC: Publish WCAG 2.1 FPWD
>
> >I cringe whenever I see  ‘essential’ in a rule.
>
> oh oh... there are a lot of "essential" instances in SCs There are 3 
> SCs with it in WCAG 2, and 9 in the proposed SCs for 2.1. This would 
> be a good time to discuss alternatives.
>
> WCAG 2
> =============
>
> 1.4.9 Images of Text (No Exception)§AAA
>
> ​ ​
>
> Images of text are only used for pure decoration or where a particular 
> presentation of text is essential to the information being conveyed.
> 2.2.1 Timing Adjustable
>
> ​ ​
>
> A
>
> ​ ​
>
> Essential exception
> 2.2.3 No Timing§AAA
>
> ​ ​
>
> Timing is not an essential part of the event or activity presented by 
> the content, except for non-interactive synchronized media and 
> real-time events.
>
> ===========================
>
> WCAG 2.1
> 1.4.10A mechanism is available to view content as a single column, 
> except for parts of the content where the spatial layout is essential 
> to the function and understanding of the content.
> 1.4.12 Graphics Contrast
> The visual presentation of graphical objects that are essential for 
> understanding the content or functionality have a contrast ratio of at 
> least 4.5:1 against the adjacent color(s), except for the following:
> 1.4.14 User Interface Component Contrast (Minimum)
> ...
> The visual presentation of essential graphical objects for user 
> interface component(s)
> 2.2.7 Animation from interactionsA
> For significant animations triggered by a user action that is not an 
> essential part of the action, there is a mechanism for the user to 
> pause, stop or hide the animations while still performing the same action.
> 2.6.1 Device Sensors
> All functionality of the content can be operated without requiring 
> specific device sensor information unless the device sensor is 
> essential for the function and not using it would invalidate the 
> activity2.6.2 Orientation§
> 2.6.2 Orientation: Content is not locked to a specific orientation, 
> and functionality of the content is operable in all orientations, 
> except where orientation is essential for use of the content.
> 3.1.7 Plain Language (Minimum) Essential exception: If the writing 
> style is an essential part of the main function of the site, such as a 
> game, a literary work, or teaching new terms.
>
> 3.2.6 Accidental Activation
>
> ​ essential exception:  Timing of activation is essential and waiting 
> for the up-event would invalidate the activity.
> 3.2.7 Familiar design essential Exception: The style is an essential 
> part of the main function of the site, such as for a game
>
>
> Cheers,
> David MacDonald
>
> *Can**Adapt**Solutions Inc.*
>
> Tel:  613.235.4902
>
> LinkedIn
> <http://www.linkedin.com/in/davidmacdonald100>
>
> twitter.com/davidmacd <http://twitter.com/davidmacd>
>
> GitHub <https://github.com/DavidMacDonald>
>
> www.Can-Adapt.com <http://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 <http://www.davidmacd.com/disclaimer.html>
>
> On Thu, Feb 23, 2017 at 6:28 AM, Gregg Vanderheiden RTF 
> <gregg@raisingthefloor.org <mailto:gregg@raisingthefloor.org>> wrote:
>
>         ​- ​
>
>         an alternative
>
>         ​means of visually displaying
>
>          the essential information
>
>         ​ is provided. (e.g., visible text)
>
>     I cringe whenever I see  ‘essential’ in a rule.
>
>     1) there is no way to judge essential
>
>     2) there is a long history of this term being abused by developers
>     to not include things you would judge as essential.
>
>     for example — on phones — only the dial pad is essential.   not
>     being able to look things up in the directory of phone numbers on
>     your phone.  or anything else on your phone.
>
>     on a web page — only the primary function of the page is
>     essential.   all the rest is extra
>
>     etc
>
>     and worse.
>
>     Essential is not objective
>
>
> ------------------------------------------------------------------------
>
> This e-mail and any files transmitted with it may contain privileged 
> or confidential information. It is solely for use by the individual 
> for whom it is intended, even if addressed incorrectly. If you 
> received this e-mail in error, please notify the sender; do not 
> disclose, copy, distribute, or take any action in reliance on the 
> contents of this information; and delete it from your system. Any 
> other use of this e-mail is prohibited.
>
>
> Thank you for your compliance.
>
> ------------------------------------------------------------------------