- From: <bugzilla@jessica.w3.org>
- Date: Tue, 22 Nov 2011 14:37:51 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14870 John Thomas <therandshow@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |therandshow@gmail.com --- Comment #3 from John Thomas <therandshow@gmail.com> 2011-11-22 14:37:50 UTC --- (In reply to comment #1) > From what I can tell from the bug description, this is a request to add an > @autosubmit boolean attribute to all form input elements. If @autosubmit is set > on an input element then an action that would have the element fire an onchange > event would automatically submit the form that owns the element. > > WCAG 2.0 success criteria 3.2.2 > "On Input: Changing the setting of any user interface component does not > automatically cause a change of context unless the user has been advised of the > behavior before using the component. (Level A)" > > http://www.w3.org/TR/UNDERSTANDING-WCAG20/consistent-behavior-unpredictable-change.html The key element here should be unpredictable. For example, sometimes sorting controls (especially in js-free environments) are represented as form elements. I think most users would expect a simple sorter (such as an arrow button next to a table header) to autosubmit. Likewise with paging controls. In addition, consider a corporate environment where web pages may be modeled after certain desktop applications. If that application autosubmits, then the user will likely expect the web page to do likewise. If I may make a bad pun, sometimes what is unpredictable to the user is not always predictable. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Tuesday, 22 November 2011 14:37:57 UTC