W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2017

RE: Proposal for support personlization AA from John, Chris, Jan and myself

From: White, Jason J <jjwhite@ets.org>
Date: Thu, 20 Jul 2017 13:04:56 +0000
To: David MacDonald <david100@sympatico.ca>, Chris McMeeking <chris.mcmeeking@deque.com>
CC: Alastair Campbell <acampbell@nomensa.com>, John Foliot <john.foliot@deque.com>, lisa.seeman <lisa.seeman@zoho.com>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>
Message-ID: <BN6PR07MB3457A88C5197BE1B83CB966DABA70@BN6PR07MB3457.namprd07.prod.outlook.com>

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Thursday, July 20, 2017 4:31 AM

I don't think "consistency" is a new concept in 2.1.

3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)
​In this case "identification" is used instead of "purpose"​.  At the very least there is
​so much
 overlap, that they would probably have to be merged after August.
[Jason] It seems clear that we’re already seeing differences of opinion (perhaps implicitly) regarding what must be programmatically determined under the new proposal. I agree that, on some interpretations, there is overlap with 3.2.4.
Under the proposal currently before us, “conventional controls” (perhaps better stated as “conventional user interface components” for consistency with the remainder of WCAG) are defined in terms of a list of functions. I think the definition needs to be clarified and that there are ambiguities, as well as potential internationalization concerns, but I won’t digress into that territory for now.
One way of characterizing the requirement is to say that which function on the list is performed by a given UI component can be programmatically determined. That is, for example, if I include a link to a home page (where a link to a home page is one of the controls explicitly included in the list), then the fact that it’s a link to a home page cmust be able to be programmatically determined, on this view of the proposal. There seem to be other views of the proposal whereby “purpose” requires or allows for more, or something other, than programmatic determination of what the control does by reference to the list of conventional controls. On those interpretations, a label or description of what the UI component does would qualify as meeting the success criterion.
I think the narrower interpretation is closer to what Lisa, at least, has been advocating in recent meetings – that the AT must be able to traverse the page and unambiguously identify any controls that belong on the list of “conventional” controls according to the definition.
The lack of clarity in the proposal which can be gleaned from the subsequent mailing list discussion indicates that more work is needed to refine and define the idea.


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.

Received on Thursday, 20 July 2017 13:05:34 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:15 UTC