[Webkit-unassigned] [Bug 164773] New: AX: Need to update implicit/default values for aria-valuemin, aria-valuenow, and aria-valuemax

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=164773

            Bug ID: 164773
           Summary: AX: Need to update implicit/default values for
                    aria-valuemin, aria-valuenow, and aria-valuemax
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: All
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Accessibility
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jdiggs at igalia.com
                CC: webkit-bug-importer at group.apple.com

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().

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161115/ba2d878c/attachment-0001.html>