Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 320582 - When the label is in 1 line, screen reader will be able to read the complete label . But if the same label is in multiple lines(because of lower resolution/ resizing of the window), then the screen reader will read the line which the focus is on
Summary: When the label is in 1 line, screen reader will be able to read the complete ...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-22 00:36 EDT by Yang Rui CLA
Modified: 2019-11-08 04:37 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yang Rui CLA 2010-07-22 00:36:26 EDT
Build Identifier: 3.4.2

The accessability issue:
When the label in eclipse is in 1 line, then the screen reader will be able to read the complete label . 
But if the same label is in multiple lines(because of lower resolution/ resizing of the window), then the screen reader will read the line which the focus is on.
 


Reproducible: Always
Comment 1 Felipe Heidrich CLA 2010-07-22 09:17:18 EDT
We are not fixing bugs in 3.4.2 anymore.

Can you please try the same scenario on 3.6 ? Thank you
Comment 2 Carolyn MacLeod CLA 2011-03-21 14:19:51 EDT
Please provide a snippet so that we can test this,
or give steps to see this problem in Eclipse.

I do not know what you mean by a "label" because SWT Label controls do not take focus. So I need to either see code, or an example, so that I can figure out what you mean.
Comment 3 Lars Vogel CLA 2019-11-08 04:37:07 EST
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.