RE: Question on techniques for Identify Common Purpose

From: Jonathan Avila [mailto:jon.avila@levelaccess.com]
Sent: Tuesday, February 13, 2018 9:04 AM

If the div is an input that uses contentEditable or some other type of input control like a birthday chooser, etc. that falls as input and has a mapped purpose in autocomplete values of 5.2 then it would need to define the purpose - but the autocomplete attribute would not be appropriate.  I'd imagine you would need to define the purpose programmatically via techniques related to schema.org - otherwise if it is not be input then it would not fall under this SC at level aA.
[Jason] However, techniques related to the use of metadata to specify purpose using vocabulary mapped to HTML5 autocomplete tokens are not accessibility-supported yet. The user won't benefit, whereas they arguably will in some cases if the HTML autocomplete attribute is used on a standard form field. This may be enough to satisfy Candidate Recommendation exit criteria in connection with accessibility support, but it can hardly be regarded as a satisfactory situation either, as the benefit to the user (in so far as there is one) only accrues if HTML autocomplete is chosen as the implementation mechanism.

________________________________

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.

________________________________