Jamie,

Date: Tue, 12 Feb 2013 05:21:02 +1000

From: James Teh <ja...@nvaccess.org<mailto:ja...@nvaccess.org>>

To: NVDA screen reader development

Subject: Re: [NVDA-dev] Apache Open Office IAccessible2 QA ia2 branch

      builds



>Hi Stuart,

>Thanks for letting us know. Initial testing is very promising. I'm

>working on a few tweaks to get NVDA to use some of its custom code for

>symphony to allow for reporting of formatting, etc. (Unfortunately,

>Symphony's IA2 implementation doesn't follow the IA2 standard in some

>areas, though we've already worked around this.)



Yes I've spent a bit more time with it, and Steve Yin's folks have done a 
superb job so far. I am concerned though that you see "non-standard" IA2, 
because while the ia2 Branch builds thus far have been for Windows testing, 
assume that other accessibility components of the Symphony contributed code 
will also be merged in some fashion.



Assume you'd like things to be IAccessible2 1.2.1 and better draft 1.3 
compliant. But that will mean some work under the hood to move the Symphony ia2 
code base onto the emerging standards for IAccessible2. Obviously lots of work, 
and at this point Steve Yin characterizes the work on IAccessible2 at only 5% 
complete-so for getting collaboration on standards compliance in place--now is 
the best time.



Also, for the other bridges--ATK/AT-SPI and NSAccessible--and their mappings of 
the existing UNO Accessibility API, this ongoing work on a native Windows 
bridge offers an opportunity to clean up and redefine incomplete or inadequate 
roles and mappings to bring all the APIs equivalent correcting any omissions. 
And I'd hope that once started, the whole UNO Accessibility API could 
ultimately be systematically extended to support needs of all the ISO/IEC 
13066-1 parts for improving AT.



>I found and read the mailing list thread about this support and saw your

>question about bug tracking, but there hasn't been a response yet. I'll

>check the thread from time to time, but it'd be great if you could let

>us know once a decision has been made about bug tracking. I'm hoping for

>Bugzilla, as this makes for better tracking and I'd rather not be

>swamped by the general ooo-dev list. :)



Will keep an eye out for response. Will post back to the nvda-dev forum any 
guidance.

Stuart

Quick refs:
AOO 4.0 IAccessible2 - 
https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+IAccessible2
Why IAccessible2 - http://wiki.openoffice.org/wiki/Why_IAccessibile2

Reply via email to