Bug 258142 - [Accessibility] Screen reader cant read Expand Bar
Summary: [Accessibility] Screen reader cant read Expand Bar
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-09 13:29 EST by Edgar Velazquez CLA
Modified: 2021-11-12 11:34 EST (History)
4 users (show)

See Also:


Attachments
Areas that the screen reader wont read from the expand bar (35.07 KB, image/jpeg)
2008-12-09 13:29 EST, Edgar Velazquez CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Edgar Velazquez CLA 2008-12-09 13:29:26 EST
Created attachment 119942 [details]
Areas that the screen reader wont read from the expand bar

Build ID: 20080221-1602 

Steps To Reproduce:
1.Open a screen reader and an application with an expand bar array (multiple expand bars)
2.Tab until you get to the expand bar, you'll see that the screen reader doesn't read the title of the expand bar, when you expand it and tab again (you are now in the content of the expand bar) it reads the text.
3.From there you can move through the expand bar array with the arrow keys (at this moment, while moving with the arrow keys the screen reader doesn't read the title of the select expand bar) 

More information:
Seems that the systems doesn't recognize any change in the expand bars while moving with the arrow keys

I used Inspect32 to check the info of the control selected and no name is set while moving with the arrow keys
Comment 1 Steve Northover CLA 2008-12-16 12:45:22 EST
Please work with Felipe to implement the missing accessibility features.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:08:23 EDT
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.