W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2019

Re: WCAG 2.2 COGA SC Information in Steps Ready For Review Edits

From: David Fazio <dfazio@helixopp.com>
Date: Mon, 4 Nov 2019 15:52:29 +0000
To: Alastair Campbell <acampbell@nomensa.com>
CC: "lwatson@tetralogical.com" <lwatson@tetralogical.com>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Message-ID: <DAFF1795-31D7-42AF-B3E0-D813A4F3AFE3@helixopp.com>
Thanks, Alastair. Yes, I am referring to the specific session. I think it’s important to make that clear distinction, which I may have failed to do well enough. If there is a better way to word it, I’m open to suggestions. 

This message was Sent from my iPhone. Please excuse any typographic errors. 

> On Nov 4, 2019, at 1:11 AM, Alastair Campbell <acampbell@nomensa.com> wrote:
> 
> Hi Léonie, David,
> 
> I think two things are getting confused, autofill (the attribute) and auto-filling in inputs during a session based on previous input from that user.
> 
> Autocomplete/autofill attributes are based on the user's browser, and we settled the security discussion a while ago for the Input Purpose SC: https://github.com/w3c/wcag/issues/407#issuecomment-401418096 
> 
> If a form has a series of steps, and re-asks (or confirms) information from a previous step, that should be attached to the session rather than something the browser fills in. I think this is the technique proposed;.
> 
> Also, if something in an SC doesn't apply if it might be shown whilst in a library, that pretty much applies to any public website, so we'd need to re-think the SC.
> 
> -Alastair
> 
> 
Received on Monday, 4 November 2019 15:52:37 UTC

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