Re: Fw: Latest updated version of Purpose of Controls

RE: The new introduction to the *Common Purposes for User Interface
Components *section.

While I don't disagree that further disambiguation is a good thing, I have
a minor concern that the introduction introduces the concept of a taxonomy
(Q: do we need to define that in the Glossary?).

The use of a common taxonomy of course is a critical part of achieving
success for this SC, but the actual language doesn't reference anything
about metadata/taxonomies at all, and so as a general question, are we
missing something here?

Should the language of the SC be modified to something like:

In content implemented using markup languages, for each user interface
component that serves a purpose identified in the Common Purposes for User
Interface Components
<http://rawgit.com/w3c/wcag21/purpose_of_controls_changes3/guidelines/index.html#commonpurposes>
section,
that purpose can be programmatically determined using a publicly available
taxonomy.

...and then:

Taxonomy: When used as part of a metadata solution, the taxonomy is the
listing of terms and definitions used to further abstract or define the
element that the metadata term is applied to. Common public metadata
libraries (schemas) include Schema.org, Dublin Core, Personalization
Semantics, and others.


Thoughts?

JF

On Fri, Dec 1, 2017 at 5:52 AM, lisa.seeman <lisa.seeman@zoho.com> wrote:

>
> +1 to the new wording, title and scope and terms in the list of items.
>
> Really good wording Andrew!
>
>
> All the best
>
> Lisa Seeman
>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
>
>
>
>
> ---- On Fri, 01 Dec 2017 07:06:27 +0200 *lisa.seeman<lisa.seeman@zoho.com
> <lisa.seeman@zoho.com>>* wrote ----
>
> Hi
>
> On the call on Wednesday  we resolved the issues with chat help so it was
> excepted.
>
> All the best
>
> Lisa Seeman
>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
>
>
>
>
> ---- On Fri, 01 Dec 2017 06:54:54 +0200 *Michael
> Gower<michael.gower@ca.ibm.com <michael.gower@ca.ibm.com>>* wrote ----
>
> Put this in as a pull request https://github.com/w3c/wcag21/pull/597
>
> Michael Gower
> IBM Accessibility
> Research
>
> 1803 Douglas Street, Victoria, BC
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
>  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> gowerm@ca.ibm.com
> voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034
> ----- Forwarded by Michael Gower/CanWest/IBM on 2017-11-30 08:54 PM -----
>
> From:        Michael Gower/CanWest/IBM
> To:        Andrew Kirkpatrick <akirkpat@adobe.com>
> Cc:        WCAG <w3c-wai-gl@w3.org>
> Date:        2017-11-30 08:43 PM
> Subject:        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*
> <http://rawgit.com/w3c/wcag21/purpose_of_controls_changes3/guidelines/index.html#dfn-user-interface-components>
> 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
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
>  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> 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”.
>
>
>
>
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__rawgit.com_w3c_wcag21_purpose-5Fof-5Fcontrols-5Fchanges3_guidelines_index.html-23identify-2Dcommon-2Dpurpose&d=DwMGaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc&m=RCoI2lSAt-zLWyNtf85vhQ5bwRHVXLzTGalH_rnlPbg&s=zn0v8jM8l2iice255fTfcqbGwljQgABKWW8jg2QdtO4&e=>*http://rawgit.com/w3c/wcag21/purpose_of_controls_changes3/guidelines/index.html#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
>
>
>
>
>
>
>


-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion