standards-support icon indicating copy to clipboard operation
standards-support copied to clipboard

Incorrect operating instruction for spinbutton

Open JAWS-test opened this issue 5 years ago • 5 comments

Summary

Incorrect operating instruction for spinbutton

  1. Open https://www.w3.org/TR/wai-aria-practices/examples/spinbutton/datepicker-spinbuttons.html
  2. Navigate with Tab key to the spinbuttons

Expected result

Correct operating instructions

Actual result

The operating instructions "To set the value use the Arrow keys or type the value." are wrong because no value can be entered. According to ARIA specification text input is not necessary for spinnbutton. See also: https://github.com/w3c/aria-practices/issues/1155

Additional Information

JAWS version and build number

JAWS 2019.1907.42

Operating System and version

Windows 8

Browser and version:

Chrome 76.0.3809.100 Firefox 68.0.2 Internet Explorer 11.0.9600.19431

JAWS-test avatar Aug 31 '19 23:08 JAWS-test

@JAWS-test it may be difficult for JAWS to determine whether text can be entered into a particular spinbutton, so the hint could get quite wordy: "To set the value use the arrow keys. Some spinbuttons allow you to type the value" - do you feel this would suffice?

frex65 avatar Mar 20 '20 12:03 frex65

JAWS should recognize whether or not the spinbutton allows text input. The operating instructions should be output correctly depending on the type of spinbutton. According to @mcking65, this is possible and therefore a JAWS error; see https://github.com/w3c/aria-practices/issues/1155#issuecomment-526821857 Unfortunately, I do not know how JAWS can make the difference. If that is not possible, my tickets should be reopened, see https://github.com/w3c/html-aam/issues/234 and https://github.com/w3c/aria-practices/issues/1155

JAWS-test avatar Mar 20 '20 13:03 JAWS-test

@frex65 In NVDA the output is correct. This is because the "editable" property is not transmitted for spinbuttons without text input.

JAWS-test avatar Mar 25 '22 11:03 JAWS-test

@BrettLewisVispero issue still present in JAWS 2024/Chrome

test case

stevefaulkner avatar Apr 10 '24 13:04 stevefaulkner

Imported into ADO as bug 79623

BrettLewisVispero avatar Apr 10 '24 22:04 BrettLewisVispero