First, section 508 and document accessibility in general is a VERY
complex topic. A good starting place might be Duff Johnson's blog -
for example this entry <http://www.acrobatusers.com/blogs/duffjohnson/
2006/12/20/blind-spots-pdf-and-section-508-compliance/>.
Second, if you wish to create a tagged/structured PDF, some (but not
all) of the pieces are already present in iText and you can start
using them today.
Finally, if you are using JasperReports as the "layout engine", you
will have to also make requests of its author to make the necessary
code changes to enable tagged PDF - or do it yourself.
Leonard
On Mar 16, 2007, at 8:59 AM, Adam Schaible wrote:
Hello,
I’m a Java developer that primarily uses iText with
JasperReports. We’ve chosen this route and it’s worked well for
us, however as you may or may not know, section 508 (which dictates
accessibility standards in the United States) will soon be
bolstered to implement specific requirements, and most seem to
believe the equivalence of an <alt> tag will be required in all
reports – currently supported in PDF spec 1.6. Is there any plan
to upgrade iText to adhere to this standard? If so, do you have
any anticipated time frame? I’m familiar with the iText and
JapserReports api, and have written a project that wraps the two
into a reporting system – however I’ll need to rethink an approach
if I cannot generate more accessible PDF documents in the future.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
iText-questions mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/itext-questions
Buy the iText book: http://itext.ugent.be/itext-in-action/
