Description: This component relates to bugs in our support for accessibility APIs on the various platforms. Accessibility APIs allow 3rd party products, such as screen readers used by visually impaired users, to communicate with our content and UI. The APIs we support specifically are MSAA on Windows and
ATK on UNIX/Linux (Apple has not yet published specs for an accessibility API on OS X). This component is not for keyboard, focus or any accessibility bugs other than those relating to the APIs we export.

Security

(public)

User Story

Do we need to create thumb accessible for xul:scale element? Iirc, MSAA and OS X expects thumb accessible inside of slider accessible but we don't expose it (nsAccUtils::MustPrune works). Afaik ARIA hasn't way to point thumb accessible and AT seems lives fine without thumb accessible. As well we don't need thumb accessible internally. So probably it's worth to remove it?

Note for dojo we made what is visually the thumb, actually the node with role="slider". We did this because we want the thumb(s) in the tab order and the focussed node should be the one that gets the related aria-attributes like valuenow etc.

(In reply to comment #2)
> Note for dojo we made what is visually the thumb, actually the node with
> role="slider". We did this because we want the thumb(s) in the tab order and
> the focussed node should be the one that gets the related aria-attributes like
> valuenow etc.
Heh, I bet they would get the same result if they would choose container of thumb to make it as slider. But any way ARIA hasn't thumb role, right?

I just took a look at a slider as found in the Windows Volumen Control applet. The Slider accessible has 3 children:
1. A PushButton with an accName of "Page to the left".
2. An Indicator accessible with an accName of "Position".
3. A PushButton with an accName of "Page to the right".
So yeah, I believe we need that thumb accessible.

(In reply to comment #5)
> (In reply to comment #4)
> > Right, no aria role of thumb.
>
> Btw, could be ARIA slider a thumb then?
If I understand the question right, yes (see comment #2).
I would get rid of thumb accessible.
Even for multi-thumbs http://dev.aol.com/dhtml_style_guide#slidertwothumb
In that case each thumb is supposed to be marked up as a slider with aria-value[min|max|now|text] so in gecko we don't have to worry ;) We just expose a slider for each visual thumb.