Skip to content

Annotations #749

Closed
Closed

Description

@jnurthen

from https://www.w3.org/WAI/ARIA/track/issues/655

Proposal to support commenting, inline error highlighting, etc. in documents.

Office wants to be able to make these types of annotations more accessible. Commenting on a document is a pretty common scenario, and this would be useful to many web app developers.

We'd like to explore creating this as an extension spec. I have a person from the Office team who is willing to do the heavy lifting.
http://www.w3.org/2014/04/annotation/submissions/Microsoft_Position_Paper_on_Annotations.pdf

Activity

  1. added this to the milestone on May 9, 2018
  2. changed the title [-]Consider creating annotations roles for comments, spell-check errors, etc[/-] [+]Annotations[/+] on May 9, 2018
  3. jnurthen commented on May 9, 2018

    @jnurthen
    MemberAuthor

    Also https://www.w3.org/WAI/ARIA/track/issues/670

    See Response from Doug Schepers to me reqarding the formation of an Annotation Working Group pertaining to remote annoation requirements:
    http://lists.w3.org/Archives/Public/public-digipub-ig/2014Jul/0030.html

  4. jnurthen commented on May 9, 2018

    @jnurthen
    MemberAuthor

    https://www.w3.org/WAI/ARIA/track/actions/1454

    dd aria-hasannotation attribute with values: comment, footnote, endnote, reference, insertion, deletion, modification, true, false, more where aria-hasannotation has only one value at a time

  5. jnurthen commented on May 9, 2018

    @jnurthen
    MemberAuthor

    https://www.w3.org/WAI/ARIA/track/actions/1455

    Add aria-annotatedby where it takes idrefs as a value and must only be applied when that same element has aria-hasannotation

  6. jnurthen commented on May 9, 2018

    @jnurthen
    MemberAuthor
  7. azaroth42 commented on May 11, 2018

    @azaroth42

    The TR for web annotations, including commenting and highlighting:
    https://www.w3.org/TR/annotation-model/

  8. modified the milestones: ARIA 1.4, ARIA 1.2 on Oct 26, 2018
  9. aleventhal commented on Nov 15, 2018

    @aleventhal
    Contributor

    I've put an updated draft proposal on the Wiki:
    https://github.com/w3c/aria/wiki/ARIA-annotations-draft-proposal
    This draft incorporates comments from the F2F in Lyon.

  10. azaroth42 commented on Nov 15, 2018

    @azaroth42

    The J Paul Getty Trust would formally object to this unless it is at least aligned with existing W3C standards for Annotation.

  11. 31 remaining items

  12. aleventhal commented on Jan 13, 2020

    @aleventhal
    Contributor

    This is now landed in Chrome Canary (Chrome 81).

    I filed some follow-up issues:
    AOM - WICG/aom#157
    Firefox - https://bugzilla.mozilla.org/show_bug.cgi?id=1608883

    Updated existing WebKit bug - https://bugs.webkit.org/show_bug.cgi?id=165842

    CORE-AAM doesn't need any changes, it already says there could be multiple elements.

  13. added a commit that references this issue on Feb 13, 2020
  14. cookiecrook commented on Mar 5, 2020

    @cookiecrook
    Contributor

    @aleventhal requested public comment.

    No concerns re: ARIA Annotations from Apple Accessibility Engineering. I'll stop short of a formal "Intent to Implement," but it's an area of interest that we hope to implement at some point in the future. Congrats on shipping it in Chrome and Firefox.

  15. pkra commented on Feb 27, 2021

    @pkra
    Member

    I think this can be closed as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions