Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work

[Steve Lee]

On 13 February 2013 01:18, Andrew Rist  wrote:

>
> On 2/12/2013 5:57 AM, Steve Lee wrote:
>
>> Andrew
>>
>> I think that binaries URL should be he following, at least for accessing
>> the binaries.
>>
>> http://ci.apache.org/projects/**openoffice/#w7ia2<http://ci.apache.org/projects/openoffice/#w7ia2>
>>
>> As you point out however they are not there yet. Do you have an ETA?
>>
>
> ETA is now.
> http://ci.apache.org/projects/**openoffice/#w7ia2<http://ci.apache.org/projects/openoffice/#w7ia2>
>
> Andrew
>
> (actually - it's a bit of a Wizard of Oz thing, as they've actually been
> there all along...)
>

Thanks Andrew, I will pass it on
("We're off to see the Wizard...)

Steve

>
>> 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<https://twitter.com/jcsteh/status/301051115502448641>
>>
>> Steve
>> OpenDirective
>>
>> On 10 February 2013 01:14, Andrew Rist  wrote:
>>
>>  Do you all know about this?
>>> http://ci.apache.org/builders/aoo-w7ia2/<http://ci.apache.org/builders/**aoo-w7ia2/>
>>> <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/>
>>> <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.**html<http://ci.apache.**org/projects/openoffice/**
>>> buildlogs/w7ia2/log/wntmsci12.**pro.build.html<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<http://ci.apache.org/**builders/aoo-w7ia2/builds/6>
>>> 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<https://issues.apache.org/ooo/**show_bug.cgi?id=107914>
>>>> 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=**<https://issues.apache.org/ooo/**buglist.cgi?query_format=**>
>>>> advanced&resolution=---&short_desc=msaa%20accessible%**
>>>> 20iaccessible%20iaccessible2%20accessibility&short_desc_**
>>>> type=anywordssubstr&order=component%2Cpriority%2Cbug_**
>>>> severity&query_based_on=>>> buglist.cgi?query_format=**advanced&resolution=---&short_**
>>>> desc=msaa%20accessible%**20iaccessible%20iaccessible2%**
>>>> 20accessibility&short_desc_**type=anywordssubstr&order=**
>>>> component%2Cpriority%2Cbug_**severity&query_based_on=<https://issues.apache.org/ooo/buglist.cgi?query_format=advanced&resolution=---&short_desc=msaa%20accessible%20iaccessible%20iaccessible2%20accessibility&short_desc_type=anywordssubstr&order=component%2Cpriority%2Cbug_severity&query_based_on=>
>>>> >
>>>>
>>>>
>>>>
>

Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work

[Steve Lee]

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  wrote:

> 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  projects/openoffice/buildlogs/**w7ia2/log/wntmsci12.pro.build.**html>
> and the buildbot log 
> >,
> 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=**
>> advanced&resolution=---&short_**desc=msaa%20accessible%**
>> 20iaccessible%20iaccessible2%**20accessibility&short_desc_**
>> type=anywordssubstr&order=**component%2Cpriority%2Cbug_**
>> severity&query_based_on=
>>
>>
>

Re: [Call For QA Volunteers] AOO UI IAccessible2 testing work

[Steve Lee]

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  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 
> 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 
>> 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 
>> > >
>> > > > 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

Re: AOO.Next IBM Priorities

[Steve Lee]

Steve Lee
OpenDirective - opendirective.com
On Nov 2, 2012 7:59 AM, "Andre Fischer"  wrote:
>
> On 01.11.2012 17:45, robert_w...@us.ibm.com wrote:
>>
>> A quick note, wearing my "IBM hat".
>>
>> We (IBM) have consulted with customers, internal users, other IBM product
>> teams, on what our (IBM's) development priorities should be for the next
>> AOO release.  Obviously, we're not the only ones with priorities or
>> interests or opinions.  We don't make AOO decisions by ourselves.  But we
>> want to be transparent about what our own priorities are, for our
>> employees participating in the AOO community, and what they will be
>> focusing on.   As we did with AOO 3.4.0 and 3.4.1, we'll be putting the
>> details onto the wiki over the next couple of weeks.  You'll hear more at
>> ApacheCon, but I wanted you to hear it hear first.
>>
>> Our top priorities:
>>
>> -- Improve the install and deployment experience, especially by
supporting
>> digital signatures on installs, and introducing a new incremental update
>> feature, so users are not required to download and install a full image
>> for just a minor update.
>>
>> -- A major UI enhancement, a sidebar framework for the editors, ported
>> over from Symphony, and including an API.  If you recall, Symphony won
>> quite a lot of praise for its UI, and much of this was due to the sidebar
>> panel.  I think we can make a good argument that this approach, say
>> compared to the MS Office "ribbon" is a better use of screen real-estate,
>> especially as we see more frequent use of wide screen displays.
>>
>> -- Improved Table of Contents in Writer
>>
>> -- Improved system integration on Windows and MacOS, including possible
>> adoption of "gestures".
>>
>> -- IAccessible2 bridge, ported over from Symphony, to improve
>> accessibility.  This is a major effort, but very important.
>
>
> I will be talking about IAccessible2 as stand in for Steve Yin at the
ApacheCon.
> Please meet me there at 11:45am on Nov 6 (Level 1 Left).

Andre, sorry to mid your talk but I will check the slides. I have 2 points
of information regarding the usefulness of the  IAccessible2 work. Neither
are new but I thought worth restating now to support it being a priority..

1: I just had a conversation with one of developers of NVDA, the popular
screen reader for blind access on Windows. He said right now the Windows
Accessibility story is "terrible" in OSS office solutions. To repeat a
previous observation, there is a real demand for this from the
Accessibility community. This need is also wider than the those using
assistive technology who have visual impairments.

2: I also spotted Hubert Duerr's talk on automated testing in the ApacheCon
programme and thought it worth mentioning that Accessibility APIs provides
a powerful way to automate testing of and via the user interface. At least
2 Linux desktop testing frameworks take this approach using AT/API which is
similar to IA2. I'm sure appealing to the testing market was the reason
Microsoft named their updated Accessibility API "User Interface Automation,
UIA"

Steve Lee
Open Directive

>> -- Closer integration of clipart and template libraries with user
>> experience.
>>
>> -- Update branding and visual styling, contemporary and compelling, fresh
>> and relevant.
>>
>> -- Social integration, allow our users to quickly and easily share their
>> thoughts in a way that compliment their commercial social behavior.
>> Explore the integration of consumer service-specific capabilities as well
>> as generic Share... actions.
>>
>> -- And many other smaller items
>>
>> Obviously the release date for this cannot be pinned down so early, and
>> releasing is PMC decision, not an IBM one.  But we think that this work
>> could be completed and tested for a release in the March/April 2013
>> time-frame.  And the scope of the release might be significant enough to
>> warrant a "4.0" designation.
>>
>> In any case, we'll soon set up a page on the wiki to collect these items.
>> As always, I invite you to add your own priorities to the wiki, things
>> that you would like to work on.  This could be a new feature.  Or, if one
>> of the above items sound interesting to you, we always welcome help
>> designing and implementing these features.
>>
>> Regards,
>>
>> -Rob
>>
>>
>>
>>
>