W3C home > Mailing lists > Public > public-digipub-ig@w3.org > February 2014

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

From: Suzanne Taylor <suzanne.taylor@pearson.com>
Date: Wed, 5 Feb 2014 23:44:51 -0500
Message-ID: <27aa322a9f71174bccc9a032286d014e@mail.gmail.com>
To: Richard Schwerdtfeger <schwer@us.ibm.com>, Robert Sanderson <azaroth42@gmail.com>
Cc: Gerardo Capiel <gerardoc@benetech.org>, George Kerscher <kerscher@montana.com>, Markus Gylling <markus.gylling@gmail.com>, Thea Eaton <thea@doodledoo.com>, W3C Digital Publishing IG <public-digipub-ig@w3.org>
Rob - I reviewed all of your use cases with accessibility in mind. Their
efficient expression, organization and content are impressive.



I'm sending a list of the additions I made to make it easy to review and
vet the additions:



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
   - Making sure the annotations can be categorized:
   https://www.w3.org/dpub/IG/wiki/Anno_A11y_2



While these 2 follow the format of the rest of the Annotations use cases,
both of these point also to a longer use case in the accessibility section,
which includes rationale, more explanation and user interface requirements.
The current version of the longer use case in the accessibility section is
here (
https://www.w3.org/dpub/IG/wiki/Accessibility_When_Users_Select_and_Highlight_Text)
and will be further improved.





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.



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.



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.



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')



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')






From: Robert Sanderson <azaroth42@gmail.com>
To: Markus Gylling <markus.gylling@gmail.com>
Cc: Suzanne Taylor <suzanne.taylor@pearson.com>, Richard
Schwerdtfeger/Austin/IBM@IBMUS, Gerardo Capiel <gerardoc@benetech.org>,
George Kerscher <kerscher@montana.com>, Thea Eaton <thea@doodledoo.com>
Date: 01/28/2014 10:56 AM
Subject: Re: DPUB Interest Group | Summary of Annotations Comments Task |
Due Feb 5
 ------------------------------





Dear all,

A couple of introductory presentations that may be useful to get up to
speed with Open Annotation:

High level presentation:
    http://www.slideshare.net/azaroth42/oai8-openanno

Core Data Model:

http://www.slideshare.net/azaroth42/open-annotation-core-data-model-tutorial

And if there's questions, I'm very happy to either reply by email or have a
conference call to walk through some of the points.

Many thanks :)

Rob



On Tue, Jan 28, 2014 at 8:15 AM, Markus Gylling <markus.gylling@gmail.com>
wrote:

Adding Rob Sanderson, co-chair of OA CG to the thread. Rich, Rob was the
one who offered you help re introducing you to OA at the end of the call
yesterday.
/markus


On Tue, Jan 28, 2014 at 12:41 AM, Suzanne Taylor <suzanne.taylor@pearson.com>
wrote:

Thanks:




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


*From:* Richard Schwerdtfeger [mailto:schwer@us.ibm.com]
* Sent:* Monday, January 27, 2014 2:42 PM
* To:* Suzanne Taylor
* Cc:* Gerardo Capiel; George Kerscher; Markus Gylling; Thea Eaton
* Subject:* Re: DPUB Interest Group | Summary of Annotations Comments Task
| Due Feb 5



Hi Suzanne,

Thank you. There was a Bill something on the call today. Do you have his
email information.

[Suzanne Taylor:]

Probably Bill Kasdorf (bkasdorf@apexcovantage.com)

We need to look at the open annotation work for additional accessibility
issues. For example, did they alot for multiple people being identified as
annotators and which annotations apply to whom? What about Notes? There are
cross-cutting opportunities here for things like online interactive office
documents. We address some of this in IBM Docs but it is not as
standardized. We would want this work to be such that annotations be
spareable across a cloud - which I am sure the annotation people have
already considered.

[Suzanne Taylor:] Ah, very important! So it's not just do the things being
proposed as standards include accessibility, but also a push for more
things to be part of standardization to get past reliance on proprietary
solutions, which are often not accessible.



The first problem I found was with the <mark> element. The HTML5 platform
accessibility API mapping guide maps <mark> to text which does not convey a
lot about the fact that it is highlighted to an assistive technology. The
HTML A11y task force people responsible for mapping never completed the
work. We will be starting that work back up. Here is a link to first drafts
of outlines for three interoperability specs we will be creating:

I drafted these:

http://www.w3.org/WAI/PF/wiki/Outline_Core_User_Agent_Implementation_Guide#Core_User_Agent_Implementation_Guide

If you look at the current implementation guide spec for <map> you will see
the current defined mapping:
http://www.w3.org/TR/2012/WD-html-aapi-20120329/

We will need one for the ePub structural semantics as well. This may
require platform accessibility API extensions. We will see.

Rich



Rich Schwerdtfeger

[image: Inactive hide details for Suzanne Taylor ---01/27/2014 11:26:43
AM---This is just a note to summarize the deliverable that Rich]Suzanne
Taylor ---01/27/2014 11:26:43 AM---This is just a note to summarize the
deliverable that Rich, Gerardo and I accepted in the meeting to

From: Suzanne Taylor <suzanne.taylor@pearson.com>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS, George Kerscher <
kerscher@montana.com>, Gerardo Capiel <gerardoc@benetech.org>, Thea Eaton <
thea@doodledoo.com>
Cc: Markus Gylling <markus.gylling@gmail.com>
Date: 01/27/2014 11:26 AM
Subject: DPUB Interest Group | Summary of Annotations Comments Task | Due
Feb 5
 ------------------------------




This is just a note to summarize the deliverable that Rich, Gerardo and I
accepted in the meeting today to make sure everyone knows what's taking
place and also to make the documents easier to find.

The Annotations Taskforce of the DPUB IG is looking to publish a note by
April.

So, their use cases will move forward rapidly. Our task is to review the
following with a view toward ensuring that accessibility is considered as
part of the whole:


    - We need to edit and expand on this use case on accessibility
         requirements generally and move (or copy) it from the
accessibility section
         to the annotations section:
         http://www.w3.org/dpub/IG/wiki/Mark_Highlighting (we could expand
         into multiple use cases, if we want)
         - We need to review the annotations use cases and add any
         accessibility comments. These are here:
         http://www.w3.org/dpub/IG/wiki/UseCase_Directory#Social_Reading_and_Annotations

         - This seems to be a key document to also review:
         http://www.w3.org/community/openannotation/  I haven't read this
         yet, so I'm not 100% sure what we need to do with it, if
anything, at this
         point. It might just be good background.




The accessibility comments are due Feb 5th and the Interest Group will look
for interest group buy-in in the call on Feb 10th.

Thanks,
Suzanne


* Suzanne Taylor*
Director, Accessibility Solutions
Pearson UX

T: (201)236-7781

* Pearson *
Always Learning
Learn more at www.pearson.com


Can all learners use your product? Make sure: Pearson's Accessibility
Guidelines for Digital Learning http://wps.pearsoned.com/accessibility

image001.gif
(image/gif attachment: image001.gif)

Received on Thursday, 6 February 2014 04:45:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:35:48 UTC