Timeline for Are users more likely to make mistakes when functionality is easier to access?
Current License: CC BY-SA 4.0
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Feb 22, 2023 at 8:41 | history | suggested | unforgettableidSupportsMonica | CC BY-SA 4.0 |
1. Improving title. 2. Improving post contrast; please see the WCAG contrast guideline.
|
| Feb 21, 2023 at 18:53 | comment | added | Glorfindel | @unforgettableidSupportsMonica I rejected your previous edit because it changed too much - I don't doubt the question can be improved, but it almost looked like I didn't write it. The current edit is acceptable, but 1) if you improve the title, why not the emphasized sentence which is identical? 2) I've asked what the appropriate way is to emphasize the central sentence of a question - the blockquote used to stand out more when I asked this question, but I'm waiting for the best solution w.r.t. accessibility. | |
| Feb 20, 2023 at 19:44 | review | Suggested edits | |||
| S Feb 22, 2023 at 8:41 | |||||
| Feb 20, 2023 at 14:40 | review | Suggested edits | |||
| Feb 20, 2023 at 15:01 | |||||
| Jan 19, 2022 at 10:03 | comment | added | knallfrosch | You're looking for friction, intentionally adding complexity. It's used infamously in privacy controls, but also on GitHub, where you have to type your repository's name in order to delete it. | |
| Jul 29, 2017 at 23:55 | comment | added | Voo | I like the idea of the TFS UI where dangerous options like deleting a build or whole team project requires you to type out the name of the object. Seems like a similar system would work perfectly fine in this situation as well. | |
| Jul 29, 2017 at 22:23 | comment | added | Ghanima | User destroyed by a cat on the keyboard... certainly not the best idea. | |
| Jul 28, 2017 at 12:04 | answer | added | Aganju | timeline score: 2 | |
| Jul 28, 2017 at 9:53 | answer | added | Klaws | timeline score: 0 | |
| Jul 28, 2017 at 7:55 | vote | accept | Glorfindel | ||
| Jul 28, 2017 at 7:34 | comment | added | Dennis Jaheruddin | Some already mentioned that the keystrokes may overlap with other shortcuts. Keep in minds that there may also be other things that could overlap with the keystrokes (especially if you would have 2 windows in parallel). For instance anyone could take the name mm4a by coincidence or on purpose to illicit erroneous deletes. (Not to mention accidental occurrances of things like mma or mm4) | |
| Jul 28, 2017 at 5:28 | comment | added | Glorfindel | @Kat other actions on that page (e.g. annotations and suspensions) are much, much rarer for me (maybe not for moderators on other sites) and require typing a custom text. I wouldn't use the keyboard shortcuts for those actions. | |
| Jul 28, 2017 at 1:17 | answer | added | Harper - Reinstate Monica | timeline score: 3 | |
| Jul 27, 2017 at 22:18 | comment | added | Kat | How quickly do you perform their keystrokes? Is there a situation where you'd use the same keystrokes but be trying to perform a different action? For instance, could you be trying to do a temp ban or delete a different user? Five keystrokes that can only do what you want is one thing; five keystrokes that can do something catastrophic before you realize it's been done is another. | |
| Jul 27, 2017 at 10:07 | comment | added | terdon | Note that only the last keystroke needs to be wrong to delete a user inadvertently. The previous four or five are also used for other actions you can take on that user, so it doesn't need multiple mistakes to get it wrong, just one. | |
| Jul 26, 2017 at 21:40 | answer | added | LinWin | timeline score: 1 | |
| Jul 26, 2017 at 19:25 | comment | added | mgarciaisaia | If this feature is crucial but kind-of-frequently-used, it may be really useful to have something like a Trash Bin for users - moderators Destroy a User, and it is kept in the Purgatory for a month so it can be Un-destroyed if a mistake has been done. | |
| Jul 26, 2017 at 16:18 | history | edited | Glorfindel | CC BY-SA 3.0 |
added 283 characters in body
|
| Jul 26, 2017 at 15:52 | answer | added | CumminUp07 | timeline score: 11 | |
| Jul 26, 2017 at 15:09 | answer | added | Peter | timeline score: 3 | |
| Jul 26, 2017 at 14:05 | answer | added | krillgar | timeline score: 3 | |
| Jul 26, 2017 at 11:28 | comment | added | Glorfindel | The two answers below are useful (thanks, I upvoted them), but I'm also interested (if it exists at all) in some kind of graph relating the # of clicks (or a similar metric) and the error rate. | |
| Jul 26, 2017 at 11:25 | comment | added | Glorfindel | @CodyGray it's five keyboard hits: M -> M -> 4 -> (Tab ->) A -> Enter. | |
| Jul 26, 2017 at 11:24 | comment | added | Cody Gray | If "destroy user" is still irreversible like I remember it being, then a keyboard shortcut is absolutely a bad idea. This should take at least 2 clicks to prevent misfires. | |
| Jul 26, 2017 at 10:46 | history | tweeted | twitter.com/StackUX/status/890161290173403137 | ||
| Jul 26, 2017 at 10:14 | answer | added | Joao Carvalho | timeline score: 28 | |
| Jul 26, 2017 at 9:22 | answer | added | user101673 | timeline score: 54 | |
| Jul 26, 2017 at 9:17 | comment | added | locationunknown | As a sidenote: I think it is as much about error prevention as it is about recovering from errors. | |
| Jul 26, 2017 at 9:03 | history | asked | Glorfindel | CC BY-SA 3.0 |