Bug 268407 - Focus not set properly after activating faces-config editor with the keyboard
Summary: Focus not set properly after activating faces-config editor with the keyboard
Status: NEW
Alias: None
Product: Java Server Faces
Classification: WebTools
Component: JSF Tools (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: Future   Edit
Assignee: Debajit Adhikary CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility, helpwanted
Depends on:
Blocks:
 
Reported: 2009-03-12 14:49 EDT by Christine Rice CLA
Modified: 2010-12-09 11:25 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christine Rice CLA 2009-03-12 14:49:36 EDT
Version: 3.4.1, Build id: M20080911-1700

Steps To Reproduce:
1) Create a Web project with the JavaServer Faces configuration.
2) Create a faces jsp (so that you have another editor open)
3) Open faces-config.xml and switch to the Overview tab
4) Using the keyboard (I used Ctrl + F6), switch focus off of the faces-config editor and then back to it.

At this point, for accessibility reasons, there needs to be a visual focus indicator in the editor so that a user (and assistive technology) can tell where the focus is. But there won't be one. The Microsoft Inspect Objects program reports the name of the focused object as "Web - Prj/WebContent/WEB-INF/faces-config.xml - Eclipse Platform", which I think it's reading from Eclipse's title bar.

Similar problems occur with other tabs of this editor.

The only way I've found to navigate this editor with keyboard is to tab off of it, and then use Shift-Tab to return to the editor. At this point the editor usually has focus and I can use the keyboard.
Comment 1 David Williams CLA 2009-03-30 13:47:29 EDT
I'm setting to P2 as this is an important accessibility defect for some adopters trying to meet government regulations. 

I hope some attention can be given to it, or a response if for example, there is some issue we are missing. 



Comment 2 David Williams CLA 2009-04-21 14:33:09 EDT
FYI, this sounds similar to bug 271382 ... for which there was a pretty easy fix. 

Not sure it's exactly the same, but hope it helps. 

Comment 3 Bob Gallagher CLA 2009-09-18 15:57:47 EDT
Could we get an update to this defect's status?
Comment 4 Raghunathan Srinivasan CLA 2009-09-18 16:21:03 EDT
This has not been fixed in 3.1.1. We will address this and other accessibility issues in 3.1.2.
Comment 5 Christine Rice CLA 2010-04-01 11:31:43 EDT
Marking this as a hotbug request since not having an accessible editor interferes with or may prevent IBM's adoption of WTP.

Thanks.
Comment 6 Raghunathan Srinivasan CLA 2010-04-01 14:22:27 EDT
We invite patches to address these issues.
Comment 7 Ian Trimble CLA 2010-04-23 16:56:13 EDT
Debajit,
Raghu asked me to re-assign to you. Thanks!
Comment 8 Raghunathan Srinivasan CLA 2010-06-03 14:04:42 EDT
Mass update of Helios bugs
Comment 9 David Williams CLA 2010-12-09 11:25:41 EST
From discussions with Yury Kats, this does not need the focused tracking as "hotbug" any longer.