W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2018

Re: Issue 948 SC 1.3.5 Identify Input Purpose - autocomplete technique VS Privacy/Security

From: David MacDonald <david100@sympatico.ca>
Date: Tue, 5 Jun 2018 17:22:59 -0400
Message-ID: <CAAdDpDZyFyTMDE8Y9YaykCDL_LDt4kdemQcwmUfpYX3frkZgKA@mail.gmail.com>
To: Alastair Campbell <acampbell@nomensa.com>
Cc: John Foliot <john.foliot@deque.com>, "lisa.seeman" <lisa.seeman@zoho.com>, WCAG <w3c-wai-gl@w3.org>
I'm wondering if we can provide a second set of techniques where using the
programmatically determinable accname (<label for>, aria-label etc.) for
common fields including:

- First Name
- Last Name
- Middle Name
- Address
- Phone Number
- etc...

 AT should be able to identify these common fields if they are labelled om
a way that makes its purpose obvious.

See this Twitter thread.
https://twitter.com/davidmacd/status/1002848685997416448


Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Tue, Jun 5, 2018 at 4:16 PM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi everyone (and particularly John & Lisa),
>
>
>
> I’d like to run a proposed response past the group before posting to
> github (and notifying the commenter before the group gets a chance to
> review).
>
>
>
> https://github.com/w3c/wcag21/issues/948
>
>
>
> I’d summarise the core issue as: using autocomplete/autofill could be an
> issue for privacy/security for people using shared devices (e.g. family
> computer), and autcomplete shouldn’t be proposed as a technique to fulfil
> it.
>
>
>
> You can read the back and forth on the thread, but I’m proposing the
> response is:
>
>
> The working group have considered the security and privacy aspects of
> this, and whilst it must be acknowledged there may be some circumstances in
> which a user would not want fields identified and auto-filled, the working
> group feel the benefits outweigh the risks.
>
>
>
> Mitigating factors include:
>
>
>
> - This is functionality that is already available in user-agents, and used
> by some websites already.
>
> - It is something that must be enabled within the user-account and browser
> of the device used.
>
> - People can use various privacy features if that is a requirement.
>
>
>
> Currently the autocomplete attribute (for autofill) is the best supported
> method, so that will be the first technique provided.
>
>
>
> Personally, I don’t see it as an issue, but I’d appreciate a review from
> others familiar with autocomplete.
>
>
>
> Kind regards,
>
>
>
> -Alastair
>
>
Received on Tuesday, 5 June 2018 21:23:26 UTC

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