Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Current versions of SC and Definitions
Users are provided with the ability to undo an action and to correct mistakes such that:
Principle 3, Guideline 3.3.3
The intent of this Success Criterion is to allow users to easily undo steps in a process at any point in the process, and not just at the confirmation prior to submission.
This is especially important for people with learning and cognitive disabilities, who make many more mistakes than most people. They may realize their mistake at any point and need to correct it. For example, a work group member was booking a trip online. Due to their dyslexia, they selected a destination with a similar spelling to their intended destination. They noticed this at a later step when trying to book a hotel. The user needs to correct the mistake then, and not wait for the confirmation just prior to submission. If the user is not able to check for and correct a mistake immediately, they run the risk of forgetting their mistake later on or abandoning the whole process.
It is vital for people who are prone to making mistakes, that data they have entered correctly is not deleted when undoing a mistake. Each time the user has to reenter data, there is a new chance for new mistakes to occur. Therefore, if the user has to redo a form each time they correct one section, it can become impossible to submit all the data correctly.
For example, when booking a trip a user can make a mistake at many points, such as incorrect dates, location, hotel, flight, etc. If the user typically makes one or two mistakes in the process, they need to take breaks and double check their work a few times. If a detail is incorrect, such as booking a hotel that is too far away from an event, they must be able to fix that detail. However, if they need to redo the whole process, then when they reenter the other data they are likely to make another mistake. For example, they might invert the dates. If they need to redo the process again from the beginning a third time, they will be tired and probably make more mistakes. Hence the task becomes impossible.
Those who have difficulties accurately entering information correctly or perceiving errors will need to undo incorrect actions. It allows all users, but especially those with learning and cognitive disabilities, to re-check data entered and make necessary changes if errors have occurred.
Undo can simplify actions, reduce fear of failure, and make it possible for users to complete their task.
The benefits of having data remaining intact, even if submitted in error, allows for correction for users with poor short term memory and for those with learning disabilities.
It is part of the COGA theme to prevent the user from making mistakes and make it easy to correct mistakes when they do occur.
Issue Paper: Online Payments
In a process which requires a user to enter data, confirm that at every step all of the following are true for the user:
working groups notes (optional)
Conceptually, would you say this is related /extends 3.3.6 Error Prevention (All), but at AA level? Does it replace/cross over with 3.3.4 Error Prevention (Legal, Financial, Data) (also at AA).
If an authors satisfied this proposed SC at AA, would they automatically be passing 3.3.4 AA and 3.3.6 AAA ?
added a commit
May 12, 2017
When we broke apart issue #33, a portion overlapped with this issue. The concern Mike Gower and I have with current wording is that it may be too broad, requiring sites to retain actions and data everywhere. . We suggest the following title and wording which has a much more targeted scope. @lseeman has made an initial review of this.
Some contribution about wording.
Undo an action is singular here while as with “correct mistakes” I expect “undo actions…” (plural)
Better to add where there should be “at least one clearly labeled action” (there may be step numbers and back/next buttons present)
Will it be mandatory or will edit do in overview page?
Shouldn’t it be “and/or” instead of “and”
Is there a definition for what is right and wrong for “clearly”?
Also here the term unwanted is a bit flaky, what is unwanted?
At the Description I see the text “easily undo steps” but I guess it must be “easily undo actions in a step”
At Testability there is “In a process which requires “. I can think of steps where the data is not mandatory but optional.
The bullet points at Testability mention the clearly labeled action in multiple ways. The first is to go back steps, the other to repair information. Then again to get back to the previous step. Refinement of the term would be pleasant as this may cause confusion.
What does the ‘replaced’ here means? Filled in again…?
As @rachaelbradley suggested in her comment I see the benefit of a more targeted scope.
Why only transaction here? The need for error correction is broader and limiting the scope this much seems to strict and also the SC text “Error correction” is not appropriate for only transactions.
Also here the and/or would fit better.
Should be to correct “errors” (as this is the text of the SC)
Is this where the error is or where they identified it… (could be they identified it at step 3 while the error is at step 1)
@jake-abma I've incorporated your comments and corrections into account in the new SC text, with the exception of the limitation to transactions. We have been struggling with appropriate wording for this SC and #33. We need to exclude situations such as IM but leave an appropriately useful scope. Recommendations would be appreciated.
New potential wording (uploads to GIT are failing).
Where users are required to enter data to complete a transaction, a mechanism is provided to undo an action or correct an error and return to the place where they identified the error through at least one clearly labeled action without data loss, except when the data loss is part of the correction.
Changes to the SC text, based in survey and comment https://www.w3.org/2002/09/wbs/35422/COGA_undo/results
-The user can return to the location they were at, prior to the change in context, via visible or clearly labeled controls without unwanted loss of data unless the data loss is part of the correction; or
-Where allowing the user to undo an action or maintaining data may cause harm such as adding risk to the user privacy or security.
Just so it isn't lost, I suggested on the call:
That is not perfect (e.g. what's an action?), but I thought it would help to distill down first, then build up to fill the gaps.
NB: I thought that data loss could be part of the correction that you wanted, therefore simplified it a bit.
I think we need to say some context. Perhaps leverage the "steps in a process" language from the conformance section. Also revising "unwanted" adjective.