Revision as of 15:00, 19 August 2022 edit BrownHairedGirl (talk \| contribs) Autopatrolled, Extended confirmed users, File movers, Pending changes reviewers, Rollbackers 2,942,733 edits m Added 1 {{Bare URL inline}} tag(s) using a script. For other recently-tagged pages with bare URLs, see Category:Articles with bare URLs for citations from August 2022 ← Previous edit		Revision as of 23:33, 19 November 2022 edit undo 103.116.245.10 (talk) →Mode errors: unrelevant hyperlink Tag: Visual edit Next edit →
Line 37: {{See also\|User error}} Modes are often frowned upon in interface design because they are likely to produce ''mode errors'' when the user ~~[[Short-term memory\|~~forgets]] what state the interface is in, performs an action that is appropriate to a different mode, and gets an unexpected and undesired response.<ref>[http://www.usabilityfirst.com/glossary/mode-error/ Glossary: mode error]</ref><ref name="glossary">[http://www.usabilityfirst.com/glossary/modal Usability Glossary: modal]</ref> A mode error can be quite startling and disorienting as the user copes with the sudden violation of their user expectations. Problems occur if a change in the system state happens unnoticed (initiated by the system, or by another person, such as the user who was previously using the machine), or if after some time the user forgets about the state change. Another typical problem is a sudden change of state that interrupts a user's activity, such as [[focus stealing]]. In such a situation it can easily happen that the user does some operations with the old state in mind, while the brain has not yet fully processed the signals indicating the state change.

Mode (user interface): Difference between revisions