Bug 8846 - Accelerators are not acknowledged by JAWS
Summary: Accelerators are not acknowledged by JAWS
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Carolyn MacLeod CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2002-01-31 11:16 EST by Tod Creasey CLA
Modified: 2002-02-01 16:16 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 Tod Creasey CLA 2002-01-31 11:16:28 EST
If you fire an action by selecting an acceleraor JAWS give no feedback that 
that action has occurred.

STEPS
1) Start JAWS
2) Open a text editor
3) Type something
4) Hit Ctrl-S - save occurs but the user is given no feedback
Comment 1 Nick Edgar CLA 2002-02-01 14:43:30 EST
How does this work in other apps?
Comment 2 Tod Creasey CLA 2002-02-01 14:49:36 EST
Yes it does - in word for example it tells you all of the accelerators
Comment 3 Nick Edgar CLA 2002-02-01 15:11:40 EST
Seems like an SWT problem, since for Save we just set the accelerator on the 
MenuItem.  Should be able to demonstrate easily in a standalone SWT app.
Comment 4 Mike Wilson CLA 2002-02-01 15:14:43 EST
What is the expected behavior? 
Comment 5 Tod Creasey CLA 2002-02-01 15:29:46 EST
In other applications (such as Word) the accelerator is said i.e. for copy they 
say Ctrl C Copy.
Comment 6 Carolyn MacLeod CLA 2002-02-01 16:16:31 EST
Tod & I tried to figure out what JAWS was doing, and we believe now that it is 
simply reading the key presses from the keyboard. JAWS knows about standard 
operations like Cut/Copy/Paste/Undo/Redo and so it can speak those actions in 
detail. But it turns out that JAWS is really inconsistent. We can get some 
things to work in Eclipse, and we can get the same things to fail in Word, and 
vice-versa. We were able to get JAWS to read CTRL+S in Eclipse, as described in 
this bug report, so I am marking it "Works For Me". If Tod discovers a 
repeatable, reliable case that definitely always fails in Eclipse and always 
works in Word, then we will reopen this PR.