Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Stuart, I am back from the Spring Festival. Sorry for the late reply. On Sun, Feb 10, 2013 at 2:05 AM, V Stuart Foote vstuart.fo...@utsa.eduwrote: Steve, Nothing substantive yet in working through the Windows build of the ia2 branch. Should we build against Linux and OSX and be testing for impact on ATK/AT-SPI and NSAccessibility User Interface? Agreed. Testing the branch on Linux and OSX is necessary. And, with QA and testing of the ia2 branch proceeding what mechanism should folks use for reporting and tracking issues on the ia2 branch builds? Should we stay with PM and ML exchanges, or start to use Bugzilla at issues.apache.org/ooo? I believe that starting with BZ tracking now provides continuity upon merge of branch back into AOO4.00. Bugzilla may be the best choice. And, if into Bugzilla, would suggest a note in your AOO 4.0 IAccessible2 release planning wiki that QA participants and casual users report in Bugzilla categorized for consistency as against: Product: UI Component: AccessBridge Version: AOO4.00-dev Good suggestion. Thanks. Stuart =-=-= Sidebar--the legacy IAccessible2 enhancement bug could probably be revised https://issues.apache.org/ooo/show_bug.cgi?id=107914 And here is a generic BZ search for accessibility issues https://issues.apache.org/ooo/buglist.cgi?query_format=advancedresolution=---short_desc=msaa%20accessible%20iaccessible%20iaccessible2%20accessibilityshort_desc_type=anywordssubstrorder=component%2Cpriority%2Cbug_severityquery_based_on= -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Andrew I think that binaries URL should be he following, at least for accessing the binaries. http://ci.apache.org/projects/openoffice/#w7ia2 As you point out however they are not there yet. Do you have an ETA? After Stuart's post of the NVDA list there has been quite a bit of discussion and enthusiasm from some NVDA people on Twitter so others may come looking. https://twitter.com/jcsteh/status/301051115502448641 Steve OpenDirective On 10 February 2013 01:14, Andrew Rist andrew.r...@oracle.com wrote: Do you all know about this? http://ci.apache.org/builders/**aoo-w7ia2/http://ci.apache.org/builders/aoo-w7ia2/ We now have an automatic build of the ia2 branch running nightly. (and successfully) It is not loading up install bits for some reason, but I'll look at that and fix it. If you want to see the status of the latest build look for Windows ia2 Branch on this page: http://ci.apache.org/projects/**openoffice/http://ci.apache.org/projects/openoffice/ that page links to the build logs http://ci.apache.org/** projects/openoffice/buildlogs/**w7ia2/log/wntmsci12.pro.build.**htmlhttp://ci.apache.org/projects/openoffice/buildlogs/w7ia2/log/wntmsci12.pro.build.html and the buildbot log http://ci.apache.org/**builders/aoo-w7ia2/builds/6http://ci.apache.org/builders/aoo-w7ia2/builds/6, and should have the latest build of the install packages. Andrew On 2/9/2013 10:05 AM, V Stuart Foote wrote: Steve, Nothing substantive yet in working through the Windows build of the ia2 branch. Should we build against Linux and OSX and be testing for impact on ATK/AT-SPI and NSAccessibility User Interface? And, with QA and testing of the ia2 branch proceeding what mechanism should folks use for reporting and tracking issues on the ia2 branch builds? Should we stay with PM and ML exchanges, or start to use Bugzilla at issues.apache.org/ooo? I believe that starting with BZ tracking now provides continuity upon merge of branch back into AOO4.00. And, if into Bugzilla, would suggest a note in your AOO 4.0 IAccessible2 release planning wiki that QA participants and casual users report in Bugzilla categorized for consistency as against: Product: UI Component: AccessBridge Version: AOO4.00-dev Stuart =-=-= Sidebar--the legacy IAccessible2 enhancement bug could probably be revised https://issues.apache.org/ooo/**show_bug.cgi?id=107914https://issues.apache.org/ooo/show_bug.cgi?id=107914 And here is a generic BZ search for accessibility issues https://issues.apache.org/ooo/**buglist.cgi?query_format=** advancedresolution=---short_**desc=msaa%20accessible%** 20iaccessible%20iaccessible2%**20accessibilityshort_desc_** type=anywordssubstrorder=**component%2Cpriority%2Cbug_** severityquery_based_on=https://issues.apache.org/ooo/buglist.cgi?query_format=advancedresolution=---short_desc=msaa%20accessible%20iaccessible%20iaccessible2%20accessibilityshort_desc_type=anywordssubstrorder=component%2Cpriority%2Cbug_severityquery_based_on=
RE: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Steve, Nothing substantive yet in working through the Windows build of the ia2 branch. Should we build against Linux and OSX and be testing for impact on ATK/AT-SPI and NSAccessibility User Interface? And, with QA and testing of the ia2 branch proceeding what mechanism should folks use for reporting and tracking issues on the ia2 branch builds? Should we stay with PM and ML exchanges, or start to use Bugzilla at issues.apache.org/ooo? I believe that starting with BZ tracking now provides continuity upon merge of branch back into AOO4.00. And, if into Bugzilla, would suggest a note in your AOO 4.0 IAccessible2 release planning wiki that QA participants and casual users report in Bugzilla categorized for consistency as against: Product: UI Component: AccessBridge Version: AOO4.00-dev Stuart =-=-= Sidebar--the legacy IAccessible2 enhancement bug could probably be revised https://issues.apache.org/ooo/show_bug.cgi?id=107914 And here is a generic BZ search for accessibility issues https://issues.apache.org/ooo/buglist.cgi?query_format=advancedresolution=---short_desc=msaa%20accessible%20iaccessible%20iaccessible2%20accessibilityshort_desc_type=anywordssubstrorder=component%2Cpriority%2Cbug_severityquery_based_on=
RE: [Call For QA Volunteers] AOO UI IAccessible2 testing work
From: V Stuart Foote Sent: Saturday, February 09, 2013 12:05 PM And here is a generic BZ search for accessibility issues https://issues.apache.org/ooo/buglist.cgi?query_format=advancedresolution=---short_desc=msaa%20accessible%20iaccessible%20iaccessible2%20accessibilityshort_desc_type=anywordssubstrorder=component%2Cpriority%2Cbug_severityquery_based_on= Sorry, here is a slightly more complete retrieval adding the old ACC: keyword https://issues.apache.org/ooo/buglist.cgi?query_format=advancedlist_id=45172short_desc=ACC%3A%20msaa%20accessible%20iaccessible%20iaccessible2%20accessibilityshort_desc_type=anywordssubstrresolution=---
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Do you all know about this? http://ci.apache.org/builders/aoo-w7ia2/ We now have an automatic build of the ia2 branch running nightly. (and successfully) It is not loading up install bits for some reason, but I'll look at that and fix it. If you want to see the status of the latest build look for Windows ia2 Branch on this page: http://ci.apache.org/projects/openoffice/ that page links to the build logs http://ci.apache.org/projects/openoffice/buildlogs/w7ia2/log/wntmsci12.pro.build.html and the buildbot log http://ci.apache.org/builders/aoo-w7ia2/builds/6, and should have the latest build of the install packages. Andrew On 2/9/2013 10:05 AM, V Stuart Foote wrote: Steve, Nothing substantive yet in working through the Windows build of the ia2 branch. Should we build against Linux and OSX and be testing for impact on ATK/AT-SPI and NSAccessibility User Interface? And, with QA and testing of the ia2 branch proceeding what mechanism should folks use for reporting and tracking issues on the ia2 branch builds? Should we stay with PM and ML exchanges, or start to use Bugzilla at issues.apache.org/ooo? I believe that starting with BZ tracking now provides continuity upon merge of branch back into AOO4.00. And, if into Bugzilla, would suggest a note in your AOO 4.0 IAccessible2 release planning wiki that QA participants and casual users report in Bugzilla categorized for consistency as against: Product: UI Component: AccessBridge Version: AOO4.00-dev Stuart =-=-= Sidebar--the legacy IAccessible2 enhancement bug could probably be revised https://issues.apache.org/ooo/show_bug.cgi?id=107914 And here is a generic BZ search for accessibility issues https://issues.apache.org/ooo/buglist.cgi?query_format=advancedresolution=---short_desc=msaa%20accessible%20iaccessible%20iaccessible2%20accessibilityshort_desc_type=anywordssubstrorder=component%2Cpriority%2Cbug_severityquery_based_on=
RE: [Call For QA Volunteers] AOO UI IAccessible2 testing work
From: V Stuart Foote Sent: Tuesday, February 05, 2013 8:25 PM Going to try removing JRE 1.7u11 and backing up to 1.6u39 to see if that has an impact, but if IAccessibile2 is functional--should not need a JRE, right? So an uninstall of JRE 1.7u11 did set everything right with this initial build of the ia2 branch, a big thanks Ariel for building and posting to get the QA effort rolling. And congratulations to Steve and all the ia2 branch team for some very solid work on the merge! With no JRE the, Open Accessibility (A11y) group's AccProbe Eclipse RCP can not run, but comfortable to say the \winaccessibility IAccessible2 implementation is already matching support Symphony 3.0.1 fix pack 2 for basic MSAA/IAccessible IAccessible2 roles. Folks doing QA will need to use AccProbe so should go ahead and install either JRE 1.6u39 or JRE 1.7u13, but Java Access Bridge is NOT a requirement for full function of the ia2 branch. Since I still fight with LibreOffice and the JAB I went with the JRE 1.6u39 install--the JRE 1.7 builds with JAB 2.0.3 are still a problem ( https://issues.apache.org/ooo/show_bug.cgi?id=121510 ) Only a couple of hours into the interface and working out the testing tools--the a11y project's AccProbe is going to need some work, but it or something similar is necessary for working on correctness of IAccessibility2 events and roles. I have to dig deeper, but I do think there are some pretty big holes in what is instrumented. At the same time, I found Microsofts AccEvent and especially the Inspect tools from the Windows 8 SDK very helpful. I started leaving the Inspect panel running minimized and popping it open to review non-sounding actions in the GUI. And if working with a screen reader, folks should note that when using a current release of NVDA (2012.3.1) the NV Access developers have put a lot of effort into the project to read UI Automation and MSAA events--so it is not purely dependent on IAccessible2 rendering of UNO Accessibility API roles and events for the user interface. Its a hybrid, but it is already working as well with the ia2 branch as with the last Symphony builds and I think on a par with GNOME Orca for LibreOffice, I don't have access to JAWS but suspect there will be similar improvements in fidelity over Java Access Bridge based Accessibility and AT support there as well.
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Ariel, Well done! Thanks! On Tue, Feb 5, 2013 at 3:48 PM, Ariel Constenla-Haile arie...@apache.orgwrote: Hi Steve, On Tue, Feb 05, 2013 at 03:36:05PM +0800, Steve Yin wrote: Hi Ariel, Can you try to run it as administrator? I am afraid that the user privilege cannot modify the registry on Windows 7. The AOO branch build need to register the UaccCom.dll as a COM component. I tried NVDA under Win 7 x64 and Win XP as administrator. It works fine. You were right, now it works, even toolbar icons are read now, nice work! Regards -- Ariel Constenla-Haile La Plata, Argentina -- Best Regards, Steve Yin
RE: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Steve, Ariel Installed Ariel's posted ia2 branch build Run as Administrator, and also captured a verbose install log. AOO350m1(Build:9611) - Rev. 1441343 2013-02-04 20:38:26 -0300 (lun, 04 feb 2013) Windows 7 sp1 64-bit Oracle Java JRE 1.7u11 Verified the UaccCOM.dll is registered at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\B4197A678F2F566AC9CE342EB80665B2 as 346FD3847C37D3440BBCC0FF600F4DEA with a string value of C:\Program Files (x86)\Apache OpenOffice 3\program\UAccCOM.dll However, when running the ia2 branch as a user in the Administrators group, and monitoring with a11y's AccProbe Eclipse RCP probe as well as the MS AccEvent I am not seeing IAccessible2 events, only MSAA. The UI Access mode of AccEvent listings are also very sparse. Kind of interesting is that AccProbe shows all only a few of the msaa components howFound from Navigating the Tree--with most howFound values of AtPoint:java.awt.Point from browsing the GUI. No event tracking in the probes--and it follows that NVDA is mute. Am I missing something? Ariel on your Windows box are you running an Oracle 7 JRE, or Just the JDK 6 you built against? Going to try removing JRE 1.7u11 and backing up to 1.6u39 to see if that has an impact, but if IAccessibile2 is functional--should not need a JRE, right? Stuart
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Stuart, On Wed, Feb 06, 2013 at 02:25:13AM +, V Stuart Foote wrote: Steve, Ariel Installed Ariel's posted ia2 branch build Run as Administrator, and also captured a verbose install log. AOO350m1(Build:9611) - Rev. 1441343 2013-02-04 20:38:26 -0300 (lun, 04 feb 2013) Windows 7 sp1 64-bit Oracle Java JRE 1.7u11 Verified the UaccCOM.dll is registered at: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\B4197A678F2F566AC9CE342EB80665B2 as 346FD3847C37D3440BBCC0FF600F4DEA with a string value of C:\Program Files (x86)\Apache OpenOffice 3\program\UAccCOM.dll However, when running the ia2 branch as a user in the Administrators group, Note that I am also in the Administrators category, but it didn't work, I had to run OpenOffice as Administrator (right-click on the Desktop shortcut, select Run as administrator). and monitoring with a11y's AccProbe Eclipse RCP probe as well as the MS AccEvent I am not seeing IAccessible2 events, only MSAA. The UI Access mode of AccEvent listings are also very sparse. Kind of interesting is that AccProbe shows all only a few of the msaa components howFound from Navigating the Tree--with most howFound values of AtPoint:java.awt.Point from browsing the GUI. No event tracking in the probes--and it follows that NVDA is mute. Am I missing something? Ariel on your Windows box are you running an Oracle 7 JRE, or Just the JDK 6 you built against? I have several Java versions, OpenOffice is configured to run with JRE 7. Going to try removing JRE 1.7u11 and backing up to 1.6u39 to see if that has an impact, but if IAccessibile2 is functional--should not need a JRE, right? When running as a normal user (even in the Administrators category), OpenOffice was using Java, the ia2 component and COM were not even loaded; running the program as administrator made ia2 work. Regards -- Ariel Constenla-Haile La Plata, Argentina pgp42LGXomddD.pgp Description: PGP signature
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Steve, Great work! Hope to be able to get to work on QA of the ia2 branch soon. From: Steve Yin [mailto:steve.yin@gmail.com] Sent: Sunday, February 3, 2013 7:10 PM snip Yes, the branch ia2 is ready for QA now. The earlier the power users involve, the faster project progress we can expect. Since we are a while out from a nightly build incorporating the ia2 branch, we'll need to roll our own. Any particular configuration controls you'd recommend to have in place for QA for builds of the ia2 branch for Windows OS? Something similar to the Software requirements you'd posted for doing a Symphony build (http://wiki.openoffice.org/wiki/How_to_build_Symphony%27s_source_code#Building_Symphony_on_Windows) Any chance of having Oliver-orw at apache.org--or one of your IBM Beijing team, cobble together and post a Windows build of the ia2 branch to standardize any QA work. Finally, noted your exchange with Simon Liu From: Steve Yin [mailto:steve.yin@gmail.com] Sent: Friday Jan 25, 2013 6:03 AM snip For the AOO IAccessible2 testing tools, I think a screen reader which can support IA2 is required. We recommand JAWS for IA2 testing. And for the IA2 attributes or events information testing, AccProbe is preferred. Of course those only cover Linux testing. For IAccessibility2 testing of ia2 in Windows, the QA and testers would probably need Inspect.exe and AccEvent.exe from the Microsoft Windows SDK as those are the best tools for monitoring MSAA/IAccessible and UI Automation. Also, in addition to JAWS, a current build of NVDA would be helpful. And I'm sure Jamie Teh at NV Access has some solid Python utilities for use with exposing events in Windows Stuart Foote
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Stuart, Welcome! The configuration of the ia2 branch is same with the trunk. http://wiki.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows But we need Visual C++ 2008 Professional with parameters--enable-activex and--enable-atl to compile the branch. And I plan to upload the developer-snapshots to a space for QA. Inspect and AccEvent can only show the MSAA stuff. AccProbe can fully show MSAA and IA2 information. Yes, NVDA is a recommend screen reader for IA2 testing. If Jamie can provide utilities to community, it couldn't be better. Thanks! On Tue, Feb 5, 2013 at 7:36 AM, V Stuart Foote vstuart.fo...@utsa.eduwrote: Steve, Great work! Hope to be able to get to work on QA of the ia2 branch soon. From: Steve Yin [mailto:steve.yin@gmail.com] Sent: Sunday, February 3, 2013 7:10 PM snip Yes, the branch ia2 is ready for QA now. The earlier the power users involve, the faster project progress we can expect. Since we are a while out from a nightly build incorporating the ia2 branch, we'll need to roll our own. Any particular configuration controls you'd recommend to have in place for QA for builds of the ia2 branch for Windows OS? Something similar to the Software requirements you'd posted for doing a Symphony build ( http://wiki.openoffice.org/wiki/How_to_build_Symphony%27s_source_code#Building_Symphony_on_Windows ) Any chance of having Oliver-orw at apache.org--or one of your IBM Beijing team, cobble together and post a Windows build of the ia2 branch to standardize any QA work. Finally, noted your exchange with Simon Liu From: Steve Yin [mailto:steve.yin@gmail.com] Sent: Friday Jan 25, 2013 6:03 AM snip For the AOO IAccessible2 testing tools, I think a screen reader which can support IA2 is required. We recommand JAWS for IA2 testing. And for the IA2 attributes or events information testing, AccProbe is preferred. Of course those only cover Linux testing. For IAccessibility2 testing of ia2 in Windows, the QA and testers would probably need Inspect.exe and AccEvent.exe from the Microsoft Windows SDK as those are the best tools for monitoring MSAA/IAccessible and UI Automation. Also, in addition to JAWS, a current build of NVDA would be helpful. And I'm sure Jamie Teh at NV Access has some solid Python utilities for use with exposing events in Windows Stuart Foote -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Ariel, Thanks for your build! The bug you mentioned is about a JAB issue of JAVA 1.7. The IAccessible2 bridge does not relate to JAVA. You can simple enable ia2 on the branch AOO build by running a AT tool such JAWS, NVDA or AccProbe. AOO will automatically enable the IA2 bridge. On Tue, Feb 5, 2013 at 12:36 PM, Ariel Constenla-Haile arie...@apache.orgwrote: On Mon, Feb 04, 2013 at 11:36:39PM +, V Stuart Foote wrote: Steve, Great work! Hope to be able to get to work on QA of the ia2 branch soon. From: Steve Yin [mailto:steve.yin@gmail.com] Sent: Sunday, February 3, 2013 7:10 PM snip Yes, the branch ia2 is ready for QA now. The earlier the power users involve, the faster project progress we can expect. Since we are a while out from a nightly build incorporating the ia2 branch, we'll need to roll our own. Any particular configuration controls you'd recommend to have in place for QA for builds of the ia2 branch for Windows OS? Something similar to the Software requirements you'd posted for doing a Symphony build ( http://wiki.openoffice.org/wiki/How_to_build_Symphony%27s_source_code#Building_Symphony_on_Windows ) Any chance of having Oliver-orw at apache.org--or one of your IBM Beijing team, cobble together and post a Windows build of the ia2 branch to standardize any QA work. I uploaded my build to http://people.apache.org/~arielch/packages/ia2/ I've played with https://issues.apache.org/ooo/show_bug.cgi?id=121510 and still find it broken, but as I don't know much about accessibility, I leave it to you to find out :) Regards -- Ariel Constenla-Haile La Plata, Argentina -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Steve, On Tue, Feb 05, 2013 at 01:35:04PM +0800, Steve Yin wrote: Hi Ariel, Thanks for your build! The bug you mentioned is about a JAB issue of JAVA 1.7. The IAccessible2 bridge does not relate to JAVA. You can simple enable ia2 on the branch AOO build by running a AT tool such JAWS, NVDA or AccProbe. AOO will automatically enable the IA2 bridge. I tried it with NVDA version 2012.3.1 (looks like a date, I took it from their About dialog). What I wanted to mean is that the behaviour described in the bug is reproducible with ia2: - create a new Writer document - select Edit - Find Replace... NVDA reads the controls in the Find Replace... dialog when I position the mouse over the control, but if a travel the dialog using the TAB key, NVDA does not read any control. On the other Windows applications, when a control gets the focus traveling with the TAB key, NVDA reads it. I attached the VS2008 debugger to the soffice.bin process, winaccesibility.dll and UAccCOM.dll are not listed among the loaded modules. IAccesible2Proxy.dll, minHook.dll and nvdaHelperRemote.dll, from NVDA, are loaded. May I missed something in the NVDA set up, or is there something we have to configure on AOO at runtime? I already checked Tools - Options... - AOO - Accessibility - Miscellaneous options - Support assistive technology tools (program restart required) Regards -- Ariel Constenla-Haile La Plata, Argentina pgpkDa63O0gzE.pgp Description: PGP signature
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Ariel, Checking support assistive technology tools is unnecessary for the branch build. Did you run the AOO build with administrator privilege? On Tue, Feb 5, 2013 at 2:08 PM, Ariel Constenla-Haile arie...@apache.orgwrote: Hi Steve, On Tue, Feb 05, 2013 at 01:35:04PM +0800, Steve Yin wrote: Hi Ariel, Thanks for your build! The bug you mentioned is about a JAB issue of JAVA 1.7. The IAccessible2 bridge does not relate to JAVA. You can simple enable ia2 on the branch AOO build by running a AT tool such JAWS, NVDA or AccProbe. AOO will automatically enable the IA2 bridge. I tried it with NVDA version 2012.3.1 (looks like a date, I took it from their About dialog). What I wanted to mean is that the behaviour described in the bug is reproducible with ia2: - create a new Writer document - select Edit - Find Replace... NVDA reads the controls in the Find Replace... dialog when I position the mouse over the control, but if a travel the dialog using the TAB key, NVDA does not read any control. On the other Windows applications, when a control gets the focus traveling with the TAB key, NVDA reads it. I attached the VS2008 debugger to the soffice.bin process, winaccesibility.dll and UAccCOM.dll are not listed among the loaded modules. IAccesible2Proxy.dll, minHook.dll and nvdaHelperRemote.dll, from NVDA, are loaded. May I missed something in the NVDA set up, or is there something we have to configure on AOO at runtime? I already checked Tools - Options... - AOO - Accessibility - Miscellaneous options - Support assistive technology tools (program restart required) Regards -- Ariel Constenla-Haile La Plata, Argentina -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Steve, On Tue, Feb 05, 2013 at 02:54:19PM +0800, Steve Yin wrote: Hi Ariel, Checking support assistive technology tools is unnecessary for the branch build. Did you run the AOO build with administrator privilege? No, I launched it from the start menu on Windows 7, as normal user. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpGV5vuDTiRG.pgp Description: PGP signature
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Ariel, Can you try to run it as administrator? I am afraid that the user privilege cannot modify the registry on Windows 7. The AOO branch build need to register the UaccCom.dll as a COM component. I tried NVDA under Win 7 x64 and Win XP as administrator. It works fine. Thanks. On Tue, Feb 5, 2013 at 2:58 PM, Ariel Constenla-Haile arie...@apache.orgwrote: Hi Steve, On Tue, Feb 05, 2013 at 02:54:19PM +0800, Steve Yin wrote: Hi Ariel, Checking support assistive technology tools is unnecessary for the branch build. Did you run the AOO build with administrator privilege? No, I launched it from the start menu on Windows 7, as normal user. Regards -- Ariel Constenla-Haile La Plata, Argentina -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Steve, Yes, the branch ia2 is ready for QA now. The earlier the power users involve, the faster project progress we can expect. Good idea! I hope NVDA dev team can join AOO IA2 dev work now. NVDA and Symphony had ever corroborated for a while in 2010, they are very professional and enthusiastic. Your initial testing is welcome. It will be helpful for IA2 QA work. I am sorry that I did not attend the event. I hope we can meet in the near future. : ) Thanks. On Sat, Feb 2, 2013 at 11:34 PM, Steve Lee st...@opendirective.com wrote: Hi Steve, thanks Don It's good to hear you have progressed so far already. Is the work in a state ready for testing by some screen reader users who are very technical? If you have binaries or they are easy enough create I suggest we bring in the NVDA dev team in now or very soon. They have been wanting IA2 in [A]OO for a long time, but in it's absence have been recommending Symphony to their users; the Java Access Bridge is a real pain for their users to install. They will obviously give a very thorough testing and should engage well at a deep technical level. One of the NVDA contributors has provided the Arabic support so we'd get broad extra testing of IA2 with i18n and RTL languages. If you feel you are ready then let me know and I will make the introductions. http://www.nvda-project.org/ Otherwise how can I help? I have restricted cycles for the next week or 2. I could do some initial 'gorilla testing'. PS Steve did we meet in Boston at a Mozilla/GNOME a11y event? Steve Lee Programme Leader (Open Accessibility) OpenDirective http://opendirective.com On 1 February 2013 14:29, Steve Yin steve.yin@gmail.com wrote: Hi Steve and Don, Thanks Don. Welcome Steve Lee! Now we can do more on AOO accessibility testing, not only IA2. : ) On Fri, Feb 1, 2013 at 8:46 PM, Donald Harbison dpharbi...@gmail.com wrote: Hi Steve Yin, Steve Lee from OpenDirectives is keen to help get the testing started. He's new to AOO, but an old hand with A11Y work. He's very well connected to the accessibility community and will be able to help us connect with experts for the testing process. Take it away Steve (Lee), /don On Mon, Jan 28, 2013 at 1:46 AM, Steve Yin steve.yin@gmail.com wrote: Hi Diego Valle, Welcome to join AOO IAccessible2 QA work. We will prepare QA cases and assign some of them to you. And I hope we can work together at the beginning. On Sun, Jan 27, 2013 at 6:44 AM, Diego Valle Rosado diegogvalleros...@gmail.com wrote: Hello My name is diego valle.At the moment I study the career IT in Quintana Roo, Mexico. I'm interested in AOO IAccessible2 testing work and I'd like to be a QA volunteer. Would be a great way to learn how to get started programming OpenOffice and to help bring the benefits of OpenOffice to my country and the region where I live. Regards Diego Valle 2013/1/25 Steve Yin steve.yin@gmail.com Hi all, The UI part of the AOO IAccessible2 migration dev work will be done in a few days. We need QA volunteers to join the testing work and ensure the migration quality. This work will be started on the branch ia2. https://svn.apache.org/repos/asf/openoffice/branches/ia2 If you are interested in AOO IAccessible2 testing work, please reply this mail. Thanks. -- Best Regards, Steve Yin -- Best Regards, Steve Yin -- Best Regards, Steve Yin -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Steve Yin, Steve Lee from OpenDirectives is keen to help get the testing started. He's new to AOO, but an old hand with A11Y work. He's very well connected to the accessibility community and will be able to help us connect with experts for the testing process. Take it away Steve (Lee), /don On Mon, Jan 28, 2013 at 1:46 AM, Steve Yin steve.yin@gmail.com wrote: Hi Diego Valle, Welcome to join AOO IAccessible2 QA work. We will prepare QA cases and assign some of them to you. And I hope we can work together at the beginning. On Sun, Jan 27, 2013 at 6:44 AM, Diego Valle Rosado diegogvalleros...@gmail.com wrote: Hello My name is diego valle.At the moment I study the career IT in Quintana Roo, Mexico. I'm interested in AOO IAccessible2 testing work and I'd like to be a QA volunteer. Would be a great way to learn how to get started programming OpenOffice and to help bring the benefits of OpenOffice to my country and the region where I live. Regards Diego Valle 2013/1/25 Steve Yin steve.yin@gmail.com Hi all, The UI part of the AOO IAccessible2 migration dev work will be done in a few days. We need QA volunteers to join the testing work and ensure the migration quality. This work will be started on the branch ia2. https://svn.apache.org/repos/asf/openoffice/branches/ia2 If you are interested in AOO IAccessible2 testing work, please reply this mail. Thanks. -- Best Regards, Steve Yin -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Hi Diego Valle, Welcome to join AOO IAccessible2 QA work. We will prepare QA cases and assign some of them to you. And I hope we can work together at the beginning. On Sun, Jan 27, 2013 at 6:44 AM, Diego Valle Rosado diegogvalleros...@gmail.com wrote: Hello My name is diego valle.At the moment I study the career IT in Quintana Roo, Mexico. I'm interested in AOO IAccessible2 testing work and I'd like to be a QA volunteer. Would be a great way to learn how to get started programming OpenOffice and to help bring the benefits of OpenOffice to my country and the region where I live. Regards Diego Valle 2013/1/25 Steve Yin steve.yin@gmail.com Hi all, The UI part of the AOO IAccessible2 migration dev work will be done in a few days. We need QA volunteers to join the testing work and ensure the migration quality. This work will be started on the branch ia2. https://svn.apache.org/repos/asf/openoffice/branches/ia2 If you are interested in AOO IAccessible2 testing work, please reply this mail. Thanks. -- Best Regards, Steve Yin -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Steve, Thanks very much for your work on the Accessibility development work! For the calling for Accessibility QA volunteers, I wonder if there is any skill requirement, or tool that we prefer to use in testing? - Shenfeng (Simon) 2013/1/25 Steve Yin steve.yin@gmail.com Hi all, The UI part of the AOO IAccessible2 migration dev work will be done in a few days. We need QA volunteers to join the testing work and ensure the migration quality. This work will be started on the branch ia2. https://svn.apache.org/repos/asf/openoffice/branches/ia2 If you are interested in AOO IAccessible2 testing work, please reply this mail. Thanks. -- Best Regards, Steve Yin
Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work
Great works, Steve, Well done! And I think you may give some certain corresponding FVT cases to the QA volenteers, if there exist. 2013/1/25 Steve Yin steve.yin@gmail.com Hi Simon, For the AOO IAccessible2 testing tools, I think a screen reader which can support IA2 is required. We recommand JAWS for IA2 testing. And for the IA2 attributes or events information testing, AccProbe is preferred. Link for AccProbe: http://accessibility.linuxfoundation.org/a11yweb/util/accprobe/ Link for JAWS: http://www.freedomscientific.com/products/fs/jaws-product-page.asp The demo JAWS is fully functional, but require a computer reboot after 40 minutes if you wish to continue using the product. As an IAccessble2 QA volunteer, you may need to know how to use JAWS, such as the JAWS functions and their short cut keys. Using AccProble can view the IA2 attributes and events. The document for IAccessible2 API can be found here http://www.linuxfoundation.org/collaborate/workgroups/accessibility/iaccessible2 . In short, for the accessibility testing, what we need is to simulate blind users, try to find no accessible parts of the application and fix them. Thanks. On Fri, Jan 25, 2013 at 5:49 PM, Shenfeng Liu liush...@gmail.com wrote: Steve, Thanks very much for your work on the Accessibility development work! For the calling for Accessibility QA volunteers, I wonder if there is any skill requirement, or tool that we prefer to use in testing? - Shenfeng (Simon) 2013/1/25 Steve Yin steve.yin@gmail.com Hi all, The UI part of the AOO IAccessible2 migration dev work will be done in a few days. We need QA volunteers to join the testing work and ensure the migration quality. This work will be started on the branch ia2. https://svn.apache.org/repos/asf/openoffice/branches/ia2 If you are interested in AOO IAccessible2 testing work, please reply this mail. Thanks. -- Best Regards, Steve Yin -- Best Regards, Steve Yin
