- From: lisa.seeman <lisa.seeman@zoho.com>
- Date: Tue, 18 Jul 2017 17:34:29 +0300
- To: White <jjwhite@ets.org>
- Cc: "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>, "Alastair Campbell" <acampbell@nomensa.com>, "public-cognitive-a11y-tf" <public-cognitive-a11y-tf@w3.org>
- Message-Id: <15d561f2a10.113acdef957659.1768465063724143431@zoho.com>
Hi Jason This is an important question on why 3.3.6 does not meet the needs in the undo SC. Firstly it does covers were the user to submit information data. This does not touch on the case were you touched something by accident and your page or context has gone. your were typing in a text box and now you continue typing and it is going somewhere else. Whilst anoying for everyone, you need to be able to work out how to get back to continue. Many people in COGA can not work out how to get back. Think of someone with mild dementia when the context changes in a way they did not expect. They then need help. If the back function works consistently, a person (who is used to computers) can often carry on (even with stage 1 or 2 of dementia -stages that can last years). Secondly some of the options in 3.3.6 and 3.3.4 are often not a solution by people from COGA usergroups. For example there is a specific techniques (g164) where the Web content would tell the user how long the cancellation period is after submitting the form and what the procedure would be to cancel the order. The cancellation procedure may not be possible online. It may, for instance, require written notice be sent to an address listed on the Web page. Typically this process can not be done independently by a lot of our users as there is not restriction of the complexity of this process. All the best Lisa Seeman LinkedIn, Twitter ---- On Mon, 17 Jul 2017 20:29:39 +0300 White<jjwhite@ets.org> wrote ---- Also, we should consider whether promoting 3.3.6 to level AA would be a preferable solution to the current proposal, or whether it would be better to carry forward a proposal that is similar to 3.3.4, but which applies to a greater range of application scenarios. From: White, Jason J [mailto:jjwhite@ets.org] Sent: Monday, July 17, 2017 11:16 AM To: lisa.seeman <lisa.seeman@zoho.com>; W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>; Alastair Campbell <acampbell@nomensa.com>; public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org> Subject: RE: new wording for Undo From: lisa.seeman [mailto:lisa.seeman@zoho.com] Sent: Sunday, July 16, 2017 12:50 PM UNDO: Users can undo actions, return to the previous context and correct data entry without loss of non-dependent data except when: [Jason] Is there a definition of “non-dependent” (should that be “independent” or something more descriptive)? data? Is it always clear what constitutes the previous context? I’m not sure this is testable. It also isn’t apparent whether the term “the previous context” (implying that there’s only one at any given time) is meant to have this implication, but that’s what the proposal above says. allowing the user to undo an action or maintaining data may cause harm such as adding risk to the user privacy or security; [Jason] Is this reliably testable, or instead, should the users be required to “opt in” to this functionality? the user has confirmed an action; allowing the user to undo an action may interfere with the essential function of the content; [Jason] “may” seems rather vague here. Shouldn’t this be expressed in terms of “invalidating the activity”, as is done elsewhere in WCAG? the action can no longer be controlled by the site; [Jason] The site never controls the action, so I don’t know what this means. As it stands, it’s probably not reliably testable and it’s very vague. It should be removed or clarified. the user has been idle for 24 hours. 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. 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 Tuesday, 18 July 2017 14:35:01 UTC