At 16:07 8-8-2011, Sigrid Carrera wrote:
I would like our documentation to be accessible to people who can't
see as good as I can. So what do I have to do to achieve this goal?
I imagine, that it is more than just checking "tagged PDF" when I
create the PDF file from the odt. So what else needs to be done?
You can check the presentation I made at the RMLL conference last month:
<http://2011.rmll.info/Accessibilite-des-documents> (in English and in French).
I you prefer text (and more details), you can check the authoring
techniques for OpenOffice Writer (v3.2) from the ADOD project at
<http://adod.idrc.ocad.ca/>. You will need to work around some bugs
of you are using LibreOffice 3.3, for example, adding alt text to
images after the caption (because adding a caption deletes the alt
text), or identifying the language of links (because links by default
have no language in OOo or Libo, unless you modify the character
style named "Internet link").
Thanks in advance for any hints you can offer.
K.U.Leuven - Dept. of Electrical Engineering - SCD
Research Group on Document Architectures
Kasteelpark Arenberg 10 bus 2442
tel: +32 16 32 85 51
Open source for accessibility: results from the AEGIS project
Please don't invite me to Facebook, Quechup or other "social
Unsubscribe instructions: E-mail to email@example.com
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
Impressum (Legal Info)
: 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