PDFUA-9: TOC, simple

[zakkinsey]

Jira issue originally created by user @:

Sample of a simple table of contens, using , as suggested in Best Practice Guide.

[zakkinsey]

Comment created by @:

Native output with indesign will cause a non valid file.

Output with the accessibility plugin axaio MadeToTag will result in a valid PDF/UA-file, but not the PDF example.

PDF is hand edited with Acrobat.

[zakkinsey]

Comment created by @:

{color:#000000}Evaluation with Acrobat and JAWS {color}

{color:#000000} {color}

{color:#000000}Adobe Acrobat DC (19.010.10059){color}

{color:#000000}JAWS Version 2018.1811.2 ILM{color}

{color:#000000}Windows 10{color}

{color:#000000} {color}

{color:#000000}When needed to exemplify what JAWS is speaking, I’m using the same notation used in our guides for tagged psudo code. For instance,

{foobar} means that the text "foobar" is a heading level 1.{color}

 

{color:#000000}Below is JAWS reading:{color}

{color:#000000} {color}

\{Table of contents} list of 3 items \{1.} Heading first chapter \{��������������������������������������������} \{page 2} \{Another heading} \{�������������������������������������������������������} \{page 3} \{Last heading } \{��������������������������������������������������������������} \{page 4} list end

\{1. Heading first chapter} Some portion of text.

\{Another heading} Some portion of text.

\{Last heading} Some portion of text.   There are several usability problems with this: * for each entry in the TOC, there are 4 separate links. It should be only 1 link per entry in the TOC. * the chars used to separate the item text from the page # (dots?) is silent, so the user only hears "link". * JAWS virtual cursor navigation is erratic, getting stuck in some fragment of the doc. this is most likely a JAWS/Acrobat bug related to page transition. More investigation required.

[zakkinsey]

Comment created by @:

In m setup (using JAWS2019), the TOC items are read twice. This is not just with this example. It is an issue I started to notice since a few months. So it must have been in JAWS2018 already