17:01:49 RRSAgent has joined #DPUB 17:01:49 logging to http://www.w3.org/2016/07/08-DPUB-irc 17:01:59 rrsagent, make logs public 17:02:05 scribe: clapierre 17:02:14 chair: clapierre 17:02:27 title: Accessibility DPUB Task Force Weekly Meeting 17:02:44 present+ Tzviya 17:02:59 present+ Charles 17:03:12 present+ Deborah 17:03:49 present+ George 17:05:53 Charles: to ping Heather about pull request for Braille example. 17:06:35 George: 1 I’ll be on a cell phone today. 17:06:36 2 . Perhaps in the new 5.4 or a separate section 5.5 or in an accessibility section, which relates to metadata 17:06:36 x.x.x Accessibility metadata must describe the whole publication 17:06:36   17:06:37 Accessibility metadata of a PWP  relates to the whole publication; the components as an aggregate must be accessible. 17:06:37   17:06:37 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. 17:06:38   17:06:38 x.x.x Accessibility Metadata must be Discoverable 17:06:38   17:06:39 Before a person, school, or university decides to use a PWP, the accessibility of the PWP must be available. 17:06:39   17:06:39 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. 17:06:40   17:06:40 I don’t know if these types of use cases relate directly to PWP, but I thought I would bring them up. 17:08:38 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. 17:08:51 Charles: I will add that. 17:09:26 Tzviya: I am not sure that covers everything you want. you have a11y metadata 17:10:48 … 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. 17:11:13 … just ref. to accessibility section no section #'s. 17:12:55 George: perhaps only 2nd one is relevant since we already have metadata applies to whole package. 17:14:33 Tzviya: whole package metadata, each component is marked up for its own metadata. Maybe this goes in summary. 17:15:07 … I just gave a talk to Wiley since a11y is a spectrum. since it is accessible to some but not all 17:15:44 Tzviya: we need metadata at package level and component 17:16:19 … in 2.1.11 add bullet that says we need accessible metadata at package level 17:17:23 … in accessibility section we can add in the component level accessibility metadata. 17:18:23 Topic: a11y metadata 17:18:58 Charles: manifest metadata on the call. 17:20:12 Tzviya: in Section 8 under manifest we need to add 2 sub items for a11y package level metadata and compoent level metadata 17:20:58 … discoverability metadata not package level. 17:21:31 … George Wrote: Before a person, school, or university decides to use a PWP, the accessibility of the PWP must be available. 17:21:31   17:21:31 \ 17:22:40 … make it more neutral: … must be discoverable so that users knows how accessible the publication is. 17:23:05 Accessibility of a PWP must be discoverable so that users know how (or whether) a PWP is accessible 17:23:26 … then add bullets of usage example 17:23:27 usage examples 17:24:17 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 17:25:48 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. 17:28:12 Deborah: I dislike mice worse than keyboards 17:28:49 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. 17:29:32 Deborah: not allowing keyboard use is SR incomparable. and not allowing keyboard use is not speech control compatible. 17:30:12 … user that uses a mix of keyboard and speech recognition and cant use any pointer devices can only keyboard and keyboard emulation. 17:30:40 George: is this metadata vs. reading system. 17:31:47 George: we can use the word hazard for users identified. "No descriptive Audio", "There is Descriptive audio" 17:31:57 Alejandra must ensure that the videos in her textbook have captioning before she purchases. 17:32:25 Charles: I will add these. 17:32:45 Tzviya: granularity a11y metadata examples needed. 17:33:45 … Statement is: There is a need for component level Accessibility Metadata. 17:34:44 … "there is a need" is a little lacking… 17:36:15 charles: need for knowing chapter 5 only is accessible. 17:36:47 Tzviya: there needs to be metadata for component level on Monday granular metadata for components. 17:38:23 Deborah: I will work on Personalized Experience.. but not until next week. 17:41:28 17:41:28 Tzviya: Assistive Technology. we could probably remove it or add it as another example of a single unit. 17:42:37 … put it as a usage example of assistive technology as a single unit. 17:42:49 … meaning its another use case of 2.1.11 17:42:59 Charles: ok I will add that. 17:44:20 rrsagent, draft minutes 17:44:20 I have made the request to generate http://www.w3.org/2016/07/08-DPUB-minutes.html clapierre 17:45:41 clapierre has left #dpub 17:50:49 zakim, bye 17:50:49 leaving. As of this point the attendees have been Tzviya, Charles, Deborah, George 17:50:49 Zakim has left #dpub 17:50:53 rrsagent, bye 17:50:53 I see no action items