Opened 12 years ago

Closed 12 years ago

#4126 closed defect (wontfix)

Window-Eyes is speaking the accordion arrows as question

Reported by: Becky Gibson Owned by: ptbrunet
Priority: low Milestone: 1.0
Component: Accessibility Version: 0.9
Keywords: Cc: Becky Gibson
Blocked By: Blocking:

Description

the arrows for expanding/contracting an accordion container are properly marked with waiRole=Presentation (altho try adding tabindex=-1 to make sure FF includes them in a11y hierarchy). Window-Eyes speaks the arrows as part of the accordion title but JAWS does not. I'm not sure if we can do anything about this or not. This may be a Firefox bug that is fixed in Firefox 3 builds.

Change History (6)

comment:1 Changed 12 years ago by ptbrunet

Using http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/layout/test_AccordionContainer.html with FF2 and both JAWS 9 331 and JAWS 10 113 not in virtual mode, tabbing into an accordian first moves to role PAGETAB. Hear "pane 1 tab". Pressing tab again moves to role PROPTERTY_PAGE. Hear nothing. The accessible hierarchy looks like PAGETAB, PROPERTY_PAGE, TEXT. This could be fixed by putting focus on the text object not the property page. JAWS would ignore focus on a PROPOERTY_PAGE.

comment:2 Changed 12 years ago by ptbrunet

I don't hear W-E 6.1D speaking anything related to the icon. Here's what I hear: When the tab gets focus: "pane 1, 4 of 9". When the property page gets focus: "property page". So W-E has problems with the property page like JAWS. The "n of m" is seen in Inspect so it has nothing to do with the screen reader. I'll investigate.

comment:3 Changed 12 years ago by ptbrunet

For the first comment above, refer to #4484. Instead of focus moving to the tab pagetab object and then the property_page object, focus would move to the first focusable object in the pane (and if there is nothing focusable, e.g. static text, maybe the static text can be given focus).

comment:4 Changed 12 years ago by ptbrunet

The second comment is addressed by #4127.

comment:5 Changed 12 years ago by ptbrunet

FF3 is correctly ignoring the up/down arrows and creating an acc name of just the title of the pane. FF2 is creating an acc name with the up/down arrow characters at the beginning of the name.

comment:6 Changed 12 years ago by ptbrunet

Resolution: wontfix
Status: newclosed

Closing as won't fix since the issue has been resolved in FF3, i.e. the arrow character entities have been removed from the accessible name by FF3.

Note: See TracTickets for help on using tickets.