User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3pre) Gecko/2008011305 Minefield/3.0b3pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3pre) Gecko/2008011305 Minefield/3.0b3pre In both Thunderbird3 and Firefox3 options dialogs, the list of tabs contains items that all have an IAccessible role of list. Usually it would be expected that these be list items. I *think* these have an XUL tag of "radio" according to the IAccessible2 tag object attribute. From a quick look at nsRoleMap.h, I can see that ROLE_RICH_OPTION is mapped to ROLE_SYSTEM_LIST. I'm not sure if this is the problematic amapping or not? but reading the description of ROLE_RICH_OPTION it says its an option that could contain children. However, I would still think that mapping this to listItem would be more appropriate, as all the exampls I've seen (if this is in deed the problem) they only contain a label as a child, not much else. Reproducible: Always Steps to Reproduce: 1. Open Firefox3 or Thunderbird3 2. Open the options dialog 3. Using Accessibility Probe, locate the Options dialog frame. 4. Open this branch, one of the child branches should be a list 5. Open the list's branch 6. notice the list's children Actual Results: The list's children all have a role of list. Also using the properties view of Accessibility probe, you can see the IAccessible2 object attributes contain tag:radio Expected Results: The children should either have a role of listItem, or radioButton, but not list.
Summary: radio items in XUL dialogs have an IAccessible role of list, nor listitem or radioButton → radio items in XUL dialogs have an IAccessible role of list, not listitem or radioButton
This will get changed with the fix for bug 407359. That bug will reclass the RichOption to an ListItem instead of a List.
Depends on: 407359
Fix checked in with bug 407359
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Verified using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.