zakkinsey / pdfa-test-7

0 stars 0 forks source link

PDFUA-146: Link over Artifact #146

Open zakkinsey opened 5 years ago

zakkinsey commented 5 years ago

Jira issue originally created by user @pkopicar:

The text marked as artifact contains the link annotation.

zakkinsey commented 5 years ago

@pkopicar assigned issue to self

zakkinsey commented 5 years ago

@pkopicar added a link to #11: This issue is duplicated by #11

zakkinsey commented 5 years ago

Comment created by @mrbhardy:

Interesting example. I think this one needs some discussion. The content is artifacted, but the link is tagged, which effectively means we have a floating link with little to no context... I'd like to hear from more tagging experts on this (I'm not saying it is wrong, just a little surprising).

zakkinsey commented 5 years ago

Comment created by @DuffJohnson:

[~AndresGonzalez] Please review this file in the context of the Adobe Accessibility API. Bart's test with JAWS during the LWG meeting today did not reveal the link even though it appears in the structure tree...

zakkinsey commented 5 years ago

Comment created by @pkopicar:

From my testing with NVDA and JAWS in Acrobat I figured:

Link without Alternate Text (Alt)

NVDA output: "Link"

JAWS output: ""

Link with Alternate Text (Alt)

NVDA output: "Link" whatever the alt is

JAWS output: "Link" whatever the alt is

The Contents key does not have any impact here.

JAWS does not reveal the link because it has no Alternate or page content associated with it.

zakkinsey commented 1 week ago

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