Hi :)
Yes, the more bug-reports the better. Especially very specific ones that
might
be fairly easy to fix. There is a fork called NeoOffice that is targeted at
Macs and doesn't use the X system.
Regards from
Tom :)
________________________________
From: titengodocchio.it <info@titengodocchio.it>
To: accessibility@global.libreoffice.org
Sent: Tue, 26 July, 2011 14:37:28
Subject: Re: [libreoffice-accessibility] Should Writer export taggedPDF and
bookmarks by default?
Hi guys,
I'm reading this tread with great interest.
I am not an expert-user of Libreoffice (the mac os X' version is still very
inaccessible!), but I wonder if libreoffice is able to perform a "serious"
accessibility check on PDF documents, not limited, of course, to the tags...
If it isn't, it should be great if this feature could be implemented in this
suite...
Libreoffice needs really more work on accessibility (I tested the MAC OS X'
version)...
By the way, about two months ago we were talking about the "accessibility
issues" in the mac OS X' version of LO. I would like to help to fix them..Do
you
think i should report them as bugs?
Vincenzo.
----- Original Message ----- From: "Christophe Strobbe"
<christophe.strobbe@esat.kuleuven.be>
To: <accessibility@global.libreoffice.org>
Sent: Tuesday, July 26, 2011 3:24 PM
Subject: Re: [libreoffice-accessibility] Should Writer export taggedPDF and
bookmarks by default?
Hi Tom,
At 14:44 26-7-2011, Tom Davies wrote:
Hi :) Can you post a bug-report about it?
http://wiki.documentfoundation.org/BugReport
Sure.
Perhaps add "[wishlist]" to the subject-line?
OK, I did not know that tag existed.
I think post the bug-report now rather than leaving it. Any small
improvement
in accessibility should be a priority in my opinion. Sometimes the
defaults are
not really thought about and are easy to change which helps new devs learn
how
to do coding :) A good win for everyone.
Is there a down-side to having Pdfs tagged by default? What does the
tagged
option do?
"Tagged PDF contains information about the structure of the document
contents.
This can help to display the document on devices with different screens,
and
when using screen reader software. "
(<http://help.libreoffice.org/Common/Export_as_PDF#Tagged_PDF>)
Exporting an inaccessible document as "tagged PDF" may give people the
impression that a document is accessible when they do only a superficial
check
(e.g. Adobe Reader's so-called accessibility check only checks whether the
PDF
is tagged or not).
I would also want to avoid that authors get the false idea that checking
"tagged PDF" is all they need to do to produced accessible PDF. (Although I
doubt that changing the default setting will make a difference to this type
of
authors.)
Best regards,
Christophe
Regards from Tom :)
________________________________
From: Christophe Strobbe <christophe.strobbe@esat.kuleuven.be>
To: accessibility@global.libreoffice.org
Sent: Tue, 26 July, 2011 12:28:35
Subject: [libreoffice-accessibility] Should Writer export tagged PDF and
bookmarks by default?
Hi, I have been thinking about ways to improve accessible authoring in
LibreOffice Writer. As far as I know, Writer (in OpenOffice.org and in
LibreOffice) is the only open source office software that can export
tagged PDF,
which is important for accessibility. When you open the PDF Options dialog
(File
-> Export as PDF...), the options "Tagged PDF" and "Export bookmarks" on
the
General tab and the option "Bookmarks and page" on the Initial View tab
are
unchecked by default. When you check them, they remain checked for later
export
commands. However, wouldn't it be better if these options were checked by
default? Checking these options does not magically make your PDF documents
accessible, because that depends on the quality of the ODF source. So
should we
request this feature now or should we wait until an accessibility checker
for
Writer becomes available? 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
--
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
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.