Issue 103863 - Accessibility with Jaws for Windows IE
Summary: Accessibility with Jaws for Windows IE
Status: UNCONFIRMED
Alias: None
Product: ui
Classification: Code
Component: AccessBridge (show other issues)
Version: OOo 2.4.0
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2009-07-29 04:40 UTC by colinguo
Modified: 2013-01-29 22:01 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description colinguo 2009-07-29 04:40:55 UTC
I want use JAWS read the odt files, at first I installed the JRE and Java 
Access Bridge for Microsoft Windows Operating System 2.0.1, then I configured 
the JRE environment and turned on 'support assistive technology tools 
trigger'. Eventually JAWS can read all things if I open a odt file using 
OpenOffice Writer, but it can not read the form controls  information if I 
open the odt file with Internet Explorer. I wonder whether it is a bug or 
there are other things need to do for IE? Look forward to your reply, Thanks!
Comment 1 eric.savary 2009-07-29 11:24:30 UTC
@colinguo: can you please do some tests (I cannot check with JAWS right now but
I will do it)?
- Does this happen in OOo too when setting the file as read-only (should be the
6th icon in the Standard toolbar)?
- Does this happen in Firefox too?
- which OOo and JAWS versions do you have?
Comment 2 Olaf Felka 2009-07-29 11:36:01 UTC
OOo documents displayed in a browser are always read-only.
Comment 3 colinguo 2009-07-30 03:37:04 UTC
Hi Wed Jul,

This issue will not happen in OOo when setting the file as read-only, but this 
issue will appear when OOo documents displayed in IE browser.
For Firefox, I found the OOo can not be displayed in it.
The JAWS version I used is 9.0, for OOo I used 2.4 and 3.1.
Thanks!
Comment 4 colinguo 2009-08-31 04:54:10 UTC
Has anyone tried this case?
Could you give me some help about this issue?
Thanks.
Comment 5 Rainer Bielefeld 2010-04-11 08:18:07 UTC
Currently I have some difficulties to understand why this might be an OOo
problem and not a JAWS or IE Problem?

@colinguo:
The Issue tracker is not a user help facility. Please read the FAQ and other
information linked in the left frame of this screen. You can get help from the
public users mailing list users@openoffice.org or on the forum at
<http://user.services.openoffice.org/en/forum/>

I doubt that you have those problems with  OOo 1.0 documents
Comment 6 colinguo 2010-04-12 05:06:44 UTC
Hi rainerbielefeld & OOo Accessibility dev guys,

I am sorry for not updating this issue for long time. The OOo Accessibility is 
very complex problem, I spent a lot of times on this issue, I debug OOo codes 
and find that the so_activex work window which OOo created doesn't have the 
window Style which is required in OOo accessibility. I fixed this issue just 
hacking the below codes.

1. extensions\source\activex\main\SOActiveX.cpp  
HRESULT CSOActiveX::CreateFrameOldWay( HWND hwnd, int width, int height )
- pDescriptorVar[5] = CComVariant( 33 );
+ pDescriptorVar[5] = CComVariant( 9600 );//9600 is special flag.
2. toolkit\source\awt\vclxtoolkit.cxx
Window*	VCLXToolkit::ImplCreateWindow( VCLXWindow** ppNewComp,
	const ::com::sun::star::awt::WindowDescriptor& rDescriptor,
    Window* pParent, WinBits nWinBits )
if( bUseParentData )
{
    ...
    - pNewWindow = new WorkWindow( &aParentData );
    + if(rDescriptor.WindowAttributes == 9600)
    + {
    +  pNewWindow = new WorkWindow( &aParentData, 
WB_SIZEMOVE,WINDOW_WORKWINDOW);
    + }
    + else
    + {
    + pNewWindow = new WorkWindow( &aParentData );
    + }
}
3. vcl\inc\vcl\wrkwin.hxx
+ WorkWindow( SystemParentData* pParent , WinBits nStyle, WindowType nType );
4. vcl\source\window\wrkwin.cxx
+ WorkWindow::WorkWindow( SystemParentData* pParent, WinBits nStyle, 
WindowType nType) :SystemWindow( WINDOW_WORKWINDOW )
+ {
+     ImplInitWorkWindowData();
+     mbSysChild = TRUE;
+    ImplInit( NULL, nStyle, pParent );
+ }
I know my hacking was not best fixing for this issue, I hope OOo accessibility 
dev guys will fix this issue in next release.

rainerbielefeld, thanks for your response.