13:55:55 RRSAgent has joined #pcg-a11y 13:55:55 logging to https://www.w3.org/2022/05/19-pcg-a11y-irc 13:56:12 rrsagent, make log public 13:56:27 rrsagent, bookmark 13:56:27 See https://www.w3.org/2022/05/19-pcg-a11y-irc#T13-56-27 13:57:11 meeting: PCG-a11y sub-taskforce on Accessibility Summary 13:57:37 Date: 19 May 2022 13:57:58 chair: Georgek 14:01:37 TerenceSmyre has joined #pcg-a11y 14:02:17 AlexGrover has joined #pcg-a11y 14:03:34 Michelle_ has joined #pcg-a11y 14:05:07 Makoto has joined #pcg-a11y 14:05:13 present+ 14:06:01 CharlesL has joined #pcg-a11y 14:06:31 present+ 14:06:35 mgarrish has joined #pcg-a11y 14:06:41 present+ 14:06:52 duga has joined #pcg-a11y 14:06:54 zheng_xu has joined #pcg-a11y 14:06:54 present+ 14:06:57 present* 14:06:58 present+ 14:06:59 present+ 14:06:59 present+ 14:07:09 present+ 14:07:11 present+ 14:07:21 scribe: zheng_xu 14:07:28 Naomi has joined #pcg-a11y 14:07:37 present+ 14:07:59 GeorgeK: we have updated the columns in the repo, the question is now we have got a couple of roles in the table. If we were to add all the possible combinations we are gonna have quite a few 14:08:13 topic: Table columns have been updated with: Accessibility Metadata, Priority and  Suggested summary 14:08:22 https://htmlpreview.github.io/?https://github.com/w3c/publ-a11y/blob/main/drafts/schema-a11y-summary/index.html 14:08:37 ... we want to provide guidance of the first column 14:09:25 ... some publisher have confirmance statement in internal standards 14:09:40 ... the question is how we structure the columns 14:10:11 Rachel: we are tracking state internal, not a really standard but benefit for us 14:10:33 q+ 14:10:36 GeorgeK: so you just use the internal fields internally and not to put in the summary 14:10:41 q+ 14:10:45 ack Makoto 14:11:23 Makoto: I am wondering if DAISY Japan introduce fields especially for Japan publications we might need to add to accessibility summary as well 14:12:22 GeorgeK: in that case can you put some explaination 14:12:32 Makoto: yes 14:12:33 q+ 14:12:55 GeorgeK: so how we can structure the table? 14:13:22 ack Michelle_ 14:13:42 q+ 14:14:04 Michelle_: I wonder if we could have external statement and internal statement 14:14:16 ... some publisher might want to use certain external statement 14:14:48 ack me 14:15:16 CharlesL: I wonder if we could map your needs to see which statement could be internal or external 14:15:50 ... one thing is we have a lot of confirmTo statement and we have some issues 14:16:02 ... because some of them are referring to internal resources 14:16:11 ... I think we need to make it clear 14:16:44 ... back to george's question for the WCAG case we can have some general statement 14:16:54 ... maybe we can expand table? 14:16:56 ack mgarrish 14:18:37 mgrrish: the text itself is pretty generic. How we represent the different string metadata? 14:19:10 ... I don't think we need lots and lots of different statement but think we might have some basic statement 14:20:03 s/maybe we can expand table?/I don't think we need to expand the table. 14:21:07 GeorgeK: so we link the crosswork in accessibilitySummary. If company is produsing this from ONIX then they can generate accessibilitySummary from there since not all epub has this field 14:21:17 ... does this sound correct? 14:21:46 s/basic statement/basic statement. Only way to tell internal/external we would have to use the refines statement, is the only option we have available programmatically within the OPF. 14:23:10 GeorgeK: multiple confirmsTo is included in a11y 11 spec? 14:23:16 mgarrish: need to check 14:24:14 GeorgeK: move on to the 2nd item in the agenda 14:25:14 ... which group we are going to link to? 14:27:14 ... so we got two crosswalk - schema.org and ONIX, schema.org and MARC 14:29:23 ... now for example of confirmsTo, we got accessibilityFeature and so on, for the confirmsTo what are we linking to 14:29:36 CharlesL: maybe still IDPF for now 14:30:06 mgarrish: we can use publishing a11y since it's only in the epub a11y right now 14:30:53 GeorgeK: so what do we link to from accessibilitySummary to give people correct confirmsTo? 14:31:25 ... is it the EPUB Accessibility specification link (https://www.w3.org/TR/epub-a11y-11/) ? 14:31:46 mgarrish: if that is to provide the mapping and confirmsTo then can link to it 14:32:48 ... just try how to structure the a11y table 14:33:23 s/... just try how to structure the a11y table/GeorgeK: just try how to structure the a11y table 14:35:11 GeorgeK: ok, now we are clear about which crosswalk we are going to link to 14:36:22 ... question to Brady, if a book has multiple languages then in accessibilitySummary how do we deal with multiple language? For book with more languages it's going to be complicated 14:36:45 duga: I don't think we need to overengeneer it 14:37:40 ... if a book is in English and French and in Canada then if there is any legal reason for it we might have issue there though 14:38:05 ... but in most cases we only get one language for a book in the bookstore 14:39:17 ... suggest remain silent here since we don't know if that is a true use case 14:39:47 ... but I can not make any statement here yet 14:41:11 q+ 14:44:09 GeorgeK: ok let's not close this issue yet. We might not want to go to multiple accessibilitySummary and we assume take the first one 14:45:08 Naomi: I agree with not make statement yet. The scope can be very quick snowball 14:46:12 GeorgeK: we get one more issue in the agenda 14:47:08 ... when publisher provide contact information for help or feedback do you think we could put it as part of accessibilitySummary? 14:48:06 Naomi: one issue is the hardcoded metadata in epub might be outdated later. Maybe still just email address is good enough? 14:48:28 q+ 14:48:57 q+ 14:49:05 Rachel: we maintain generic a11y issue email and we included it in book and else where I don't know if needed to put it as part of accessibilitySummary 14:49:34 q+ 14:50:11 q+ 14:50:44 duga: this is kinda beyond accessibility but we also get all feedback of typo and stuff 14:51:21 ... I don't think the contact in accessibilitySummary is very helpful and we might have a lot false positive 14:53:35 mgarrish: I don't know if people look at metadata for accessibility related contact. 14:54:06 ... recommend not put in accesibilitySummary 14:54:25 Michelle_: second mgarrish 14:54:38 ... might not be necessary for library as well 14:55:26 GeorgeK: ok I suggest close this issue and put minuts in the github link 14:56:23 ... next call is June 2nd 14:56:40 ... thank you everyone and talk later 14:57:21 zakim, end meeting 14:57:21 As of this point the attendees have been AvneeshSingh, CharlesL, GeorgeK, g_pellegrino, AlexGrover_, MadeleineRothberg, Naomi_, Makoto, AlexGrover, mgarrish, duga, zheng_xu, 14:57:24 ... TerenceSmyre, Michelle_, Naomi 14:57:24 RRSAgent, please draft minutes 14:57:26 I have made the request to generate https://www.w3.org/2022/05/19-pcg-a11y-minutes.html Zakim 14:57:26 I am happy to have been of service, zheng_xu; please remember to excuse RRSAgent. Goodbye 14:57:31 Zakim has left #pcg-a11y 15:08:04 GeorgeK_ has joined #pcg-a11y 18:11:40 CharlesL has left #pcg-a11y