Closed Bug 713010 Opened 13 years ago Closed 12 years ago

Element marked with ARIA role='button' and aria-pressed attribute not exposed as a toggle button

Categories

(Core :: Disability Access APIs, defect)

8 Branch
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: clown, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en; rv:1.9.2.24) Gecko/20111113 Camino/2.1 (like Firefox/3.6.24)
Build ID: 20111113195207

Steps to reproduce:

Viewed the a11y tree for sample widgets (see link below) to see what was exposed for a <label role="button" aria-pressed="false" ..>.  Run on Fedora-16, with FF 8.0 and used Accerciser 3.3.1 to inspect the tree.

The full markup is here -- look for the "Shuffle" toggle button:
http://access.aol.com/aegis/#goto_button


Actual results:

The element was exposed as a push button (AT-SPI ROLE_PUSH_BUTTON).


Expected results:

The element should be exposed as a toggle button (AT-SPI ROLE_TOGGLE_BUTTON).

See:
- ARIA spec: http://www.w3.org/WAI/PF/aria/states_and_properties#aria-pressed
- ARIA implementation guide: http://www.w3.org/WAI/PF/aria-implementation/#mapping_state-property, specifically the row for aria-pressed.
OS: Mac OS X → Linux
Hardware: x86 → x86_64
See Also: → 390284
Blocks: aria
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
"Shuffle" is exposed as a push button in your example because there's no aria-pressed attribute on it. If you click it then it's exposed as toggle button, second click (uncheck it) keeps it as toggle button. Do you have different observations?
(In reply to alexander :surkov from comment #1)
> ...
> Do you have different observations?

Well, now that I take a closer look, yes and no, but mostly yes.

I can confirm that the aria markup changes as one interacts with the button.  As you noted, the aria-pressed attribute is added when the button is clicked.  I have also checked keyboard interaction and when the 'Shuffle' button is activated with the space bar, aria-pressed is added in that case too.

The "no" part:  I'm using Accerciser, and the info it displays in its "Interface Viewer" does not change -- it still says "push button" after the aria-pressed is added.  It should say "toggle button".  Now, the fault might lie with accerciser or with FF.  I can't tell since I can't look directly at the AT-SPI layer.

To sort-of double check, I looked at the page on WinXP, using accprobe.  There, the the IA2 role definitely changes from push to toggle button upon interaction.

So:  either this is a bug in FF/Linux/GNOME, or a bug in Accerciser.
Followup:  tbsaund suggested looking at the a11y tree as displayed by the DOM Inspector add-on.  I did so on FF/Linux/GNOME, and it shows the switch from push button to toggle.

Also, if accerciser is quit and restart after the aria-pressed is added, it shows a toggle button for that element.

This looks like an accerciser issue; I'll follow up with its developers.
Thanks for following this through Joseph!

Closing as WORKSFORME as per comment 3.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
(In reply to Joseph Scheuhammer from comment #3)
> Followup:  tbsaund suggested looking at the a11y tree as displayed by the
> DOM Inspector add-on.  I did so on FF/Linux/GNOME, and it shows the switch
> from push button to toggle.
> 
> Also, if accerciser is quit and restart after the aria-pressed is added, it
> shows a toggle button for that element.
> 
> This looks like an accerciser issue; I'll follow up with its developers.

afaik accerciser doesn't update the accessible tree until you click refresh button, what's happen here is we destroy old accessible and create new one.
You need to log in before you can comment on or make changes to this bug.