zakkinsey / pdfa-test-7

0 stars 0 forks source link

PDFUA-10: A paragraph split up into two paragraphs #10

Open zakkinsey opened 5 years ago

zakkinsey commented 5 years ago

Jira issue originally created by user Klaas Posselt klaas.posselt@einmanncombo.de:

the content of one heading should be presented with one block level element

zakkinsey commented 5 years ago

Comment created by Andres Gonzalez <andgonza@adobe.com>:

Evaluation with Acrobat and JAWS

 

Adobe Acrobat DC (19.010.10059)

JAWS Version 2018.1811.2 ILM

Windows 10

 

When needed to exemplify what JAWS is speaking, I’m using the same notation used in our guides for tagging psudo code. For instance, <H1> {foobar} means that the text foobar is a heading level 1.

 

JAWS reads:

 

<H1> {One heading split up} <H1> {into two paragraphs}

 

The problem with this is the repetition of "heading level 1" twice by JAWS. This may be an Acrobat/JAWS problem.

zakkinsey commented 5 years ago

Comment created by Iacobien Riezebosch <iacobien@firmground.nl>:

I don't see 2 paragrafs in the tags. I see two h1's just containing text. Neither h1 contains a paragraph.

It is not true that one heading is split up into two paragraphs.

zakkinsey commented 5 years ago

Comment created by @DuffJohnson:

Agreed with Klaas... however the example is unfortunate because the text in the PDF refers to "paragraphs" instead of "headings".

Could we get a new example with on-page text such as "A single heading split into two heading tags" or similar?

zakkinsey commented 3 years ago

Comment created by @MarkusErle:

Optimized the example for paragraph tags.

zakkinsey commented 3 years ago

@MarkusErle assigned issue to @pkopicar

zakkinsey commented 3 years ago

Comment created by @MarkusErle:

Please clean up

zakkinsey commented 3 years ago

Comment created by @pkopicar:

Cleaned up. Accepted.

zakkinsey commented 1 year ago

Comment created by @calanca2:

This example should belong to Fundamental 5 - Appropriate Semantics.

zakkinsey commented 1 week ago

@zakkinsey unassigned issue from @pkopicar as part of jira->github migration