aria-valuenow is not a valid aria attribute for DateTextBox and TimeTextBox

[jwforres]

According to the ARIA spec www.w3.org/TR/wai-aria/roles the aria-valuenow attribute only applies to HTML elements with a role that inherits from the "range" role, e.g. spinnerbox, slider, etc. The <input> element inside DateTextBox? and TimeTextBox? does not have any role in Dojo 1.4.3 and in 1.7 it has role of textbox. aria-valuenow is not considered a valid attribute on an element with role textbox.

[Douglas Hays]

Becky, I need help with this. DateTextBox? is a range textbox but it's role is neither of the approved role=range subclasses: progressbar,scrollbar,slider,spinbutton.

[davidtodd]

Same issue for NumberTextBox?, but also contains aria-valuemin and aria-valuemax. Maybe aria-valuetext as well.

[mikeb]

A similar issue is applying 'aria-pressed' to a selected tab in a TabContainer?, since aria-pressed is not valid for role=tab (​http://www.w3.org/TR/wai-aria/roles). I'm sure there are more instances of dijits including extra aria attributes. In general these attributes are getting flagged by automated tools as errors but they do not seem to cause any useability problems (it seems that at least Jaws screen reader ignores invalid attributes.)

[bill]

The TabContainer issue was fixed 7 months ago in [26369].

[Paul Christopher]

The question is how a screenreader user gets to know the constraints of a DateTextBox and a TimeTextBox. aria-valuemin and aria-valuemax could help if those are announced by the screenreader when the control is focused. However arai-valuemin, aria-valuemax and arai-valuenow need to have a good readable description of their value, see ​http://bugs.dojotoolkit.org/ticket/15625.

Can anyone test this with a screenreader? Are those values announced? If so, I would not remove those attributes from RangeBoundText.js (although they are not considered as correct according to the specs).

[mikeb]

None of the aria-value* attributes are announced by JAWS13 on the nightly build (tested DateTextBox? and TimeTextBox?.) JAWS just seems to read out whatever is in the value attribute of the input element, probably because the input has role=textbox. There does not seem to be any way to figure out the "max" and "min" allowed elements.

I think for now we should just remove these invalid elements. However, the main issue in my opinion is that these elements are in fact "range" widgets and the ARIA spec is incomplete since the only range widgets are progressbar, scrollbar, slider, and spinbutton.

[mikeb]

removes aria range attributes for Date/TimeTextBoxes?, adds them back for _Spinner, fixes up test pages, please proxy commit for michael billau ccla on file with ibm

[Douglas Hays]

In [29819]:

Fixes #15052. Proxy commit for Mike Billau (IBM, CCLA). Move aria-valuemin/max/now from RangeBoundTextBox? to _Spinner since they're not valid for role=textbox.