Bug 164773

Summary: AX: Need to update implicit/default values for aria-valuemin, aria-valuenow, and aria-valuemax
Product: WebKit Reporter: Joanmarie Diggs <jdiggs>
Component: AccessibilityAssignee: Joanmarie Diggs <jdiggs>
Status: RESOLVED FIXED    
Severity: Normal CC: aboxhall, apinheiro, cfleizach, commit-queue, dmazzoni, jcraig, mario, samuel_white, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch none

Joanmarie Diggs
Reported 2016-11-15 07:41:20 PST
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().
Attachments
Patch (9.05 KB, patch)
2016-11-15 08:06 PST, Joanmarie Diggs 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2016-11-15 07:44:00 PST
<rdar://problem/29268020>
Joanmarie Diggs
Comment 2 2016-11-15 08:06:42 PST
Created attachment 294835 [details] Patch
WebKit Commit Bot
Comment 3 2016-11-15 11:31:27 PST
Comment on attachment 294835 [details] Patch Clearing flags on attachment: 294835 Committed r208739: <http://trac.webkit.org/changeset/208739>
WebKit Commit Bot
Comment 4 2016-11-15 11:31:31 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.