Re: Latest updated version of Purpose of Controls

1) There is no language in the the Common Purposes of User Interface 
Components introduction clarifying that these are just conceptual terms 
and not keywords.

I think there must be clarifying language of some sort in the introduction 
text, or implementers are going to be very confused. I also thought that 
since introductory language was never reviewed on the call and needed some 
editorial work, I would make a first  pass:


"This section contains a listing of some common user interface component 
purpose terms. The terms below are not keywords which must be used, but 
instead represent purposes that must be captured in the taxonomy adopted 
by a website. Where applicable, authors mark up controls with the chosen 
taxonomy to indicate the semantic purpose. This provides the potential for 
user agents and assistive technologies to apply personalized presentations 
that can enable more people to understand and use the content." 

2) As well, not sure why "Chat help" is not marked at risk since it had 
the same survey results as many that were. Can we at least make it "Get 
support" so that it both does not overlap with "help," and is not so bound 
to one delivery system for support?

Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:   Andrew Kirkpatrick <akirkpat@adobe.com>
To:     WCAG <w3c-wai-gl@w3.org>
Date:   2017-11-30 12:26 PM
Subject:        Latest updated version of Purpose of Controls



On the call we decided to call it “Identify Common Purpose”.
 
http://rawgit.com/w3c/wcag21/purpose_of_controls_changes3/guidelines/index.html#identify-common-purpose

 
If there are any changes we need consensus by 11:30 ET tomorrow.
 
Thanks,
AWK
 
Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe 
 
akirkpat@adobe.com
http://twitter.com/awkawk