Answered
I am making existing PDF documents 508 compliant. I had the document working fine. I then Inserted a few new pages (needed to convert Layered maps to JPG), and removed the old ones. All Accessibility setting are still intact, but now when I turn on the ROL, it reads back the Figures as "Warning Empty Page". All content Tagged as Text is working fine. Alt Text is present, Language is set, PDF is Tagged. I have been comparing the Tags/Order?Content and all Properties to my working documents, and I can't find any difference. Would appreciate any help.
Acrobat Pro 9.3.0
John Lundquist
508 Consultant
Lundquist Consulting Service inc
jlundquist [at] cox [dot] net
I suspect that when you inserted and removed pages the process left you with a malformed structure tree.
Removing PDF pages that have page content associated with the logical structure, marked content, and Tagged PDF does not remove the all these.
Logical structure and Tagged PDF reside independently from page content.
Inserting pages can spice things up.
If the pages have their own structure tree, this goes to the end of the existing structure tree.
If the pages are untagged PDF, then the tagging process may cause problems.
Regardless, "empty page" points to some specifics. One of which is the consequence of the insert/remove & associated work.
Again, from what you've described, I suspect the structure tree has become malformed.
In a PDF with short, simple page content, slick'n the tree and a new build, via the Tags panel can be done.
When past "short-simple", the PDF's Document Interchange facilities (accessibility is a sub-set of this) are typically skewed beyond practicle repair.
In such situations it becomes time to start over.
EMPTY PAGE
Source: Reading PDF Files Through MSAA
Empty Documents
The way a PDF was created can make it inaccessible.
For instance, scanned images that have not been OCR’d appear to be empty.
Malformed structure trees can also make a document appear empty.
When a document appears to be empty, we return an accessible object warning of a possible error.
If Acrobat is delivering information a page at a time, a genuinely empty page also generates this warning.
Source: ISO 32000-1
--| Content streams describe the contents of a PDF page. If a PDF page's "Contents" key is absent (not provided during PDF creation or adversely affected by edits of the PDF such that it becomes (effectively) absent) then the page "shall be empty".
Source: PDF Accessibility API Reference (part of the Acrobat SDK).
Provides discussion on "empty" (inaccessible, protected, empty, unavailable documents (PDF)).
Be well...
Be well...