Bug 164773 – AX: Need to update implicit/default values for aria-valuemin, aria-valuenow, and aria-valuemax

• Status: RESOLVED
• Resolution: FIXED
• Component: Accessibility

[Joanmarie Diggs]

In ARIA 1.1, the implicit/default values for aria-valuemin, aria-valuenow, and aria-valuemax are as follows:

For roles other than spinbutton:
* Default for aria-valuemin is 0. 
* Default for aria-valuemax is 100. 
* Default for aria-valuenow is half way between aria-valuemax and aria-valuemin.

For spinbutton:
* Default for aria-valuemin is that there is no minimum value.
* Default for aria-valuemax is that there is no maximum value.
* Default for aria-valuenow is 0.

We currently are returning 0 for all non-specified values.

We need to decide how to expose "no minimum/maximum value." At least in the case of ATK/AT-SPI2, we need to return something, and the something is expected to be a number. My proposal is that we expose the values we use to constrain input type="number": -std::numeric_limits<float>::max() to std::numeric_limits<float>::max().

[Radar WebKit Bug Importer]

<rdar://problem/29268020>

[Joanmarie Diggs]

Created attachment 294835 [details]
Patch

[WebKit Commit Bot]

Comment on attachment 294835 [details]
Patch

Clearing flags on attachment: 294835

Committed r208739: <http://trac.webkit.org/changeset/208739>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.