Community
Participate
Working Groups
When a accessibility screen reader tool is activated the form's section title is not read when it acquires the keyborad focus as the another widgets that are in the form's composite (checkbox, text area, etc...). It is not accessibility compliant.
Form section title by itself cannot acquire focus - it is static. Can you give me an example (what actual editor/view did you scan to get this findings)?
We are looking at screen reader accessibility right now. Could you please list the exact steps to open the dialog or go to the view or whatever to show the problem? Thanks!
Eric, please give us additional information. We are looking at screen reader problems right now, and we do not know what problem you are referring to. Please list the steps to repeat to show this problem. I am closing this bug as INVALID so that we do not waste any more time wondering what it means. Please reopen if you can show what the problem is. Thanks!
When the user goes all over the elements (text area, button, etc...) in an eclipse forms by using the tabulation key the element's characteristics and the associated text are read by the screen reader. Only the section title is not read. It is read only when the user moves the mouse pointer on them. There is not exist an issue to read this text with a keyboard action. This problem has beed detected on the plugin.xml editor. On the tab Overview the text "General Information", "Testing", "Plug-in Content" and "Deploying" are never read by the screen reader whereas the section description "This section describes general..." is read.
Tab key is used for controls capable of handling keyboard focus. I don't see how you can tab to static text. Sections that are expandable do accept focus on the expandable toggle hyperlink, and the link will report the section title. I have played in this very page of Bugzilla and when I used the TAB key, I only got information about hyperlinks and widgets, but not about static text. For static text, I had to move the mouse over it. This is consistent with PDE editor behaviour.
