Community
Participate
Working Groups
Build Identifier: Version 4.2 build 20111215-0110 When creating an eclipse4 RCP application, it is possible to create a UI model where screen readers cannot access all controls. Such an example can be found in the eclipse4 RCP tutorial by Tom Schindl in chapter 5 (http://tomsondev.com/e4rcp/chapter5.zip) where the contents of the list in the folder part cannot be accessed with NVDA's review cursor on windows and Orca on Linux has trouble as well. If one removes the stack part which contains the folder part (IE. so the folder part is directly in the sash part) then screen readers can access the contents of the list in the folder part. An example of this modification of removing the stack part can be found in the attached model file. The presence of a stack part should not make controls inaccessible to screen readers. Reproducible: Always Steps to Reproduce: 1. Download the source code for the tutorial chapter from http://tomsondev.com/e4rcp/chapter5.zip and import the projects into your workspace from the archive file. 2. Run the mailapp project as an eclipse application. 3. Try using the review keys of a screen reader (eg. NVDA) to select an account with folders and then use the screen readers review keys to find the content of the list in the folder part. 4. Try the above three steps but substitute the attached application model file for the model file in the mailapp project. Observe the difference in what the screen reader can access.
Created attachment 210622 [details] The application model which has the stack part removed which makes the list contents in the folder part accessible.
adding Carolyn - can you reproduce the problem described here? Can it be that the problem is our usage sash-layout and if a Part is not contained inside a CTabFolder this causes us trouble?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.