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

I thought we favored Alastair’s latest proposal: “the conventional name of conventional controls can be programmatically determined”.
I would adjust the text slightly:
“The conventional name of every conventional user interface component can be programmatically determined”.
Where “conventional user interface component” requires a definition based on a list that we already have, but which would need to be made more precise and refined in detail. “Conventional name” is a localized name drawn from a publicly available controlled vocabulary that associates a name with each conventional user interface component.

As mentioned in the informal meeting, I have ongoing reservations about this proposal that can only be addressed by working through all of the definitional details. It isn’t done and ready to be approved until all of the details are filled in, but inclusion in a public working draft for external review doesn’t require all of the problems to be solved in advance, as Michael Cooper has rightly insisted. I also agree with John that the details of text are best worked out by e-mail rather than in a meeting. I also think this proposal raises internationalization issues (especially the definitions that are yet to be worked out in detail), and that extensive horizontal review will be needed if this goes into a specification.

From: Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
Sent: Friday, July 21, 2017 12:52 PM
To: lisa.seeman <lisa.seeman@zoho.com>; W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
Subject: Re: Alastair, Jan, Jason , myself and John have an updated version of

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


________________________________

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.

________________________________