- From: White, Jason J <jjwhite@ets.org>
- Date: Mon, 26 Aug 2019 18:35:09 +0000
- To: David Fazio <dfazio@helixopp.com>, Jonathan Avila <jon.avila@levelaccess.com>, "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
- CC: lisa.seeman <lisa.seeman@zoho.com>, Rachael Bradley Montgomery <rachael@accessiblecommunity.org>
Interestingly, if I'm reading the proposal correctly, a password confirmation field in a Web-based form would fail. However, its purpose is, in part, to determine whether the user remembers the password and entered it correctly in the original password field. I didn't notice anything in the proposal that would allow for a password confirmation even if the browser (or an extension) fills it in automatically - along the lines of "a mechanism is available...". -----Original Message----- From: David Fazio <dfazio@helixopp.com> Sent: Friday, August 23, 2019 4:29 PM To: Jonathan Avila <jon.avila@levelaccess.com>; Patrick H. Lauke <redux@splintered.co.uk>; w3c-wai-gl@w3.org Cc: lisa.seeman <lisa.seeman@zoho.com>; Rachael Bradley Montgomery <rachael@accessiblecommunity.org> Subject: Re: WCAG 2.2 SC Do Not Rely On User Memory Draft I will insert those comments in the draft, and open it up to discussion in the COGA TF next week. On 8/23/19, 11:56 AM, "Jonathan Avila" <jon.avila@levelaccess.com> wrote: I agree, let's just add it to the understanding to clear up any confusion. Jonathan -----Original Message----- From: Patrick H. Lauke <redux@splintered.co.uk> Sent: Friday, August 23, 2019 2:02 PM To: w3c-wai-gl@w3.org Subject: Re: WCAG 2.2 SC Do Not Rely On User Memory Draft CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 23/08/2019 17:32, David Fazio wrote: > I added in a reference to 3.3.2 Labels of Instructions. I don't think we should omit it just because it constitutes a failure of another S.C. The reason being is that this gives "cause" to users with cognitive disabilities. "Cause" is a legal standard that must be met, demonstrating that an individual has been harmed, in order to bring forth a lawsuit. A user who is not blind, and does not rely on braille cannot sue a compant for not providing braille materials, because that does not harm them. Although it would harm a person that is blind. If this aspect (of the reliance on placeholder) is already a failure of 3.3.2, why not add that particular aspect/example - with specific reference to users with cognitive disabilities - directly in 3.3.2's understanding/techniques? You don't have to have separate SCs covering the same aspects for different audiences/users. P -- Patrick H. Lauke https://nam01.safelinks.protection.outlook.com/?url=www.splintered.co.uk&data=02%7C01%7Cjjwhite%40ets.org%7C89fc6d6b50e74cf540b208d72808b0b0%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637021890105055212&sdata=nyLGMDuai56qLKyNOJTOHtE%2Fnbn27vG64oKtgVEB3JI%3D&reserved=0 | https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpatrickhlauke&data=02%7C01%7Cjjwhite%40ets.org%7C89fc6d6b50e74cf540b208d72808b0b0%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637021890105055212&sdata=GYl2fKX5LE6NoxNMgAlHF0adVzwa%2Fm17gJxTRap3rhs%3D&reserved=0 https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&data=02%7C01%7Cjjwhite%40ets.org%7C89fc6d6b50e74cf540b208d72808b0b0%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637021890105055212&sdata=K39O%2F1FK6IG5lEcE6l8%2FVYzjwMErTggS9XbqJdZiRI0%3D&reserved=0 | https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&data=02%7C01%7Cjjwhite%40ets.org%7C89fc6d6b50e74cf540b208d72808b0b0%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637021890105055212&sdata=cd1Bi4fZMnfbJAuZRysegCKmpErioX9Zlp2RbPNRk68%3D&reserved=0 twitter: @patrick_h_lauke | skype: patrick_h_lauke ________________________________ 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 Monday, 26 August 2019 18:35:46 UTC