- From: Andrew Kirkpatrick <akirkpat@adobe.com>
- Date: Fri, 1 Dec 2017 15:53:57 +0000
- To: John Foliot <john.foliot@deque.com>, lisa.seeman <lisa.seeman@zoho.com>
- CC: "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>
- Message-ID: <7D7AB0DA-FE1F-4AF8-B720-CA705E192DE9@adobe.com>
John, I think that we have agreement on the SC text already and this would be a problem, but also isn’t really needed because you will need to demonstrate accessibility support anyway. Thanks, AWK Andrew Kirkpatrick Group Product Manager, Accessibility Adobe akirkpat@adobe.com http://twitter.com/awkawk From: John Foliot <john.foliot@deque.com> Date: Friday, December 1, 2017 at 09:17 To: "lisa.seeman@zoho.com" <lisa.seeman@zoho.com> Cc: WCAG <w3c-wai-gl@w3.org>, Andrew Kirkpatrick <akirkpat@adobe.com> Subject: 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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fpurpose_of_controls_changes3%2Fguidelines%2Findex.html%23commonpurposes&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=aFDiP5O4qULSNFjMMEZK2qR2iBICUcaOVQh99Acta8w%3D&reserved=0> 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<mailto: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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fil.linkedin.com%2Fin%2Flisaseeman%2F&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=RpSpit6v4BbkB8fzN3EcVMPfx5tIfTdCoBcYVgfUGJY%3D&reserved=0>, Twitter<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FSeemanLisa&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=zGOyXqodLaKnTEe6Z5tM4VTnR8whGstV6KKU3BR8%2BhM%3D&reserved=0> ---- On Fri, 01 Dec 2017 07:06:27 +0200 lisa.seeman<lisa.seeman@zoho.com<mailto: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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fil.linkedin.com%2Fin%2Flisaseeman%2F&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=RpSpit6v4BbkB8fzN3EcVMPfx5tIfTdCoBcYVgfUGJY%3D&reserved=0>, Twitter<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FSeemanLisa&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=zGOyXqodLaKnTEe6Z5tM4VTnR8whGstV6KKU3BR8%2BhM%3D&reserved=0> ---- On Fri, 01 Dec 2017 06:54:54 +0200 Michael Gower<michael.gower@ca.ibm.com<mailto:michael.gower@ca.ibm.com>> wrote ---- Put this in as a pull request https://github.com/w3c/wcag21/pull/597<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag21%2Fpull%2F597&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=kaU%2BnRbqwhmaxUt1%2B1rjq8G3X3%2FfzpigfDGRbo1%2FhH4%3D&reserved=0> Michael Gower IBM Accessibility Research 1803 Douglas Street, Victoria, BC <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaps.google.com%2F%3Fq%3D1803%2BDouglas%2BStreet%2C%2BVictoria%2C%2BBC%2B%25C2%25A0V8T%2B5C3%26entry%3Dgmail%26source%3Dg&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=bqtSW3nVAhwfVIq0pF8LX66r5jjZ7l7MUJVUfb1MyCo%3D&reserved=0> V8T 5C3<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaps.google.com%2F%3Fq%3D1803%2BDouglas%2BStreet%2C%2BVictoria%2C%2BBC%2B%25C2%25A0V8T%2B5C3%26entry%3Dgmail%26source%3Dg&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=bqtSW3nVAhwfVIq0pF8LX66r5jjZ7l7MUJVUfb1MyCo%3D&reserved=0> gowerm@ca.ibm.com<mailto:gowerm@ca.ibm.com> voice: (250) 220-1146<tel:(250)%20220-1146> * cel: (250) 661-0098<tel:(250)%20661-0098> * fax: (250) 220-8034<tel:(250)%20220-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<mailto:akirkpat@adobe.com>> Cc: WCAG <w3c-wai-gl@w3.org<mailto: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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fpurpose_of_controls_changes3%2Fguidelines%2Findex.html%23dfn-user-interface-components&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=56ij7sbIXNLr6gmVBvcbMLIZfioWD2DIqpAimw3haHM%3D&reserved=0> 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://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaps.google.com%2F%3Fq%3D1803%2BDouglas%2BStreet%2C%2BVictoria%2C%2BBC%2B%25C2%25A0V8T%2B5C3%26entry%3Dgmail%26source%3Dg&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=bqtSW3nVAhwfVIq0pF8LX66r5jjZ7l7MUJVUfb1MyCo%3D&reserved=0> V8T 5C3<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmaps.google.com%2F%3Fq%3D1803%2BDouglas%2BStreet%2C%2BVictoria%2C%2BBC%2B%25C2%25A0V8T%2B5C3%26entry%3Dgmail%26source%3Dg&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=bqtSW3nVAhwfVIq0pF8LX66r5jjZ7l7MUJVUfb1MyCo%3D&reserved=0> gowerm@ca.ibm.com<mailto:gowerm@ca.ibm.com> voice: (250) 220-1146<tel:(250)%20220-1146> * cel: (250) 661-0098<tel:(250)%20661-0098> * fax: (250) 220-8034<tel:(250)%20220-8034> From: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> To: WCAG <w3c-wai-gl@w3.org<mailto: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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fpurpose_of_controls_changes3%2Fguidelines%2Findex.html%23identify-common-purpose&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=eNm4oCxxhOiUQhcVPdfNwpSgD%2BRjh2D3P6a1Tbzyq0s%3D&reserved=0> 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<mailto:akirkpat@adobe.com> http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7Cakirkpat%40adobe.com%7C177d8e87df3142cd60c608d538c63542%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477346303569506&sdata=g4kFDGW3YK7fNC0JPiuUcusXOVLymF8ei97ykETkd8w%3D&reserved=0> -- John Foliot Principal Accessibility Strategist Deque Systems Inc. john.foliot@deque.com<mailto:john.foliot@deque.com> Advancing the mission of digital accessibility and inclusion
Received on Friday, 1 December 2017 15:54:27 UTC