RE: DPUB Interest Group | Accessibility review of Open Annotations - Action Item

Quote: Under Social Reading and Annotations > Other Use Cases, I added 2
new use cases related to accessibility:

   - Making sure the annotations can be found:
   https://www.w3.org/dpub/IG/wiki/Anno_A11y_1

Rob's Comment: Mostly implementation guidelines, rather than requiring any
particular feature in the model/vocabulary/serialization I think, but very
important!



Suzanne's Comment: Yes, but it might be important for defining length and
readibility that the use of the categorization data model as perhaps items
in a menu for navigation be known upfront.



Quote: In Anno-Specific-4 (Annotating Embedded Resources), I added bullet
three under "Requirements":

   - Ability to select all or part of alternative versions of resources
   (i.e. some portion of the alternative text) and have these exposed without
   assistive technology to those who read the comments.

Rob's Comment: I think this is fundamental enough that it deserves its own
separate use case? The functionality of annotating an image, versus the
functionality of annotating the alt-text of an image seems quite distinct
to me?



Suzanne's Comment: I agree, do you want me to write it, or will you write
it?



Thanks!


 ------------------------------

*From:* Robert Sanderson [mailto:azaroth42@gmail.com]
*Sent:* Thursday, February 06, 2014 10:46 AM
*To:* Suzanne Taylor
*Cc:* Richard Schwerdtfeger; Gerardo Capiel; George Kerscher; Markus
Gylling; Thea Eaton; W3C Digital Publishing IG
*Subject:* Re: DPUB Interest Group | Accessibility review of Open
Annotations - Action Item





Hi Suzanne, all,



Thanks so much for doing that! :)







On Wed, Feb 5, 2014 at 9:44 PM, Suzanne Taylor <suzanne.taylor@pearson.com>
wrote:

Under Social Reading and Annotations > Other Use Cases, I added 2 new use
cases related to accessibility:

   - Making sure the annotations can be found:
   https://www.w3.org/dpub/IG/wiki/Anno_A11y_1

  Mostly implementation guidelines, rather than requiring any particular
feature in the model/vocabulary/serialization I think, but very important!




   - Making sure the annotations can be categorized:
   https://www.w3.org/dpub/IG/wiki/Anno_A11y_2

  Whereas this one requires a slot in the model for the label.
 Categorization (or tagging) of annotations has been discussed in the OACG,
and there are several ways to accomplish it.  The easiest is a property on
the annotation, body or specific resource (in order of ease).  The more
systematic and interoperable way is to annotate the annotation with the
category in the manner of tagging any other resource.





  In Anno-Specific-2 (Highlighting a Span of Text) and Anno-Specific-3
(Commenting on a Span of Text), under dependencies, I added links to
"Making sure the annotations can be found":
https://www.w3.org/dpub/IG/wiki/Anno_A11y_1 and to the longer use case from
the accessibility section.



+1



  In Anno-Advanced-3 (Maintaining Annotation Style), under dependencies, I
added links to "Making sure the annotations can be categorized":
https://www.w3.org/dpub/IG/wiki/Anno_A11y_2  and to the longer use case
from the accessibility section.



+1





  In Anno-Specific-4 (Annotating Embedded Resources), I added bullet three
under "Requirements":

   - Ability to select all or part of alternative versions of resources
   (i.e. some portion of the alternative text) and have these exposed without
   assistive technology to those who read the comments.

  I think this is fundamental enough that it deserves its own separate use
case? The functionality of annotating an image, versus the functionality of
annotating the alt-text of an image seems quite distinct to me?



  In Anno-Specific-5 (Annotating Parts of Embedded Resources), I added
bullet three under "Requirements":

   - High level semantic description of the part (i.e. 'user selected
   portion of this image') and ability for the annotator to name the part
   (i.e. 'the oak tree')

  +1 (and see comments above about categorization/tagging)



  In Anno-Advanced-6 (Recording State of User Manipulated Resources), I
added bullet three under "Requirements":

   - Ability for the annotator to name the state (i.e. 'view from
   underground looking up at the tree roots')

  And +1 again :)



Many thanks Suzanne and Rich!



Rob