Re: Alastair, Jan, Jason , myself and John have an updated version of

Re: Jason’s comment, whatever the language people think is the right current language, can someone make sure that the Support Personalization issue (https://github.com/w3c/wcag21/issues/6) is updated so that the right language appears at https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/guidelines/#support-personalization


If no-one can do that, can someone send me the final final  language and I’ll update it so I can send the survey out.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com
http://twitter.com/awkawk


From: John Foliot <john.foliot@deque.com<mailto:john.foliot@deque.com>>
Date: Friday, July 21, 2017 at 13:03
To: Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>>
Cc: "lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>" <lisa.seeman@zoho.com<mailto:lisa.seeman@zoho.com>>, WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: Re: Alastair, Jan, Jason , myself and John have an updated version of

Hi Andrew,

  *   re: At AA - good catch, yes, "purpose" is important here.

  *   re: At AAA - I think that 'purpose' and 'function' are synonymous here, but agree that we should be consistent.

  *   re: 3.3.5 to AA - we batted this around a bit, and I for one am open to alternative solutions. It felt clear to us that this was certainly in the 3.3.x realm, and whether it is a modification of 3.3.2 and 3.3.5, or some other similar editorial change to both of those SC, or introduce yet another new SC, we've left that open for now (at least, that was *my* take-away).

That said, we all feel we've made some serious headway here, and we hope that the larger WG can rally behind this and get this into the Draft before the August deadline.

JF

On Fri, Jul 21, 2017 at 11:52 AM, Andrew Kirkpatrick <akirkpat@adobe.com<mailto:akirkpat@adobe.com>> wrote:
At AA

Purpose of controls: In content implemented using mark-up languages, conventional controls can be programmatically determined. (AA)

AWK: I think that you might mean "Purpose of controls: In content implemented using mark-up languages, the purpose of conventional controls can be programmatically determined. (AA)"

At AAA
we would like

In content implemented using markup languages, the function and context information of controls and regions can be programmatically determined using a publicly available vocabulary.

AWK: So do we need to define “purpose” in AA and “function” and “context information” for AAA? Why are these different?

also
Upgrade and change 3.3.5 to AA -  Context-sensitive hel<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FTR%2FUNDERSTANDING-WCAG20%2Fminimize-error-context-help.html%23context-sensitivehelpdef&data=02%7C01%7C%7Cd2cb3f0a1c64465a394408d4d0549d58%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636362509213230977&sdata=X5PQaBpBn5nEpyo4fvtjUhSb7P3rWjecT4rwpEqeRMQ%3D&reserved=0>p is available for non-conventional controls  (this would included having a explanation)

AWK: This is a constrained version of 3.3.5, so I would think that we are keeping the AAA one and adding a similar but more tightly scoped one at AA.

AWK




--
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