W3C

- DRAFT -

Accessibility DPUB Task Force Weekly Meeting

26 Aug 2016

See also: IRC log

Attendees

Present
Charles, LaPierre, Avneesh, George, Deborah
Regrets
Tzviya
Chair
clapierre
Scribe
clapierre

Contents


<scribe> ScribeNick: clapierre

PWP Accessible

George: Leonard points out that we have not made it clear that PWP needs to be accessible to persons with disabilities. So, I suggest that we introduce this requirement.

 

Entry: PWP need to be accessible to persons with disabilities when they are intended for use in schools, higher education, government, libraries or for public sale or distribution. The metadata associated with the accessibility and the accessibility hazards must be included.

 

Example 1: A university professor is developing a course and the professor knows that he is required to use accessible digital materials. The professor uses the search capabilities of available publications to determine which titles are accessible and therefore suitable for his use.

 

Example 2: The Center for Disease Control (CDC) wants to produce a PWP explaining the precautions needed in a public epidemic. Persons with disabilities need this same information and the publication is produced accessibility with the appropriate metadata.

 

Deborah: the use case there is a great one, and the software asks that the text is accurate.
... the requirement is that it gives the user all the tools they need to make it accessible.
... add a sentence, PWP needs to be accessible and this includes all components of a PWP such as annotations, etc…
... including annotations which could be user created, which means the annotations tools need to be accessible.
... a lot of stuff is ignored, but once you talk about annotations or anything dynamic, tests, bookmarking and that is authoring tools and there are no usecases there in PWP authoring components needs to be accessible.

George: annotations are on the Rec path and its all the underlying infrastructure and no lines to content, and we had it in originally when we worked with the annotations, and we currently don't have someone from a11y but now it comes through and it doesn't mention the content and whether or not it is accessible.

<scribe> ACTION: dkpalan3 will add a sentence to section #2 that a PWP must be accessible in all components such as annotations etc… [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action01]

<trackbot> Error finding 'dkpalan3'. You can review and register nicknames at <http://www.w3.org/dpub/IG/track/users>.

<scribe> ACTION: dkplan3 will add a sentence to section irc://irc.w3.org:6667/#2 that a PWP must be accessible in all components such as annotations etc… [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action02]

<trackbot> Error finding 'dkplan3'. You can review and register nicknames at <http://www.w3.org/dpub/IG/track/users>.

<scribe> ACTION: dkaplan3 will add a sentence to section irc://irc.w3.org:6667/#2 that a PWP must be accessible in all components such as annotations etc… [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action03]

<trackbot> Created ACTION-59 - Will add a sentence to section irc://irc.w3.org:6667/#2 that a pwp must be accessible in all components such as annotations etc… [on Deborah Kaplan - due 2016-09-02].

George: Example 1: A university professor is developing a course and the professor knows that he is required to use accessible digital materials. The professor uses the search capabilities of available publications to determine which titles are accessible and therefore suitable for his use.

… this brings in metadata and out schema.org which has evolved and is not reflected in the pwp use cases.

Avneesh: this should be in the primary use cases.
... is there any section by Dave on personalization because this falls in the same set.

Write up an initial section that discusses the fact that Ivan raised here

Ivan said: "I had the impression that what deborah said could be formulated noncontroversial. There's no reason to make a comparison to the web. What I heard about the stability of the publication which requires accessibility. The industry has faced legal action. Just stating that accessibility is important. I think it's possible to describe in a positive manor - as an introduction to section 8."

Deborah: someone raised, should we bring up why DPUB do this so much than the rest of the web, which is controversial and the DPUB industry cares which could be legal difference. We shouldn't make the statement that DPUB does this better. we can talk about what the industry does.

Avneesh: this is the intro to section 8 not for section 2.

Charles: lets figure out an intro to 2.

George: schema.org metadata should be a part of PWP moving forward.

Avneesh: before downloading / reading the book does it have the approprate a11y feature that is needed for them.

Charles: this goes in section 2.1.

AvneesH: user should be able to search and know what a11y features are in the book.

Charles: would we point to the IDPF?

Avneesh: that could be a political question. but the usecase is still valid.

<scribe> ACTION: clapierre to write this new statement in section 2.1 [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action04]

<trackbot> Created ACTION-60 - Write this new statement in section 2.1 [on Charles LaPierre - due 2016-09-02].

Avneesh: the main issue is braille. multiple renditions, preformatted, snippets for nemeth etc..

George: mention that there are digital publishing efforts that are focused on delivering specific with people with disabilities and we want to use the same specification.

Deborah: what are the publishing specific use cases for Braille. Ivan was why is this more of an issue with publishing and it is just more of a legal issue with DPUB.
... we don't want to say that the web doesn't care but that is not what we want what say.

Avneesh: we have css files for the braille tables, if a text book has an image of a try, the preformatted braille should also look like a tree. the Web always uses dynamic and we are talking about more stringent requirement.

Deborah: because the DPUB world is so concerned with textbooks, technical documentation and legal documentation the precise and transmission of braille is of vital importance.
... this is the missing piece in the Braille section. Then maybe someone can write a precise example for braille.

<scribe> ACTION: Avneesh, to make a Braille usecase for replica of a textbook and cleanup of existing examples if needed. [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action05]

<trackbot> Error finding 'Avneesh,'. You can review and register nicknames at <http://www.w3.org/dpub/IG/track/users>.

CTION: Avneesh to make a Braille usecase for replica of a textbook and cleanup of existing examples if needed.

A

<trackbot> Created ACTION-61 - Make a braille usecase for replica of a textbook and cleanup of existing examples if needed. [on Avneesh Singh - due 2016-09-02].

George: the two usescases I offerd. one is for discovery and one is for content with metadata, which sits well with the user to identify and find a11y content they can purchase or find

Charles: did we cover web VS epub - dynamic VS static

Avneesh: I think this will be covered and we don't want to make this comparison outright.

Charles: what about the accessible Annotations Use-Case

George: the annotations work had an a11y review but it was all about the plumbing, nothing about content.

<scribe> ACTION: clapierre take George's use case for annotations and put it in a new 8.6 section for accessible annotations. [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action06]

<trackbot> Created ACTION-62 - Take george's use case for annotations and put it in a new 8.6 section for accessible annotations. [on Charles LaPierre - due 2016-09-02].

Charles: my first action will be just to add a sentence on metadata in 2.1 and refer to section 8.1 accessible metadata.

Summary of Action Items

[NEW] ACTION: Avneesh, to make a Braille usecase for replica of a textbook and cleanup of existing examples if needed. [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action05]
[NEW] ACTION: clapierre take George's use case for annotations and put it in a new 8.6 section for accessible annotations. [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action06]
[NEW] ACTION: clapierre to write this new statement in section 2.1 [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action04]
[NEW] ACTION: dkaplan3 will add a sentence to section irc://irc.w3.org:6667/#2 that a PWP must be accessible in all components such as annotations etc… [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action03]
[NEW] ACTION: dkpalan3 will add a sentence to section #2 that a PWP must be accessible in all components such as annotations etc… [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action01]
[NEW] ACTION: dkplan3 will add a sentence to section irc://irc.w3.org:6667/#2 that a PWP must be accessible in all components such as annotations etc… [recorded in http://www.w3.org/2016/08/26-DPUB-minutes.html#action02]
 

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/08/26 18:00:21 $

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)

Succeeded: s/CTION: Avneesh to make a Braille usecase for replica of a textbook and cleanup of existing examples if needed.//
Succeeded: s/Ivan:/Ivan said:/
Found ScribeNick: clapierre
Inferring Scribes: clapierre
Present: Charles LaPierre Avneesh George Deborah
Regrets: Tzviya
Got date from IRC log name: 26 Aug 2016
Guessing minutes URL: http://www.w3.org/2016/08/26-DPUB-minutes.html
People with action items: avneesh clapierre dkaplan3 dkpalan3 dkplan3

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


[End of scribe.perl diagnostic output]