E-mail List Archives
Re: PDF accessibility
From: Karlen Communications
Date: Feb 12, 2010 10:42AM
- Next message: Bevi Chagnon | PubCom: "Re: PDF accessibility"
- Previous message: Monir ElRayes: "Re: PDF accessibility"
- Next message in Thread: Bevi Chagnon | PubCom: "Re: PDF accessibility"
- Previous message in Thread: Monir ElRayes: "Re: PDF accessibility"
- View all messages in this Thread
But the problem with this is that letting Acrobat or Reader create the
virtual Tags becomes a loophole in accessibility.
I would say that any PDF document at this point in time needs to have Tags.
It only takes a minute or less for the simple documents you are talking
about but retains consistency of workflow and addresses the standards. If
you are looking at something like Section 508 or AODA the "standard" is
clear that documents need to be accessible.
Someone/organization can be penalized if Tags don't exist in an environment
where tagging can be done and is done for other documents.
So, the "yardstick" would be to Tag documents no matter how simple or basic
they might be. This avoids confusion about what accessibility is and lets
organizations develop a consistent workflow.
My two cents CAD. Cheers, Karen
- Next message: Bevi Chagnon | PubCom: "Re: PDF accessibility"
- Previous message: Monir ElRayes: "Re: PDF accessibility"
- Next message in Thread: Bevi Chagnon | PubCom: "Re: PDF accessibility"
- Previous message in Thread: Monir ElRayes: "Re: PDF accessibility"
- View all messages in this Thread