This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23383 - Strong semantics table missing @value, @min, @max on ranges (slider, progressbar)
Summary: Strong semantics table missing @value, @min, @max on ranges (slider, progress...
Status: RESOLVED MOVED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2013-09-27 17:32 UTC by James Craig
Modified: 2015-06-05 14:49 UTC (History)
5 users (show)

See Also:

Attachments

Description James Craig 2013-09-27 17:32:30 UTC 
Strong semantics table missing @value, @min, @max on ranges (slider, progressbar)

The ARIA attributes @aria-valuenow, @aria-valuemin, @aria-valuemax, should have no effect on range widgets like @sliders because they have identical semantics to @value, @min, and @max. The "strong" table should list these on the appropriate elements.

Note: @aria-valuetext should still be allowed.

http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-strong-native-semantics
Comment 1 steve faulkner 2014-01-12 16:26:29 UTC 
(In reply to James Craig from comment #0)
> Strong semantics table missing @value, @min, @max on ranges (slider,
> progressbar)
> 
> The ARIA attributes @aria-valuenow, @aria-valuemin, @aria-valuemax, should
> have no effect on range widgets like @sliders because they have identical
> semantics to @value, @min, and @max. The "strong" table should list these on
> the appropriate elements.
> 
> Note: @aria-valuetext should still be allowed.
> 
> http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-strong-native-
> semantics

HI James, unclear what you want, the strong semantics table describes the aria semantics that correspond to the native semantics. Its a directive to implementers to map the aria semantics to the same properties as the native semantics.

What change would you like to see?
Comment 2 James Craig 2014-01-13 20:03:46 UTC 
(In reply to steve faulkner from comment #1)
> What change would you like to see?

Add rows for:

input[type="number"] /* strong map @value to @aria-valuenow */
input[type="number"] /* strong map @min to @aria-valuemin */
input[type="number"] /* strong map @max to @aria-valuemax */

input[type="range"]  /* strong map @value to @aria-valuenow */
input[type="range"]  /* strong map @min to @aria-valuemin */
input[type="range"]  /* strong map @max to @aria-valuemax */

There may be other native range types that escape me at the moment.
Comment 3 James Craig 2014-01-13 20:06:49 UTC 
Also:

progress /* strong map @value to @aria-valuenow */
progress /* strong map @min to "0" (there is no @min attr on progress)  */
progress /* strong map @max to @aria-valuemax */
Comment 4 steve faulkner 2015-06-05 14:49:13 UTC 
moved to https://www.w3.org/Bugs/Public/show_bug.cgi?id=28768