It would be helpful if annotations such as comments and footnotes/endnotes were connected to the paragraphs they describe.
Some possible approaches:
1. Use accessible relations. In particular:
a. The described-by relationship could be added to the paragraph. This relationship would have as its target the comment or footnote/endnote.
b. The description-for relationship could be added to the comment or footnote/endnote. This relationship would have as its target the paragraph being described.
2. Implement accessible hypertext/hyperlink support for comments and footnotes/endnotes. In particular:
a. The superscripted indicator for footnotes/endnotes would be treated similar to a link insofar as accessible hypertext/hyperlink is concerned. ATs like Orca would then implement the navigation between the paragraph and its annotation.
b. Something similar would need to be done for comments. But since comments seem to have an insertion offset rather than a range, I'm not sure what the best approach would be. Perhaps the start index and end index could both be the value of the character offset?
Thoughts? Other approaches?
(In reply to Joanmarie Diggs from comment #0)
> b. Something similar would need to be done for comments. But since comments
> seem to have an insertion offset rather than a range, I'm not sure what the
> best approach would be. Perhaps the start index and end index could both be
> the value of the character offset?
FTR, comments may have an insertion range too, but the question still applies to the cases when the comment is inserted into a certain position.
Another possibility, along the lines of what I describe in bug 96487: Perhaps the footnote/endnote indicator within the paragraph could (should?) be exposed as a separate accessible object.
If this were done, the footnote/endnote text (which appears as a tooltip associated with the indicator) could be the accessible description of that indicator. And the relationship pair would then be between the indicator and the note.
*** Bug 90724 has been marked as a duplicate of this bug. ***