Consider the following example:
As things stand, when converted with the --tagged-pdf option, this results in the following tag structure:
As far as I can tell, the spec doesn't explicitly prohibit an LI tag having multiple Lbl children, but some screen readers may expect there to be exactly one – it'd be handy if there were a mechanism to merge multiple adjacent Lbl tags within the same parent LI.
<ol>
<li><span style="prince-pdf-tag-type: Lbl">Name of step one:</span> body of step one.</li>
<li><span style="prince-pdf-tag-type: Lbl">Name of step two:</span> body of step two.</li>
<li><span style="prince-pdf-tag-type: Lbl">Name of step three:</span> body of step three.</li>
</ol>
As things stand, when converted with the --tagged-pdf option, this results in the following tag structure:
L
+---LI
| +---Lbl: "1."
| +---Lbl: "Name of step one:"
| +---LBody: "body of step one."
+---LI
| +---Lbl: "2."
| +---Lbl: "Name of step two:"
| +---LBody: "body of step two."
+---LI
+---Lbl: "3."
+---Lbl: "Name of step three:"
+---LBody: "body of step three."
As far as I can tell, the spec doesn't explicitly prohibit an LI tag having multiple Lbl children, but some screen readers may expect there to be exactly one – it'd be handy if there were a mechanism to merge multiple adjacent Lbl tags within the same parent LI.
Edited by David J Prokopetz
