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
