Alternate text but no Page Content - PowerPoint to PDF Accessibility

- Manually, with AApro8.
The quick overview from "Hints for Repair"

Alternatively, work in PowerPoint to resolve the issue. Produce your trial PDFs for checking. This may be more productive.

hth :)

Thanks for the suggestions. Maybe this is a problem with the Full Check. Actually 2 problems.

1) that there are no individual links for the problem given as "8 element(s) with alternate text but no page content." Normally the Full Check report separates out each problem as an individual link.

2) All the images and other items in my PDF file show up in the Tag tree as the shapes and figures. And all the shapes and figures in my Tag tree have been given Alternative Text. So it doesn't seem like I need to add anything to the Tag tree.

Unless I can discover how to "find the associated page content and add it to the element with the alternate text."

Order-Tags-Content...
While the goal is congruence; that is not always achieved on the first pass.
Any one of these can be non-congrent with the others.

A Tagged PDF can have content that is not tagged. Typically, this stems from how the source file has been authored. In some cases there will still be a lack of congruence; even though the authoring file has been fine tuned. Alternatively, this can occur when something is added post PDF production.

When this occurs there are, fundamentally, two options:
1. Remove the offending elements/items from the authoring file.
2. Manually, with AApro 7/8 compare Tags to Content and resolve any issues.

While #2, with the consequent addition/edit of Tags is an interesting
exercise, it does call for a preliminary work through of the courseware Adobe
has available and a look over of the help info (Chapter 10 for AApro8) and consumes a rather large block of time.

re: the link to possible "repair" issues. The links take you from the generated html file viewed in the nav pane space to the Tag in issue. Where content has no tag there is no link. btw - the html file is parked in the user's "My Documents" root by default. Look it over with an html editor.

hth

I appreciate your comments, which have helped me learn new aspects of Acrobat.

As it turns out, the problem with my files was extra hard returns after, or before, paragraphs. I took them all out and, where needed, went to the menu item Format > Line Spacing, and changed the “After Paragraph” from 0 to 1. This solved the problem.

Peter,
You've uncovered a gem.I suspect it is going to help many who port PowerPoint to PDF that are to be S508 accessible.

This is useful information, true, but it's always best to remember that it solves a problem with the Accessibility Checker, and really doesn't address accessibility itself.

It's critical to remember that the Accessibility Checker does not and cannot verify the accessibility of a PDF file. You can easily confirm this for yourself by considering that the Checker cannot verify reading order in a PDF.

This question was totally misunderstood. I am having the same problem.

There is no content that needs to be tagged! The opposite is true. Tags need to be changed or deleted NOT added.

The problem is that there is a tag somewhere in the document that has alternate text, but doesn't actually point to any content. I would love to find a way to easily locate these tags and delete them or change them and put the alt text on the appropriate tags.

From what I can see, I will have to manually look at each tag to determine whether it contains any content or not. I am using AAPro7. An "Expand All" option in the tags window would be very helpful right about now.

In reference to a Windows OS.

Open the Tag dialog (View > Navigation Panels > Tags).
With the Tags tab open, select "Tags".
To expand: (a) with the keyboard - use "Shift+*"; with the number pad - press " * " and
to collapse: (a) with the keyboard - use "/"; with the number pad - press "/".
n.b., when using the number pad have Num Lock on.

Be well...

Thanks, daka! Your tips were really helpful. Saved me a LOT of time.

My problem turned out to be putting alt text on a table tag. Guess that's not legal.