ATK hierarchy inconsistent for ARIA spinners

RESOLVED INVALID

Status

()

Core
Disability Access APIs
RESOLVED INVALID
10 years ago
10 years ago

People

(Reporter: Scott Haeger, Assigned: Aaron Leventhal)

Tracking

(Blocks: 1 bug)

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
This spinner http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_Slider.html is an example where there are extra 'section's in the accessible tree which make up the construct of the spinner.  These accessible nodes should not be exposed in the accessible hierarchy.
(Assignee)

Comment 1

10 years ago
Is this the same as bug 395258. Can they somehow be merged into one bug for spinners? There is also the XUL spinner bug 365893.
(Reporter)

Comment 2

10 years ago
For my purposes this is more like https://bugzilla.mozilla.org/show_bug.cgi?id=390154 .  The problem is that there are so many accessible objects associated with this widget.  I was hoping that only a single accessible object could be exposed for a spinner.

Note: the link in the opening comment should be http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_Spinner.html

Comment 3

10 years ago
If I get right then 'section' accessibles shouldn't be accessible because their div nodes has 'presentation' role but those divs contains @tabindex="-1" attribute that leads nodes are focusable and therefore we expose accessbiles for them. So, invalid?
(Assignee)

Comment 4

10 years ago
As Surkov says, this is not a bug in Mozilla.

Scott, can you file a bug on Dojo to remove the unnecessary tabindex="-1" on those divs? It's forcing the creation of an accessible even though there is role="presentation".
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.