Re: Proposing a Technique for 1.3.5 Identify Input Purpose


Should we be recommending a technique that is only valid for English?

It could work globally if it implies that cognitive AT would be parsing the AccName to determine purpose, and to make it work the AT would know the content language, and look in its own lexicon for a localized equivalent for the 5.2 autocomplete tokens.  I think that could get messy.

Also might we see content authors in non-English languages adding an English text fragment in non-English labels in an effort to comply?


From: David MacDonald <>
Sent: Sunday, June 24, 2018 4:51 PM
Subject: Proposing a Technique for 1.3.5 Identify Input Purpose

I've created a proposed technique for 1.3.5 which would allow the ACCNAME to contain a (case insensitive) string identical to the HTML 5.2 corresponding autocomplete token (or a string which contains the entire token within its string).<>

I took the idea from our new SC Label in Name (2.5.3), where the ACCNAME contains the string of the label.<>

This will provide some flexibility for authors who are creating simple contact forms in English, without compromising programmatic determination for assistive technologies, it provides another means to meet the SC,  for those with security concerns associated with autocomplete.

David MacDonald

CanAdaptSolutions Inc.

Mobile:  613.806.9005



  Adapting the web toall users

            Including those with disabilities

If you are not the intended recipient, please review ourprivacy policy<>


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 Sunday, 24 June 2018 23:03:55 UTC