Community
Participate
Working Groups
Version: 3.4.1, Build id: M20080911-1700 Steps To Reproduce: 1) Create a Web project with the JavaServer Faces configuration. 2) Create 2 faces jsp files 3) Open faces-config.xml and go to the Navigation tab 4) Add the two pages and a navigation rule between them, or paste something like this into source: <navigation-rule> <from-view-id>/page1.jsp</from-view-id> <navigation-case> <from-outcome>success</from-outcome> <to-view-id>/page2.jsp</to-view-id> </navigation-case> </navigation-rule> 5) On the Navigation Rule page, select a page with the keyboard. A screen reader should say something useful at this point, but Window-Eyes 6.1 doesn't say anything. Microsoft Inspect Objects lists the name and value as "none [false]". 6) Try to select the navigation rule itself via the keyboard. I wasn't able to select it. Issues: -Nav rules should be selectable via the keyboard -Both pages and nav rules should report useful information to accessible technology (such as screen readers)
I'm setting to P2 as this is an important accessibility defect for some adopters. The following article may help: http://www.eclipse.org/articles/article.php?file=Article-Accessibility/index.html
Could we get an update to this defect's status?
Not fixed in 3.1.1. Plan to address in 3.1.2.
Marking this as a hotbug request since not having an accessible editor interferes with or may prevent IBM's adoption of WTP. Thanks.
We invite patches to address these issues.
Debajit, Raghu asked me to re-assign to you. Thanks!
Mass update of Helios bugs
From discussions with Yury Kats, this does not need the focused tracking as "hotbug" any longer.