reflow, tagging text, combining to create 1 page

Questions on 2 downloadable pdfs ...
.
.
• CVbook_noAccessOption.6.9.pdf Page 8. Is it possible to remove right top column superscript 1, 2, 3, 4?
.
I notice that between PDF page 24 (26 of 100) and 97(99 of 100) that page content is not tagged.
If you are having to do a manual "build the structure tree" or rely on Acrobat to add "accessibility" the passage will be...
well interesting.
.



--| PDF page 8 (10 of 100): "1" and "2" are present. I see no "3" or "4". The "1" and "2" are intended to be footnotes.
There is a footnote for both "1" and "2". However, the manner in which the footnote was mastered back in InDesign failed to bring the footnotes over into PDF with the [Note] tag (which is specifically for footnotes or endnotes). As well, within the [Note] element one might want there to be an accessible link from the footnote "marker" (the superscript in this document) to the footnote content.
.
Yes, you can remove the superscript "1" and "2". Use the TouchUp Text tool to select the character. Open the context menu & select Properties. Ensure that the character's font is one that is on the local machine and has been made available to the OS.
You may have to use something other than Avenir-Book if that is not actual available on your local machine and available to the OS. Having assured that the character is now provided with a system font you can close the dialog and delete the "1" or the "2".
But, what then to do with the actual PDF page content that is the symantic content of the "1" and the "2"?
.
Just an observation — heavy edits of a PDF's content, structure tree, etc. rather than correcting issues that can and should be corrected back in the authoring file typically won't result in getting to the thresehold of "2.5 and survive" let alone something better.
Sounds harsh but it is really very pragmatic.
It is ever so much easier to do everything possible upfront (measure twice, cut once approach).
(There's a learning curve (like mine, which is still in process, for video tutorials - ask UVSAR ) - but, once the rite of passage is completed the deliverables will reflect it.)
.
.
• CVbook_noAccessOption.6.9.pdf On pg 21, reflow comes up squished. Why?
.
--| I strongly suspect this is due to the table being malformed in the structure tree. Aside from the unnecessary designation of the first column's cells as [TH] which unnecessarily complicates the table the [Table] element has two [THead] elements. [Table] has only one [Thead], can have more than one [TBody] and has only one [TFoot] (when used). As-is each cell calls for the assignment of "ID" (some unique string to each cell) and appropriate application of the Header attribute. While easier with Acrobat Pro 9 or X Table Editor this activity does require thoughtfull pre-planning if it is to function properly. It is a labor & time intensive activity, particularly so if there are many [TH] and [TD] cells as each cell must be addressed.
.
A cleaner, simpler, and ultimately a more accessible approach would be to re-master the table.
Make "Preventive care guidelines for children and teens" an appropriate level "Heading" in InDesign.
The string "Recommended Lifestyle Practices" is made the Table Caption. In FrameMaker the paragraph tag "TableTitle" role maps to the PDF element [Caption]. Perhaps InDesign has something similar?
.
Insert a table having the following configuration:
----| 3 columns.
----| Approriate number of rows.
----| 1 header row (cell content - "Age", "Birth to 12 Years", Ages 13 to 18 years...").
(These would be the only [TH] elements.)
----| Use Table Editor to set each [TH] Scope.
----| Use Table Editor to confirm appropriate Span for applicable cells.
.
The table should flow from one page to another. The [Thead] and its [TH] elements should redraw at the top of subsequent pages.
This should be reflected in the Tagged PDF.
.
Reflow, to be effective, must have a well-formed structure tree. Again, getting that starts in the authoring files.
.
• CVbook_noAccessOption.6.9.pdf On page 24. I was unable to separate the bottom "* Centers for Disease." It needs to read after the top head's asterisk. All bottom text was in one "text" reading block. The only way I could separate was to TORU define text as H3 instead of Text. OK to do this way.
.
Root cause: Tagged PDF is mal-formed. Symantically/logically this is a footnote. The structure tree shows the text for " * " is the content for an [H3] element. Clearly footnotes are not Headings. The PDF element
[Note] is called for here.
.
ISO 32000-1 states that Tagged PDF doesn't dictate footnote placement. This is left to the descreation of the "conforming writer".
Consequently placement in the structure tree can be different (e.g., MS Word to Tagged PDF via PDFMaker or via the MS Save As to PDF or how FrameMaker or InDesign are coded to do the deed). With that said, tweaks to the placement of [Note] and its associated accessible [Link] element is fairly easy. This placement will dictate read order.
.
The only way I could separate was to TORU define text as H3 instead of Text. OK to do this way(?)
.
Assigning an inappropriate PDF element to content is not what you want to do. AT and reflow facilities presume proper use of the PDF elements symantics.
.
• Reflow grays out occasionally in pdfs. Might I be hitting an view change shortcut key?
.
"Gray out" is typically indicative of an overloaded graphics device. The screen is being redrawn/refreshed. Reflow provides a "custom" graphical representation on the screen. Doing this effectively for a PDF necessitates that the PDF be a well-formed Tagged PDF. Even then, graphic images on a PDF page won't reflow (e.g., the document's first page).
As to graphic devices - integrated devices carry the least "load". Dedicated cards with a robust amount of on-card RAM do much better.
.
~~~~~~~
Some observations:
--| Footnotes are present in the content. They are not correctly identified in the structure tree (no [Note] element(s) used).

--| All Tables are, essentially, mal-formed. Regardless of any post-processing work the usability of the tagged content by users of AT is problematic.
AT does the job for end-users provided a clean, simple and properly configured and tagged table is provided.

--| Don't forget to use Full Checker. It identifies a number of basic issues that are present in the document.

--| The reliance on color to denote meaning that is prevalent in the tables will preclude, for those who color related vision issues, accessibility.
This flaw renders the document, as-is, non-compliant with Section 508 (paragraph 1194.22(c)).
Similarly, the document is not fully usable, as-is, to those who rely on high contrast presentation of the information.
-- + ------------------------------------ + --
.
• Pg21_chart_combined.pdf was made using "create new pdf from" combine CVbook_noAccessOption.6.9.pdf only and then selected page 21. I tried with Accessibility options checked and without. Now I can't do reflow, or select table with TURO. Why?
.
I can select the table with TURO.
.
Using Acrobat you certainly can migrate content to a new PDF in the manner you did.
If asked to do so, Acrobat will provide a "best-guess" as to what might be an appropriate tag structure.
How well this is done is determined by how well the content was mastered in the authoring application from which the source PDF for content migration was created.
In InDesign where only built-in headings used to denote heading content, were tables properly mastered, were footnotes properly mastered, were InDesign's upfront tagging tools (for Tagged output PDF) appropriately utilized?
Acrobat is having to make the "educated guess" based on things such as white space, font size, relative positions of the assorted content and, I sure, many other items rolled into the heuristics.
The simpler the content layout and format the better the "guess". Your document is clearly "complex".
.
You've elements in the structure tree that are not associated with any PDF page content ([Document] and all child elements).
In the structure tree under [Article chart 21] you've a malformed [Table] element. Again, effective reflow relies on a well-formed structure tree.
Malformed elements and inappropriate element-content associations don't give the application (Adobe Reader, Acrobat, or PDF agents, AT, etc.) what is needed.
.
For tables the concept of a vertical row of header cells is fine on paper.
For Tagged PDF the basic model is horizontal header row(s).
While this file's table, when presented on paper, "makes sense" (and looks nice) the deliverable in a digital venue has significantly different prerequisites if the content is to be usable as an accessible PDF or a usable PDF on mobile devices.
A success precursor for this genre of PDF calls for remastered tables that, with a proper build, support the output of a well-formed Tagged PDF.
A well-formed structure tree is one of the prerequisites for search engine optimization of PDF, accessible PDF, and PDF that can be effectively processed by software that provides reflow (on the computer or the mobile device).
.



Don't be discouraged. From my perspective most of the "up hill" is due to how the content was mastered back in InDesign.
.

I did a "Time Machine" search for last file before tags is last part of pdf vanished, seems to happening when I try to add replace or add pages.
I've put downloadable pdfs at http://www.mcgraphics.us/source/icon.php CV_book_p1_96_6.9.11.pdf.
But I will put up do a full check for accessibility and hopefully make some changes.

For footnotes and asterisk text as there is no Note in TURO, do I just highlight tag name and type in Note?

I'll try to remove some table headers. Are TD AND TH the only table tags I should use?

Nothing I can change for design or copy, and only so much I can do in InDesign.

So much to learn.
I so appreciate your help.