Would the new accessibility api be appropriate for tagging an /XObject (ie
image) so that it can later be retrieved by test automation? Or is there
something else?
I built 5.4.0 from svn, and added accessibleAttribute to image:
image.setAccessibleAttribute(PdfName.ALT, new PdfString("image1"));
Would the new accessibility api be appropriate for tagging an /XObject (ie
image) so that it can later be retrieved by test automation? Or is there
something else?
I built 5.4.0 from svn, and added accessibleAttribute to image:
image.setAccessibleAttribute(PdfName.ALT, new PdfString("image1"));
ld just put a custom key of your own choosing on each Xobject that
> you wish to "mark". This would be a second class key (as described in ISO
> 32000-1:2008) and you'll need to register your second class extension with
> ISO. But that's just formality…
>
> Le
such as blind users). Putting your value in there will screw
> them up :(
>
> Leonard
>
> From: Jason Kissinger
> Reply-To: Post here
> Date: Wednesday, February 13, 2013 12:54 PM
> To: Post here
> Subject: Re: [iText-questions] Tagging content
>
> Righto, I'
To answer my own question (assume I'm on right track)...
Image doesn't represent an /XObject, but PDFTemplate does. Doing:
pdfTemplate.getAdditional().put(new PdfName("myId"), new
PdfString("image1"));
adds '/myId' to xobject's dictionary and I can now find the image stream by
myId.
Is that t
y_v3.pdf>,
> fill out the form and submit it. Then you'll have your legal prefix.
>
> Leonard
>
> From: Jason Kissinger
> Reply-To: Post here
> Date: Wednesday, February 13, 2013 2:56 PM
>
> To: Post here
> Subject: Re: [iText-questions] Tagging content
>
