<scribe> scribe: clapierre

title: Accessibility DPUB Task Force Weekly Meeting

Charles: to ping Heather about pull request for Braille example.

George: 1 I’ll be on a cell phone today.

2 . Perhaps in the new 5.4 or a separate section 5.5 or in an accessibility section, which relates to metadata

x.x.x Accessibility metadata must describe the whole publication

 

Accessibility metadata of a PWP  relates to the whole publication; the components as an aggregate must be accessible.

 

For example, a publication that has chapters 1,2,3 as accessible, but chapter 4 is not accessible, the metadata would indicate that the publication is not accessible.

 

x.x.x Accessibility Metadata must be Discoverable

 

Before a person, school, or university decides to use a PWP, the accessibility of the PWP must be available.

 

For example, a professor is looking for digital textbooks to use in the course. The professor knows that there are regulations that require accessible educational materials. In addition, the professor is a moral person and would never knowingly use inaccessible educational materials. The professor uses the available metadata about a PWP to determine if the publication is appropriate for the class.

 

I don’t know if these types of use cases relate directly to PWP, but I thought I would bring them up.

Tzviya: on wednesday we have section 2.1.11 PWP treated as a single unit as apposed to individual case. we can add #1 above as an example.

Charles: I will add that.

Tzviya: I am not sure that covers everything you want. you have a11y metadata
... lets add a11y metadata currently that section is currently unstructured, currently section 8. Maybe 8.1 or 8.2 Metadata. in #2.1.11 say see a11y and then these two items George wrote would go in 8.1.
... just ref. to accessibility section no section #'s.

George: perhaps only 2nd one is relevant since we already have metadata applies to whole package.

Tzviya: whole package metadata, each component is marked up for its own metadata. Maybe this goes in summary.
... I just gave a talk to Wiley since a11y is a spectrum. since it is accessible to some but not all
... we need metadata at package level and component
... in 2.1.11 add bullet that says we need accessible metadata at package level
... in accessibility section we can add in the component level accessibility metadata.

a11y metadata

Charles: manifest metadata on the call.

Tzviya: in Section 8 under manifest we need to add 2 sub items for a11y package level metadata and compoent level metadata
... discoverability metadata not package level.
... George Wrote: Before a person, school, or university decides to use a PWP, the accessibility of the PWP must be available.

 

\

scribe: make it more neutral: … must be discoverable so that users knows how accessible the publication is.

<tzviya> Accessibility of a PWP must be discoverable so that users know how (or whether) a PWP is accessible

scribe: then add bullets of usage example

<tzviya> usage examples

<tzviya> A professor wants to use an accessible textbook in her classroom and cannot make the decision about a book without information about the accessible assets in the book

<tzviya> Ferdous wants to buy a book about a museum exhibit and wants to make sure that his screen reader will describe the images to him in great detail.

Deborah: I dislike mice worse than keyboards

Tzviya: interactive textbook, HR training seminars and powerpoint which are not modal, so I click 400 times in 45 since they don't allow keyboard use.

Deborah: not allowing keyboard use is SR incomparable. and not allowing keyboard use is not speech control compatible.
... user that uses a mix of keyboard and speech recognition and cant use any pointer devices can only keyboard and keyboard emulation.

George: is this metadata vs. reading system.
... we can use the word hazard for users identified. "No descriptive Audio", "There is Descriptive audio"

<tzviya> Alejandra must ensure that the videos in her textbook have captioning before she purchases.

Charles: I will add these.

Tzviya: granularity a11y metadata examples needed.
... Statement is: There is a need for component level Accessibility Metadata.
... "there is a need" is a little lacking…

charles: need for knowing chapter 5 only is accessible.

Tzviya: there needs to be metadata for component level on Monday granular metadata for components.

Deborah: I will work on Personalized Experience.. but not until next week.

Tzviya: Assistive Technology. we could probably remove it or add it as another example of a single unit.
... put it as a usage example of assistive technology as a single unit.
... meaning its another use case of 2.1.11

Charles: ok I will add that.

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)

Found Scribe: clapierre
Inferring ScribeNick: clapierre
Present: Tzviya Charles Deborah George

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: 08 Jul 2016
Guessing minutes URL: http://www.w3.org/2016/07/08-DPUB-minutes.html
People with action items: 

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