You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Deyla Jacopo <JD...@Regione.Emilia-Romagna.it> on 2014/03/25 13:06:05 UTC
the right Accessibility configuration
Hi, I'd like to help test accessibility of 4.1.0
because I'm testing OO with win xp Jaws (from 9 to 14) for an Italin Public Admistration that's "switchin" to OO.
2 issues:
1 -configuration
2 - bug not opening OO
#1
I'd like to know what's the right configuration for OO + Java in order to check it correctly and give you feedback.
I've tested the official OO beta (see #2) with WinXP Java 1.7.0 without accessbridge and with accessbridge 2.0.2 (but I think this is no more necessary).
In any case, it works poorely, and I'm afraid that's because of something I'm doing wrong.
#2
I've downloaded and installed both the yesterday's italian and english versions (1579169) from here
http://ci.apache.org/projects/openoffice/#w7ia2
but it closes in the loading screen (after 1/3) is ther a way to tell you what blocks it?
(starting in maintenance mode or something similar)
thx
Jacopo Deyla
Regione Emilia-Romagna
Direzione Generale Organizzazione, Sistemi Informativi e Telematica
Servizio Sistema Informativo Informatico Regionale
Viale Aldo Moro, 30 [203] - 40127 Bologna - ITALIA
Tel. +39 051.527.3113 - Fax +39 051.527.3533/3146
E-mail: jdeyla@regione.emilia-romagna.it<ma...@regione.emilia-romagna.it>
===========================================
In your web projects try to:
1. Start with needs*
2. Do less
3. Design with data
4. Do the hard work to make it simple
5. Iterate. Then iterate again.
6. Build for inclusion
7. Understand context
8. Build digital services, not websites
9. Be consistent, not uniform
10.Make things open: it makes things better
*user needs not government needs
=================================================
These are just the U.K. Government Digital Service Design Principles
Re: the right Accessibility configuration
Posted by Andrea Pescetti <pe...@apache.org>.
On 28/03/2014 Andrea Pescetti wrote:
> Hello Jacopo, ...
> Are you saying that you can't even launch OpenOffice the first time?
For the record, this could be related to this bug:
https://issues.apache.org/ooo/show_bug.cgi?id=124573
Fixes were committed over the last 24 hours to trunk (last: revision
1583887), so either you wait for the next snapshot (it will likely be
copied to the AOO410 branch soon) or you try with a daily trunk build
with a higher revision number.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: the right Accessibility configuration
Posted by Andrea Pescetti <pe...@apache.org>.
On 25/03/2014 Rob Weir wrote:
> On Tue, Mar 25, 2014 at 8:06 AM, Deyla Jacopo
> <JD...@regione.emilia-romagna.it> wrote:
>> Hi, I'd like to help test accessibility of 4.1.0 ...
>> #2
>> I've downloaded and installed both the yesterday's italian and english versions (1579169) from here
>> http://ci.apache.org/projects/openoffice/#w7ia2
> I'm not sure whether that snapshot is being built from the 410 branch
> (which should be stable) or the trunk (which may have issues).
Hello Jacopo,
indeed the "Windows ia2 Branch Install Packages" are outdated and not
available in Italian anyway (they are the last two files listed in the
page, and that section is a leftover from when ia2 was still a
development branch; it was integrated several months ago).
The daily builds come from our (unstable) trunk and as Rob explained
they are "bleeding edge" and do not reflect what will appear in 4.1.0.
Development builds from the AOO410 branch can be found at
http://www.openoffice.org/download/ (right column, Additional
Resources). Chances are that these are the same builds you actually
downloaded, even if you meant to download the ia2 builds. So if you
found severe issues in them, we are certainly interested in knowing
more. They reflect quite closely what we expect to release as version 4.1.0.
Are you saying that you can't even launch OpenOffice the first time? Are
you installing over an existing user profile? See
http://s.apache.org/profilo for some tips on how to start with a clean
profile, on an Italian version of Windows.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
R: R: the right Accessibility configuration
Posted by Deyla Jacopo <JD...@Regione.Emilia-Romagna.it>.
Got it Stuart,
now everithing is clear.
So as I supposed I was already using the right configuration (JRE 1.7.0 with no access bridge)
Unfortunately JAWS in my organization is still The screen reader and a switch to NVDA has been evaluated and postoponet when it will be more mature (at least 1 or 2 years).
NVDA works great when everithing works, and as a portable screen reader,
but Jaws is more capable of making its way trough deep (inaccessible) space.
thx
Jacopo
-----Messaggio originale-----
Da: V Stuart Foote [mailto:VStuart.Foote@utsa.edu]
Inviato: martedì 25 marzo 2014 16.17
A: ooo-dev@incubator.apache.org
Oggetto: Re: R: the right Accessibility configuration
Deyla,
Actually Windows accessibility in Apache OpenOffice no longer makes any use of the Java Accessibility Bridge to interface to the Java Accessibility API installed with a JRE. A native accessibility bridge for Windows has been implemented based on the IAccessible2 API.
Apparently JAWS and OpenEyes do not yet correctly support global use of the
IAccessible2 API, as I believe they have in the past implemented support as program moudules, i.e. for the old IBM Symphony implementation of IA2.
At present, the NVDA project provides more functional support for the
IAccessible2 API standard.
Stuart
--
View this message in context: http://openoffice.2283327.n4.nabble.com/the-right-Accessibility-configuration-tp4660607p4660618.html
Sent from the Development mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: R: the right Accessibility configuration
Posted by V Stuart Foote <VS...@utsa.edu>.
Deyla,
Actually Windows accessibility in Apache OpenOffice no longer makes any use
of the Java Accessibility Bridge to interface to the Java Accessibility API
installed with a JRE. A native accessibility bridge for Windows has been
implemented based on the IAccessible2 API.
Apparently JAWS and OpenEyes do not yet correctly support global use of the
IAccessible2 API, as I believe they have in the past implemented support as
program moudules, i.e. for the old IBM Symphony implementation of IA2.
At present, the NVDA project provides more functional support for the
IAccessible2 API standard.
Stuart
--
View this message in context: http://openoffice.2283327.n4.nabble.com/the-right-Accessibility-configuration-tp4660607p4660618.html
Sent from the Development mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
R: the right Accessibility configuration
Posted by Deyla Jacopo <JD...@Regione.Emilia-Romagna.it>.
Thx Rob,
#1 on a workin OO I had java listed with (or without depending on moment) accessibility support
and NVDA was working perfectyl,
but with Jaws it was working badly.
I suppose my troubles depended form my configuration, but I read a recent post that made me think the problem can ba Jaws, also the 15
Re: the right Accessibility configuration
Posted by Rob Weir <ro...@apache.org>.
On Tue, Mar 25, 2014 at 8:06 AM, Deyla Jacopo
<JD...@regione.emilia-romagna.it> wrote:
> Hi, I'd like to help test accessibility of 4.1.0
> because I'm testing OO with win xp Jaws (from 9 to 14) for an Italin Public Admistration that's "switchin" to OO.
>
> 2 issues:
> 1 -configuration
> 2 - bug not opening OO
>
> #1
> I'd like to know what's the right configuration for OO + Java in order to check it correctly and give you feedback.
> I've tested the official OO beta (see #2) with WinXP Java 1.7.0 without accessbridge and with accessbridge 2.0.2 (but I think this is no more necessary).
> In any case, it works poorely, and I'm afraid that's because of something I'm doing wrong.
>
Hello Deyla,
One quick troubleshooting technique:
In Writer, go to the dialog at Tools\Options\OpenOffice\Java (or
equivalent in Italian). Wait a few seconds for the dialog to refresh.
Does it list an installed JRE?
If no JRE is listed, you can try to add one. One important thing is
that you require a 32-bit JVM, since OpenOffice is a 32-bit
application. This is true even if you are running on a 64-bit version
of Windows.
> #2
> I've downloaded and installed both the yesterday's italian and english versions (1579169) from here
> http://ci.apache.org/projects/openoffice/#w7ia2
> but it closes in the loading screen (after 1/3) is ther a way to tell you what blocks it?
> (starting in maintenance mode or something similar)
>
I'm not sure whether that snapshot is being built from the 410 branch
(which should be stable) or the trunk (which may have issues).
Hopefully one of the developers can advise.
Regards,
-Rob
>
> thx
> Jacopo Deyla
> Regione Emilia-Romagna
> Direzione Generale Organizzazione, Sistemi Informativi e Telematica
> Servizio Sistema Informativo Informatico Regionale
>
> Viale Aldo Moro, 30 [203] - 40127 Bologna - ITALIA
> Tel. +39 051.527.3113 - Fax +39 051.527.3533/3146
> E-mail: jdeyla@regione.emilia-romagna.it<ma...@regione.emilia-romagna.it>
> ===========================================
> In your web projects try to:
> 1. Start with needs*
> 2. Do less
> 3. Design with data
> 4. Do the hard work to make it simple
> 5. Iterate. Then iterate again.
> 6. Build for inclusion
> 7. Understand context
> 8. Build digital services, not websites
> 9. Be consistent, not uniform
> 10.Make things open: it makes things better
> *user needs not government needs
> =================================================
> These are just the U.K. Government Digital Service Design Principles
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org