Create export-8.html - #43
Open
zakkinsey wants to merge 4 commits into
Open
Conversation
Collaborator
Author
|
@romantoda - did I hear correctly that, in Derivation, FENote will derive to Span? So maybe we should map FENote to Span? |
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-note-fenote-is-rows-36-40-see-row-98-that-might-clarify-putting-this-note-here-from-the-meeting-in-paris-note-should-be-treated-however-we-decide-to-handle-fenote-question-based-on-derivation-group">`Note FENote is rows 36 - 40 See row 98 - that might clarify? Putting this note here… From the meeting in Paris, Note should be treated however we decide to handle FENote.` <span class="el-context">(Question based on Derivation group conversation (6/28/23) - Note to be derived to "small" - how does this impact us, here?)</span></h4> |
There was a problem hiding this comment.
I don't think we need this one. There was a note in the Google sheet about treating Note and FENote similarly, which I think is valid. However, on the Export 8 sheet, this is row 6 and the mapping is to doc-endnote, in DPub. Do we need to specify this? Is this something that the author - or remediator - would be expected to set, if the Note tag in question is used as an endnote? Is there "real" value in doing so?
At the same time, as we've previously discussed, there should be our "default" mappings but then if someone adds an ARIA role then that should be honored. So, for example, we should not map to doc-endnote unless that ARIA role has been "assigned" to a tag.
PaulRayius-2
reviewed
May 6, 2026
| </table> | ||
|
|
||
| <h4 id="role-note-fenote-is-rows-36-40-see-row-98-that-might-clarify-putting-this-note-here-from-the-meeting-in-paris-note-should-be-treated-however-we-decide-to-handle-fenote-question-based-on-derivation-group">`Note FENote is rows 36 - 40 See row 98 - that might clarify? Putting this note here… From the meeting in Paris, Note should be treated however we decide to handle FENote.` <span class="el-context">(Question based on Derivation group conversation (6/28/23) - Note to be derived to "small" - how does this impact us, here?)</span></h4> | ||
| <table class="data" aria-labelledby="role-note-fenote-is-rows-36-40-see-row-98-that-might-clarify-putting-this-note-here-from-the-meeting-in-paris-note-should-be-treated-however-we-decide-to-handle-fenote-question-based-on-derivation-group"> |
There was a problem hiding this comment.
Suggested change
| <table class="data" aria-labelledby="role-note-fenote-is-rows-36-40-see-row-98-that-might-clarify-putting-this-note-here-from-the-meeting-in-paris-note-should-be-treated-however-we-decide-to-handle-fenote-question-based-on-derivation-group"> | |
| <table class="data"> |
PaulRayius-2
reviewed
May 6, 2026
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-note-fenote-is-rows-36-40-see-row-98-that-might-clarify-putting-this-note-here-from-the-meeting-in-paris-note-should-be-treated-however-we-decide-to-handle-fenote-question-based-on-derivation-group">`Note FENote is rows 36 - 40 See row 98 - that might clarify? Putting this note here… From the meeting in Paris, Note should be treated however we decide to handle FENote.` <span class="el-context">(Question based on Derivation group conversation (6/28/23) - Note to be derived to "small" - how does this impact us, here?)</span></h4> |
There was a problem hiding this comment.
Suggested change
| <h4 id="role-note-fenote-is-rows-36-40-see-row-98-that-might-clarify-putting-this-note-here-from-the-meeting-in-paris-note-should-be-treated-however-we-decide-to-handle-fenote-question-based-on-derivation-group">`Note FENote is rows 36 - 40 See row 98 - that might clarify? Putting this note here… From the meeting in Paris, Note should be treated however we decide to handle FENote.` <span class="el-context">(Question based on Derivation group conversation (6/28/23) - Note to be derived to "small" - how does this impact us, here?)</span></h4> | |
| <h4 id="role-note-endnote">`Note`<span class="el-context">(`Note` used as `endnote`)</span></h4> |
PaulRayius-2
reviewed
May 6, 2026
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-note-2">`Note`</h4> |
There was a problem hiding this comment.
Suggested change
| <h4 id="role-note-2">`Note`</h4> | |
| <h4 id="role-note-footnote">`Note` <span class="el-context">(DPub `doc-footnote`)</span></h4> |
PaulRayius-2
reviewed
May 6, 2026
| </table> | ||
|
|
||
| <h4 id="role-note-2">`Note`</h4> | ||
| <table class="data" aria-labelledby="role-note-2"> |
There was a problem hiding this comment.
If we change line 181 then we should change this here, too? So it's not role-note-2 but role-note-footnote?
PaulRayius-2
reviewed
May 6, 2026
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Consult with W3C: This is "richer" than "generic" in ARIA</code></span> |
There was a problem hiding this comment.
Suggested change
| <span class="property">Note from PDFa: <code>Consult with W3C: This is "richer" than "generic" in ARIA</code></span> | |
| <span class="property">Note: <code>TBD - placeholder</code></span> |
This appears multiple times in this export. I think we should remove all of these but I didn't just suggest the deletion in case we wanted to keep the TR as a placeholder or to be consistent.
PaulRayius-2
reviewed
May 6, 2026
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-note-3">`Note`</h4> |
There was a problem hiding this comment.
What is "doc-tip"? Is that like a "Tip..." where someone gives "advice"? I don't think that's the intent of the Note tag and if that's what doc-tip is then I don't think we should use this mapping for Note.
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
PaulRayius-2
reviewed
May 6, 2026
Comment on lines
+145
to
+179
| <h4 id="role-note-fenote-is-rows-36-40-see-row-98-that-might-clarify-putting-this-note-here-from-the-meeting-in-paris-note-should-be-treated-however-we-decide-to-handle-fenote-question-based-on-derivation-group">`Note FENote is rows 36 - 40 See row 98 - that might clarify? Putting this note here… From the meeting in Paris, Note should be treated however we decide to handle FENote.` <span class="el-context">(Question based on Derivation group conversation (6/28/23) - Note to be derived to "small" - how does this impact us, here?)</span></h4> | ||
| <table class="data" aria-labelledby="role-note-fenote-is-rows-36-40-see-row-98-that-might-clarify-putting-this-note-here-from-the-meeting-in-paris-note-should-be-treated-however-we-decide-to-handle-fenote-question-based-on-derivation-group"> | ||
| <tbody> | ||
| <tr> | ||
| <th>ARIA Specification</th> | ||
| <td><a class="core-mapping" href="https://www.w3.org/TR/dpub-aam-1.1/#role-map-endnote">Role: `doc-endnote`</a> <span class="el-context">(DPub)</span></td> | ||
| </tr> | ||
| <tr> | ||
| <th>Analogous HTML Element</th> | ||
| <td>Use WAI-ARIA mapping</td> | ||
| </tr> | ||
| <tr> | ||
| <th>MSAA + IAccessible2</th> | ||
| <td>Use WAI-ARIA mapping</td> | ||
| </tr> | ||
| <tr> | ||
| <th><abbr title="User Interface Automation">UIA</abbr></th> | ||
| <td>Use WAI-ARIA mapping</td> | ||
| </tr> | ||
| <tr> | ||
| <th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology - Service Provider Interface">AT-SPI</abbr></th> | ||
| <td>Use WAI-ARIA mapping</td> | ||
| </tr> | ||
| <tr> | ||
| <th><abbr title="macOS Accessibility Protocol">AX API</abbr></th> | ||
| <td>Use WAI-ARIA mapping</td> | ||
| </tr> | ||
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td> | ||
| <span class="property">Note from PDFa: <code>Consult with W3C: This is "richer" than "generic" in ARIA</code></span> | ||
| </td> | ||
| </tr> | ||
| </tbody> | ||
| </table> |
Discussed in LWG call 5/19/26 Co-authored-by: PaulRayius-2 <paul@pdfix-us.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.