Open Bug 1563428 Opened 6 years ago Updated 2 years ago

Expose numeric value information in Accessibility Properties

Categories

(DevTools :: Accessibility Tools, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: Jamie, Unassigned)

Details

Attachments

(1 file)

We already expose the "value" property, which is usually sufficient. However, numeric controls can have minimum, current and maximum values, as well as a textual value. (In ARIA, these map from aria-valuemin, aria-valuenow, aria-valuemax and aria-valuetext.) In that case, "value" just exposes the textual value. Since these things can be controlled by the author, I think it'd be useful to expose them in Accessibility Properties.

A real world (if somewhat obscure and rare) use case for this is bug 1357071, where I'm mentoring someone to fix our exposure of default numeric values for ARIA scrollbar/slider. If this were exposed in Accessibility Properties, we wouldn't need to rely on a platform accessibility inspector to verify this information.

Assignee: nobody → taken.spc
Status: NEW → ASSIGNED

The bug assignee didn't login in Bugzilla in the last 7 months.
:Jamie, could you have a look please?
For more information, please visit auto_nag documentation.

Assignee: taken.spc → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(jteh)
Flags: needinfo?(jteh)
Severity: normal → S3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: