How do I eliminate basic boxes and lines and other graphics from showing up as "inaccessible page content" during accessibility Full Check? I'm using Acrobat Pro 8. These graphics will not be read by screen readers and they are essentially artifacts. I've tried making them into artifacts in the pdf file but they still show up in Full Check. It's a Powerpoint file with boxes and shadows and other assorted graphics. Can anyone help with this? Thanks.
Artifacts and Decorative Page Elements Show Up in "Full Check"
2008-01-17 07:56:43
My Product Information:
Acrobat Pro 8.1.1, Windows
Acrobat Pro 8.1.1, Windows
2008-01-18 05:15:32
#2
Wow. So there's really nothing I can do in Powerpoint except delete the shadows (and I guess the boxes they are a part of), lines, arrows, etc? Also, I've tried grouping and the same thing happens. It seems the only way around it is to copy and paste special as a .jpg or .gif. If the graphic is vector the alt text does't appear in the pdf. Am I totally missing something?
2008-01-18 13:46:36
#3
Some observations-
- why not try a box without drop shadows?
- grouping... even if you have to post process the PDF, one grouped item to tag is less effort than many, non-grouped, no?
As I do not routinely use Powerpoint I cannot speak to the details associated with a "custom build"; however, when I play with it to see "what if" I have observed that the out-of-the-box "themes" (?) and their associated graphics regularly become artifacts in the tagged PDF output. So, perhaps, if you could build your "theme" and save it...?
Can you drop in a text box (like in MS Word)?
Select the text box, right click, select Format Text Box, Select Web tab,
enter Alternative Text...
My thought is that the graphic placed in the box would be wrapped by the box boundary. The boundary would have the AltText. Send to PDF and check.
It occurs to me that I ought to visit Powerpoint and play...
- why not try a box without drop shadows?
- grouping... even if you have to post process the PDF, one grouped item to tag is less effort than many, non-grouped, no?
As I do not routinely use Powerpoint I cannot speak to the details associated with a "custom build"; however, when I play with it to see "what if" I have observed that the out-of-the-box "themes" (?) and their associated graphics regularly become artifacts in the tagged PDF output. So, perhaps, if you could build your "theme" and save it...?
Can you drop in a text box (like in MS Word)?
Select the text box, right click, select Format Text Box, Select Web tab,
enter Alternative Text...
My thought is that the graphic placed in the box would be wrapped by the box boundary. The boundary would have the AltText. Send to PDF and check.
It occurs to me that I ought to visit Powerpoint and play...
2008-01-18 17:19:59
#4
Millermania,
Some observations from playing with Powerpoint
(...None of the contents or annotations in this document are contained in the structure tree.)
Powerpoint "Notes" - if brought over to a tagged PDF as an annotation...
The annotation are not part of the PDF's structure tree and will have to added manually.
These would have to be manually processed using Acrobat Professional to incorporate
the annotation into the structure tree.
("...word(s) that contain characters with no reliable mapping to Unicode.)
Various symbols (i.e., bullets, etc.). Not uncommon. The character set value(s)
pull from values that are reserved. While working within the given software (which is coded to
render a desired symbol) these don't map to unicode. Thus, not reliable vis-a-vis accessiblity.
In MS Office applications this is seen when a WingDing character (i.e., a "diamond" bullet)
is used to denote a list item. While the character, in the PDF, can be isolated and changed to
an artifact consequent use of Full Check identifies that these characters won't map
to Unicode. After all, they are still present in context of evaluating character encoding.
Using the Drawing Toolbar > AutoShapes...
I used this to place two arrows.
Then - selected each - right click - selected Format AutoShape - selected Web tab
- entered Alternate Text
In the tagged PDF: "2 element(s) with alternate text but no page content."
On reflection, this makes sense. Unlike an inserted image file of a common type
such as JPG, the AutoShape appears to not be recognized by the conversion code.
An inserted JPG, with Alternate Text entered (select > format picture > Web tab > Alternate Text)
is given the Figure Tag when processed to tagged PDF.
The pre-assigned AltTxt is carried through.
This does not happen with the MS AutoShape, even with AltTxt added (as described above).
Pragmatically, in context of Section 508 accessibilty, any AutoShape would, typically not
contribute to functional understanding of the essential content.
Thus, AutoShapes could be tagged as an artifact.
However, the AltText is still present. Full Check identifies this and we still have
"...alternate text but no page content."
It would seem that AutoShapes ought not be given Alternate Text in Powerpoint.
With the tagged PDF produced, the AutoShape(s) would have to be manually isolated and
tagged as artifacts to obtain a "pass" from Full Check.
Not having the source Powerpoint file makes developing a Section 508 accessible tagged PDF of the
outputed PDF problematic. While manual post-processing with Acrobat Professional will
permit some repairs, some of the remediation must be done in Powerpoint.
An alternative success path is to re-master the essential content (in Powerpoint or another application).
Convert it to a tagged PDF. This lets you work in the authoring application to resolve most, if not all,
accessiblity issues. What remains would be repaired with Acrobat Professional (n.b., Standard lacks the
requisite tools for this).
re: vector graphic/alttxt ... might it be that, like the AutoShape, these appear to not be recognized by conversion code as a "Figure"?
Some observations from playing with Powerpoint
(...None of the contents or annotations in this document are contained in the structure tree.)
Powerpoint "Notes" - if brought over to a tagged PDF as an annotation...
The annotation are not part of the PDF's structure tree and will have to added manually.
These would have to be manually processed using Acrobat Professional to incorporate
the annotation into the structure tree.
("...word(s) that contain characters with no reliable mapping to Unicode.)
Various symbols (i.e., bullets, etc.). Not uncommon. The character set value(s)
pull from values that are reserved. While working within the given software (which is coded to
render a desired symbol) these don't map to unicode. Thus, not reliable vis-a-vis accessiblity.
In MS Office applications this is seen when a WingDing character (i.e., a "diamond" bullet)
is used to denote a list item. While the character, in the PDF, can be isolated and changed to
an artifact consequent use of Full Check identifies that these characters won't map
to Unicode. After all, they are still present in context of evaluating character encoding.
Using the Drawing Toolbar > AutoShapes...
I used this to place two arrows.
Then - selected each - right click - selected Format AutoShape - selected Web tab
- entered Alternate Text
In the tagged PDF: "2 element(s) with alternate text but no page content."
On reflection, this makes sense. Unlike an inserted image file of a common type
such as JPG, the AutoShape appears to not be recognized by the conversion code.
An inserted JPG, with Alternate Text entered (select > format picture > Web tab > Alternate Text)
is given the Figure Tag when processed to tagged PDF.
The pre-assigned AltTxt is carried through.
This does not happen with the MS AutoShape, even with AltTxt added (as described above).
Pragmatically, in context of Section 508 accessibilty, any AutoShape would, typically not
contribute to functional understanding of the essential content.
Thus, AutoShapes could be tagged as an artifact.
However, the AltText is still present. Full Check identifies this and we still have
"...alternate text but no page content."
It would seem that AutoShapes ought not be given Alternate Text in Powerpoint.
With the tagged PDF produced, the AutoShape(s) would have to be manually isolated and
tagged as artifacts to obtain a "pass" from Full Check.
Not having the source Powerpoint file makes developing a Section 508 accessible tagged PDF of the
outputed PDF problematic. While manual post-processing with Acrobat Professional will
permit some repairs, some of the remediation must be done in Powerpoint.
An alternative success path is to re-master the essential content (in Powerpoint or another application).
Convert it to a tagged PDF. This lets you work in the authoring application to resolve most, if not all,
accessiblity issues. What remains would be repaired with Acrobat Professional (n.b., Standard lacks the
requisite tools for this).
re: vector graphic/alttxt ... might it be that, like the AutoShape, these appear to not be recognized by conversion code as a "Figure"?
2008-01-19 19:25:50
#5
Thanks for your input daka630. This is definitely a strange set of problems. The vector graphics sometimes show up as paths in the tags folder. I'll have to try dropping in a grouped graphic with a text box. Maybe that'll work and produce a single graphic in the tags tree. I also have tried artifacting decorative elements in Acrobat (I don't think is anyway to do this in Powerpoint) but they still show up in Full Check as figures without alternate text--yet they're only artifacts. It seems that Acrobat just isin't doing what it's supposed to do. I make them into artifacts but they're still figures? One way around this, I've discovered is instead of using alt text in Powerpoint just type in a keystroke of the spacebar in its place. Blank alternate text but reads as valid alt text without the screen reader saying a thing. This may not be the best way to go but maybe it is.
2008-03-25 14:04:58
#6
It is COMPLETELY wrong to "...just type in a keystroke of the spacebar in its place. "
This is the tail wagging the dog, ie, using a "pass" from the Accessibility Checker as an indicator of accessibility.
The truth is that the Checker is woefully flawed, and it does not, in fact, check or validate accessibility at all, it merely offers some (occasionally) helpful indicators.
To test your file without a screen-reader, simply Save As the file to Accessible Text. If all the content and proper alt. text is present in correct order, you are all set.
"Tricking" the accessibility checker by adding "dummy" alt. text to images causes the screen-reader user to hear prompts indicating the presence of an "image", but they won't get alt. text for those images. Result: they will assume that your file is NOT accessible and NOT compliant with Section 508. Not exactly the intended effect!
The correct approach is simply to ensure that any content that is undeserving of voicing by a screen-reader or other assistive technology (such as drop-shadows) is tagged as an Artifact, regardless of what the Checker has to say on the matter.
This is the tail wagging the dog, ie, using a "pass" from the Accessibility Checker as an indicator of accessibility.
The truth is that the Checker is woefully flawed, and it does not, in fact, check or validate accessibility at all, it merely offers some (occasionally) helpful indicators.
To test your file without a screen-reader, simply Save As the file to Accessible Text. If all the content and proper alt. text is present in correct order, you are all set.
"Tricking" the accessibility checker by adding "dummy" alt. text to images causes the screen-reader user to hear prompts indicating the presence of an "image", but they won't get alt. text for those images. Result: they will assume that your file is NOT accessible and NOT compliant with Section 508. Not exactly the intended effect!
The correct approach is simply to ensure that any content that is undeserving of voicing by a screen-reader or other assistive technology (such as drop-shadows) is tagged as an Artifact, regardless of what the Checker has to say on the matter.
An alternative. Try using the TouchUp Reading Order tool - set page to background. Re-tag need content.
Be well...