RE: Identify Common Purpose - resolving issues

“In content implemented using technologies with support for identifying the expected meaning for elements, for each element that has a purpose that maps to any of the [link]list of common input fields,  the meaning of the element can be programmatically determined.”

+1 looks identical to my recently suggested text :-) 

-----Original Message-----
From: Alastair Campbell [mailto:acampbell@nomensa.com] 
Sent: woensdag 17 januari 2018 10:45
To: Abma, J.D. (Jake) <Jake.Abma@ing.nl>; Andrew Kirkpatrick <akirkpat@adobe.com>; WCAG <w3c-wai-gl@w3.org>
Subject: Re: Identify Common Purpose - resolving issues

Jake wrote:
> I see a limitation in “for each user-specific input field” if we want to expand this SC to also apply to NON user-specific input fields (or even links / buttons)
 
If we have the list in WCAG, we can use the line at the top of the appendix (there now) to indicate the user-aspect, we can remove it from the SC text.


David wrote:
> ​Now if  we  ​want to address Jake's issue we could go with a variation of his text
> 
> “In content implemented using technologies with support for identifying the expected meaning for elements, for each user-specific element that has a purpose that maps to any of the [link]list of common input fields,  the meaning of the element can be programmatically determined.”

I’d be happy with that, and combing those points would leave:

“In content implemented using technologies with support for identifying the expected meaning for elements, for each element that has a purpose that maps to any of the [link]list of common input fields,  the meaning of the element can be programmatically determined.”
(Removing user-specific)

Cheers,

-Alastair


-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------

Received on Wednesday, 17 January 2018 09:51:35 UTC