Bugzilla – Full Text Bug Listing
| Summary: | The New File Wizard Page is Not Screen reader able | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Sola <omosaiye> |
| Component: | UI | Assignee: | Tod Creasey <Tod_Creasey> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | major | ||
| Priority: | P1 | CC: | paulacox, Randy_Giffen, Tod_Creasey, vilmar |
| Version: | 2.0 | Keywords: | accessibility |
| Target Milestone: | 2.0 M6 | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
| Bug Depends on: | 15559 | ||
| Bug Blocks: | |||
|
Description
Sola
If you don't mind me asking, are you vision impaired? What is the expected behaviour in scenarios like this? In general, screen readers skip any controls that don't take focus, like labels. Is it better to use something like a read-only text so that it can take focus, or to provide the labels directly to the screen reader via the accessibility APIs? The expected behavior is as follows: Whne the wizard comes up the Screen Reader should report the title of the wizardpage to the user. JAWS for example gives one the ability, through a key combination, to read the entire contents of a dialog. When this key combination, "Ins + B" is used with the wizard page, the report(spoken text) is incomprehensible. When the wizard comes up the "New" title is read. However there is currently a problem with dialogs where they read the workbench window behind them when Ctrl+B is used. See Bug 15559 Using JAWS it is possible to read the dialog using the JAWS cursor (-) so it is not unreadable. The Ins+B functionality is an extra feature that we do not currently support that we should consider for later releases. It would likely require some sort of discussion with Freedom Scientific (the makers of JAWS). What it is currently reading is the parent shell (the window) of the dialog - special support is required to read a dialog that is not a Windows system dialog. Marking as LATER. My belief is that using the Ins+B is a fairly common key sequence when using Jaws with software applications. Will this work-around be documented in the helps? Yes it should be documented. Logged Bug 18315 to be sure it is done. *** Bug 18725 has been marked as a duplicate of this bug. *** I have added this PR to the accessibility checklist. To summarize the problem: The JAWS cursor provides an accessible alternative. Other apps have this problem, e.g. Photoshop. The issue is that it's really a bug in JAWS. JAWS should read the whole dialog, including labels contained in other composites, but it does not. They have made special workarounds for specific products, which is why the MS Office products work OK with Ins+B. We looked into changing how our dialogs work to match the patterns that JAWS handles properly, but this was non trivial and we deemed it too risky to do for 2.0. Verified that the Inspect Object tool shows the correct text when the mouse hovers over the different areas of our dialog, including the titlebar and label. We are simply using OS widgets here, so JAWS should be able to handle it. Reopening. This is a dup of 18518. See recent comments there. *** This bug has been marked as a duplicate of 18518 *** |