Issue 102960 - Support for document Tab order when exporting to PDF
Summary: Support for document Tab order when exporting to PDF
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: formatting (show other issues)
Version: OOO310m11
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL: http://user.services.openoffice.org/e...
Keywords: needmoreinfo, oooqa
: 116665 (view as issue list)
Depends on:
Blocks:
 
Reported: 2009-06-19 19:09 UTC by fauxwriter
Modified: 2013-08-07 14:38 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Sample writer document with hyperlinks (16.36 KB, text/plain)
2009-06-19 19:16 UTC, fauxwriter
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description fauxwriter 2009-06-19 19:09:56 UTC
This is an accessibility compliancy issue.  When I perform an Adobe Acrobat 
Professional full accessibility scan on a PDF exported from OpenOffice, it 
fails for 'Tab order may be inconsistent with the structure order'.

I am creating regular documents (NOT FORMS), that contain hyperlinks to both 
external URLs and also internal document or chapter links.  I then export to 
PDF and make the following selections:

General tab/General: Tagged PDF, Export Bookmarks
Links tab: Export bookmarks, convert document, export urls

I open the PDF using Adobe Acrobat PRO and run the full scan.  I can see the 
error message for each page that contains a hyperlink.  I AM able to fix the 
problem as recommended by Adobe, by selecting all pages, go to options, then 
page properties and on the TAB ORDER tab, select 'Use Document Structure'.

I could not find a way in writer to set the TAB ORDER for a regular document.  
I could see how to do it from the Form Design tool bar, but that doesn't help 
me in a regular document. 

I have a sample document if you want to look at it.  

Thank you.
Comment 1 fauxwriter 2009-06-19 19:16:11 UTC
Created attachment 63099 [details]
Sample writer document with hyperlinks
Comment 2 eric.savary 2009-06-20 11:51:36 UTC
@fauxwriter: please clarify some points. I'm not used with Adobe Accessibility
Checks.

- Going with a "naive mind" ;) in the produced PDF shows a correct tab order:
all links get jumped on in the correct order using the Tab key.

Can you find a concrete accessibility problem in the document while using it or
do you only stuck on an error saying "Tab order *may be* inconsistent with the
structure order"? ;)

- You say: "I open the PDF using Adobe Acrobat PRO and run the full scan".
I don't have tested with the Pro version and therefore might have missed the
"full scan".
Just using "Adobe Reader 9.0" and doing "Tools - Accessibility Quick Check"
finds no error.

Do I need absolutely Adobe Acrobat PRO to reproduce this or can I make such a
scan in Adobe Reader 9.0?
Comment 3 fauxwriter 2009-06-22 14:46:45 UTC
Hello and thank you for looking at my issue.  Unfortunately the Adobe 
Reader 'Quick check' does not pick up the problem with tab order.  The company 
I work for requires all documentation, to pass accessibility checking and they 
use Adobe Acrobat Pro/Full Scan as the tool to determine compliance for PDF 
files.  You must use Acrobat Pro to get the full scan capabilities.

It seems as if there should be some way to set the tab order, either as the 
default or at a document level - even if it's just at the time the PDF is 
created.

Thank you.
Comment 4 eric.savary 2009-06-23 16:58:26 UTC
Well I check with Adobe Acrobat 8 (I don't have something else).

Actually I don't really understand what this Error means as long as the document
can be traveled consistently with tab...

Looking at the workaround "Use Document Structure" in the Tab Order option is a
feature we might support one day.
One day because we are now supporting PDF 1.4 and this is a 1.5 feature.



Reassigned to Requirements
Comment 5 michael.ruess 2011-01-28 08:11:37 UTC
*** Issue 116665 has been marked as a duplicate of this issue. ***