E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 5 (In chronological order)

From: Joseph Sherman
Date: Fri, Aug 17 2018 11:05AM
Subject: PDF Validator Failures?
No previous message | Next message →

Whenever I check PDFs using Commonlook, I always get the following errors about link annotation.

"Parent tag of Link annotation doesn't define the Alt attribute." "Link Annotation doesn't define the Contents attribute."

I can fix this fairly easily. But as long as the link is descriptive text, what practical consequence does this have? The descriptive link seems to read in JAWS and NVDA just fine without ALT on the annotation.


Joseph

From: Karlen Communications
Date: Fri, Aug 17 2018 12:04PM
Subject: Re: PDF Validator Failures?
← Previous message | Next message →

I know, I have the same errors with Tables of Content as well as with
contextual links. I don't have a good solution. I can choose to ignore them
with my own documents but am curious to know how organizations deal with
this.

Not sure if it is a defect in what we've done with PDF/UA, the
implementation of PDF/UA by conversion tools, a problem with the
accessibility checkers or some other problem.

I also sometimes get the error that in a TOC, the <Link> Tag is looking for
unique ID's for each TOC entry. Yikes! Why didn't the conversion
tool/tagging tool do this?

Cheers, Karen

From: Jonathan Avila
Date: Fri, Aug 17 2018 1:17PM
Subject: Re: PDF Validator Failures?
← Previous message | Next message →

It is my understanding that from a PDF/UA perspective that all links must have the alternative content set. Ideally authoring tools would just set this on all links. For most text links that are not url this is redundant if the text of the link already describes the link's purpose.

Jonathan

Jonathan Avila, CPWA
Chief Accessibility Officer
Level Access
= EMAIL ADDRESS REMOVED =
703.637.8957 office

Visit us online:
Website | Twitter | Facebook | LinkedIn | Blog

Looking to boost your accessibility knowledge? Check out our free webinars!

The information contained in this transmission may be attorney privileged and/or confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is strictly prohibited.

From: L Snider
Date: Fri, Aug 17 2018 1:31PM
Subject: Re: PDF Validator Failures?
← Previous message | Next message →

Interesting that you mention the TOC issues. I find that is happening in my
Mac Word 2016 (insiders fast) using lastest Acrobat DC way more now than
before. It is driving me mad, because I thought that the convertor would
handle it automatically. I also tested it on PC, and it also did this, when
there was no reason for it, as I was using the proper TOC.

Would love to know more about how the alt for the link tags came about, in
terms of why it was mandated? From what I remember researching about a year
ago, I think there was some consensus that it was done because people
weren't using descriptive link text (which in my experience can be
difficult to achieve especially if the document is digital and to be
printed).

Cheers

Lisa

On Fri, Aug 17, 2018 at 1:04 PM, Karlen Communications <
= EMAIL ADDRESS REMOVED = > wrote:

> I know, I have the same errors with Tables of Content as well as with
> contextual links. I don't have a good solution. I can choose to ignore them
> with my own documents but am curious to know how organizations deal with
> this.
>
> Not sure if it is a defect in what we've done with PDF/UA, the
> implementation of PDF/UA by conversion tools, a problem with the
> accessibility checkers or some other problem.
>
> I also sometimes get the error that in a TOC, the <Link> Tag is looking for
> unique ID's for each TOC entry. Yikes! Why didn't the conversion
> tool/tagging tool do this?
>
> Cheers, Karen
>
>

From: chagnon
Date: Fri, Aug 17 2018 10:20PM
Subject: Re: PDF Validator Failures?
← Previous message | No next message

PDF/UA-1 Sec. 7.18.5 states:
"Links shall contain an alternate description via their contents key as
described in ISO 32000-1:2008."

I think this spec is ill-defined as we're all finding that a global "all
links must have alt-text" just doesn't meet users' needs well. I hope it can
be fine-tuned in PDF/UA-2.

We use our judgment when checking links for alt-text. As long as the link
itself provides enough descriptive information, Alt-text really isn't needed
and in most cases adds unnecessary verbiage to the stream that's hitting a
screen reader user's ears.

-Bevi
- - -
Bevi Chagnon, founder/CEO | = EMAIL ADDRESS REMOVED =
- - -
PubCom: Technologists for Accessible Design + Publishing
consulting . training . development . design . sec. 508 services
Upcoming classes at www.PubCom.com/classes
- - -
Latest blog-newsletter - Accessibility Tips at www.PubCom.com/blog