Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361625 - [Accessibility] JAWS reads parent shell for 3+ level dialogs
Summary: [Accessibility] JAWS reads parent shell for 3+ level dialogs
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-21 05:19 EDT by Andrey CLA
Modified: 2019-11-14 03:37 EST (History)
1 user (show)

See Also:


Attachments
test case showing the problem (4.04 KB, application/octet-stream)
2011-10-21 05:20 EDT, Andrey CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey CLA 2011-10-21 05:19:33 EDT
Build Identifier: [Accessibility] JAWS reads parent shell for 3+ level dialogs

This is much like bug 15559. However, this reproduces for 3+ level dialogs. For them, when dialog is opened, JAWS 12 reads parent shell as well as active shell. This is very inconvenient, especially if parent shell contains many text - it's all read before active dialog is read

Reproducible: Always

Steps to Reproduce:
1.Launch example attached & JAWS
2.Click Dialog and Yes
3.Listen how JAWS reads message box
Comment 1 Andrey CLA 2011-10-21 05:20:10 EDT
Created attachment 205703 [details]
test case showing the problem
Comment 2 Lars Vogel CLA 2019-11-14 03:37:31 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.