W3C

- DRAFT -

SV_MEETING_TITLE

20 May 2016

See also: IRC log

Attendees

Present
Charles_LaPierre, Tzviya, Bill_K, Deborah
Regrets
George_Kerscher
Chair
clapierre
Scribe
clapierre

Contents


<scribe> scribe: clapierre

Tzviya: gave update on Stockholm meetings this past week. Only two publishers attended. NYPL was represented with their lending app, which was impressive.
... , met a number of DAISY members which was great.

A11Y Use Cases for PWP

Charles: these are the Use cases for DIAGRAMMAR which may be relavent to DPUB.

Production Use Cases

Description: Production Use Cases are targeted towards all users that will participate in creation of (or facilitating the creation of) accessible formats of digital media.  These include some of the following types of users as examples:

 

• Rights owners (e.g. publishers, authors, photographers, artists)

• Alternate format production specialists

• Contracted volunteers

• General populace of volunteers

https://docs.google.com/document/d/1GcwrWIXSTfQYJlufbceK8utU8KPdOZp2wtj2T23P9hQ/edit?usp=sharing

Deborah: what do you think of as a use-case for PWP?

Tzviya: we have navigating across multiple documents, and extended descriptions beyond images.

Deborah: what are the use-cases of what needs to be in a PWP doc. not authoring tools. Given a user / consumer of a PWP with an a11y need. what are the use cases for that user?

<tzviya> http://w3c.github.io/dpub-pwp-ucr/

Tzviya: Heather has uploaded a lot of high level use-cases, which are brief and need more work fleshing them out.
... look at #3.3
... , opening the publication off-line should still have the bookmarks.

Deborah: we should all go look at the document charles provided and remove anything that is not relavent for next meeting.

Tzviya: Benetech has few versions of image descriptions but may not fit in this document but write it now and see where it fits in later.

Charles: I will get the google doc done and send out the link asking for comment.

Tzviya: don't worry about making this perfect, and we really need to start adding issues to the github tracker for Heather before Wednesday's F2F.

Charles: Ok will get that doc link and ask for everyone to look at this document and start adding issues to the PWP Use-case issue tracker before Wednesdays F2F.

title: Accessibility DPUB Task Force Weekly Meeting

s/https://docs.google.com/document/d/1GcwrWIXSTfQYJlufbceK8utU8KPdOZp2wtj2T23P9hQ/edit?usp=sharing/<charles to send link to google shared doc in email>/

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/05/20 17:32:37 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

WARNING: Bad s/// command: s/https://docs.google.com/document/d/1GcwrWIXSTfQYJlufbceK8utU8KPdOZp2wtj2T23P9hQ/edit?usp=sharing/<charles to send link to google shared doc in email>/
Found Scribe: clapierre
Inferring ScribeNick: clapierre
Present: Charles_LaPierre Tzviya Bill_K Deborah
Regrets: George_Kerscher

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 20 May 2016
Guessing minutes URL: http://www.w3.org/2016/05/20-DPUB-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]