312457 - Checked items in tree views do not report checked/checkable state

Status: RESOLVED DUPLICATE of bug 360510

(Core :: Disability Access APIs, defect)

Description

[James Teh [:Jamie]]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Build Identifier: version 1.6a1 (20051010)

In tree views in which items are checkable, such as the tree views in 
the "Subscribe" dialog or the "Items for Offline Use" dialog, the MSAA state 
for checked items does not include the 'checked' state flag. This means that it 
is impossible for screen readers to determine the checked state via MSAA.

Reproducible: Always

Steps to Reproduce:
1. File menu->Subscribe; or Tools menu->Account Settings->Offline & Disk Space-
>Select folders for offline use.
2. Examine the MSAA state for a checked item in the tree view.

Actual Results:  
The MSAA state does not include the 'checked' state flag.

Expected Results:  
The MSAA state should include the 'checked' state flag for checked items in 
such tree views.

I am using JAWS for Windows, though this is not overly relevant, as the problem 
can be tested easily enough with MSAA Explorer (in the MSAA developer tools).

Comment 1

[David :Bienvenu]

isn't this a core widget problem? We're using a tree...or do we have to do
something special, Aaron?

Comment 2

[Aaron Leventhal]

Yes, it sounds like a core widget problem.

Comment 3

[Aaron Leventhal]

Should also use STATE_CHECKABLE if they're checkable

Comment 4

[Evan Yan]

Is this bug a MSAA only or in XP code?
since bug 360510 seems a dupe of this one.

Comment 5

[Aaron Leventhal]

Cross platform bug.

Comment 6

[Ginn Chen]

Dupe of bug 365866?

Comment 7

[Nian Liu(n/a in a long time)]

(In reply to comment #3)
> Should also use STATE_CHECKABLE if they're checkable
> 

STATE_CHECKABLE need atk support, but do we really need that? see bill's comment in http://bugzilla.gnome.org/show_bug.cgi?id=399295

"Why do we need this?  We have ATK_ROLE_CHECK_BOX, ATK_ROLE_CHECK_MENU_ITEM, and
ATK_ROLE_RADIO_BUTTON/ATK_ROLE_RADIO_MENU_ITEM which imply checkability.  I
don't know of any other types of components that are 'CHECKABLE', so not sure
this addition would add any new information."

Comment 8

[Aaron Leventhal]

Please expose nsIAccessible::STATE_CHECKABLE anyway, because we map that in MSAA.

If we later get Bill to add this state for ATK then we'll already have support for it.

Comment 9

[Nian Liu(n/a in a long time)]

we may need a new bug to trace it. current focus is on cycler.

see 368012

Comment 10

[Willie Walker]

Regardless of how we might infer the state in Orca, CHECKABLE would be nice.  To answer Bill's question, one might have a table cell that is also a check box.  We see it all the time in GNOME, and the only way we resolve it is by inference through the existence of a named "toggle" action.

Comment 11

[David Bolter [:davidb] (NeedInfo me for attention)]

Attachment: possible fix

Comment 12

[alexander :surkov (:asurkov)]

I'm not sure about cycler code. Why it should be checkable i.e. what info does it bring to AT?

Comment 13

[David Bolter [:davidb] (NeedInfo me for attention)]

Surkov, sorry for this late reply. An example of a cycler is a cell that can contain many values (for example the numbers 1 to 5), and allows a way for a user to cycle (or toggle) among the values. It is semantically close to "checkable" (although not perfect). Since it will help screen reader users I think we might as well expose it in this case.

Comment 14

[David Bolter [:davidb] (NeedInfo me for attention)]

This bug will be fixed by work on 368012.

Comment 15

[Marco Zehe (:MarcoZ)]

Wrong dupe number. The issue reported here is still an issue and is NOT fixed for either Windows or Linux.

Comment 16

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1527381