This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From WebAIM list (scott gonzales) Then there are cases such as spinbutton, where the ARIA Authoring Practices will tell you to treat up/down the same as right/left, even though it doesn't make sense. For editable spinners, you definitely do not want to override the left and right arrows since those are used to change cursor position within the current value.
(In reply to James Nurthen from comment #0) > From WebAIM list (scott gonzales) > > Then there are cases such as spinbutton, where the ARIA Authoring Practices > will tell you to treat up/down the same as right/left, even though it > doesn't make sense. For editable spinners, you definitely do not want to > override the left and right arrows since those are used to change cursor > position within the current value. This was changed based on Scott's suggestion a while back. I don't remember exactly when, but the latest WD (07-Mar-2013) states [1] (my emphasis): "The associated text field generally supports standard text entry operations such as selection of characters, deletions, insertions, and caret movement using *the Right Arrow and Left Arrow keys*. ... * Up Arrow increases the value. * Down Arrow decreases the value. ... " The latest published editor's draft (08-Apr-2014) [2], and the work-in-progress draft [3] use the same text. [1] http://www.w3.org/TR/wai-aria-practices/#spinbutton [2] http://www.w3.org/WAI/PF/aria-practices/Overview.html#spinbutton [3] http://rawgit.com/w3c/aria/master/practices/aria-practices.html#spinbutton