Response in-line
-----Original Message-----
From: Christophe Strobbe [mailto:christophe.strobbe@esat.kuleuven.be]
Sent: Monday, October 03, 2011 06:33
To: accessibility@global.libreoffice.org
Subject: Re: [libreoffice-accessibility] [DISCUSS] What do translation and accessibility have in
common?
At 20:38 2-10-2011, Dennis E. Hamilton wrote:
I just saw this web page:
<http://www.translationautomation.com/interoperability-is-important-for-the-translation-profession.html>
It struck me that there is an overlap between translation and
accessibility. I am not clear how to describe it. I think it is
there. Does anything about the translation debate say something to
you with respect to accessibility arrangements and having them be
interoperable?
I think you will need to expand on this, because I don't see what the
overlap would be.
<orcmid>
I thought some of the commercial issues raised in that topic
might have some counterparts in accessibility and certainly
features on systems for integrating with the accessibility of
individual programs, say.
But I asked because it occurred to me that there might be some
relationship, not that I had one in mind. I don't work in
accessibility myself. I recognize its importance and wondered
about any relationship with translation tooling, if any.
</orcmid>
The basic accessibility requirements for an application are support
of the platform's accessibility API, keyboard access and themeing
support (for both high contrast modes and large fonts). Screen reader
users may find it more important than other users to have all their
software in the same language because I have not seen accessiblity
APIs that tell you the language of an application's UI. (E.g. I have
a Dutch version of Window-Eyes, which only pronounces its own UI (!)
in Dutch if you set a synthesiser for Dutch in the program.) With the
exception of this instance, I don't see any overlap (if that is the
correct word) between accessibility and translation, let alone
between accessibility and interoperability between computer-aided
translation tools.
<orcmid>
I think translation of accessibility information would be relevant.
I think having multi-lingual information be accessible might
also be important.
I even thought there might be an overlap between having translation
as a feature also be accessible.
</orcmid>
Best regards,
Christophe
--
Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/
Twitter: @RabelaisA11y
---
Open source for accessibility: results from the AEGIS project
www.aegis-project.eu
---
Please don't invite me to Facebook, Quechup or other "social
networks". You may have agreed to their "privacy policy", but I haven't.
--
Unsubscribe instructions: E-mail to accessibility+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted
--
Unsubscribe instructions: E-mail to accessibility+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.