Create export-16.html - #51
Conversation
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Note: Ref entry not only needs to be "exposed" but processors should also provide the functionality to go to wherever the Ref entry is pointing!</code></span> |
There was a problem hiding this comment.
| <span class="property">Note from PDFa: <code>Note: Ref entry not only needs to be "exposed" but processors should also provide the functionality to go to wherever the Ref entry is pointing!</code></span> | |
| <span class="property">Note: <code>Note: Ref entry not only needs to be "exposed" but processors should also provide the functionality to go to wherever the Ref entry is pointing!</code></span> |
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Should be "self explanatory" except that there are a lot of questions around how to handle Alt - and Actual - Text - and how to handle them when both are present, etc. See "Questions" doc.</code></span> |
There was a problem hiding this comment.
| <span class="property">Note from PDFa: <code>Should be "self explanatory" except that there are a lot of questions around how to handle Alt - and Actual - Text - and how to handle them when both are present, etc. See "Questions" doc.</code></span> | |
| <span class="property">Note: <code>TBD</code></span> |
Alt text, itself, is probably well understood. However, @zakkinsey @daniel-montalvo , we perhaps should define or clarify, when a tag has Alt text, if and when any substructure, and its content, inside that tag, should also be read. For example, If a Figure tag has Alt text but also contains a Caption tag with text in it. We would want the text in the Caption tag to be read, too. Or if a Figure tag, with Alt text, contains links. We would want those links to be exposed.
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Should be "self explanatory" except that there are a lot of questions around how to handle Alt - and Actual - Text - and how to handle them when both are present, etc. See "Questions" doc.</code></span> |
There was a problem hiding this comment.
| <span class="property">Note from PDFa: <code>Should be "self explanatory" except that there are a lot of questions around how to handle Alt - and Actual - Text - and how to handle them when both are present, etc. See "Questions" doc.</code></span> | |
| <span class="property">Note: <code>TBD</code></span> |
I changed the "Note" but we still will need to figure out, @zakkinsey , @daniel-montalvo - is ActualText a "thing" in HTML? And, if not, we'll need to make sure that developers understand, in the PDF context, what ActualText is. And then we'll also need to define - perhaps with a new table, here, how to handle when a tag has both Alt and ActualText assigned to it.
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Use WAI-ARIA mapping</code></span> |
There was a problem hiding this comment.
| <span class="property">Note from PDFa: <code>Use WAI-ARIA mapping</code></span> | |
| <span class="property">Note: <code>TBD</code></span> |
I removed "Use WAI-ARIA mapping" because, above, some APIs actually say to use HTML mapping.
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>How should Contents entries be handled when a single tag contains multiple Annotations? (A Link tag, for example, with multiple link Annotations inside.) If there is a Contents entry on an Annotation and Alt on the containing tag, those shall be identical. So, both should (shall?) not be exposed.</code></span> |
There was a problem hiding this comment.
| <span class="property">Note from PDFa: <code>How should Contents entries be handled when a single tag contains multiple Annotations? (A Link tag, for example, with multiple link Annotations inside.) If there is a Contents entry on an Annotation and Alt on the containing tag, those shall be identical. So, both should (shall?) not be exposed.</code></span> | |
| <span class="property">Note: <code>The Contents entry is on the annotation, not on its containing structure element.</code></span> |
I changed the note but the question that was there is still valid. How should Contents entries be handled when a single tag contains multiple Annotations? (A Link tag, for example, with multiple link Annotations inside.)
Also, if there is a Contents entry on an Annotation and Alt on the containing tag, those shall be identical, according to PDF/UA-2, at least. I would think that we would not want both exposed then, or that would just be redundant noise. But this also kind of relates back to the question in line 67, then.
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Use WAI-ARIA mapping</code></span> |
There was a problem hiding this comment.
| <span class="property">Note from PDFa: <code>Use WAI-ARIA mapping</code></span> | |
| <span class="property">Note: <code>TBD</code></span> |
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Use WAI-ARIA mapping</code></span> |
There was a problem hiding this comment.
| <span class="property">Note from PDFa: <code>Use WAI-ARIA mapping</code></span> | |
| <span class="property">Note: <code>TBD</code></span> |
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Use WAI-ARIA mapping</code></span> |
There was a problem hiding this comment.
| <span class="property">Note from PDFa: <code>Use WAI-ARIA mapping</code></span> | |
| <span class="property">Note: <code>TBD</code></span> |
|
LWG conversation... we wonder if this export shouldn't even be merged and, instead, add some prose to the AAM explaining how to handle when any PLSE has Alt (or ActualText, or E) and also contains substructure. |
Clarify notes and double-check IDs.