14:52:54 RRSAgent has joined #pcg-a11y 14:52:58 logging to https://www.w3.org/2024/07/11-pcg-a11y-irc 14:53:02 Zakim has joined #pcg-a11y 14:53:17 zakim, this will be pcg-a11y 14:53:17 ok, AvneeshSingh 14:53:30 present+ 14:53:40 chair: AvneeshSingh 14:56:01 agenda+ Updates to the Principles and techniques documents. 14:56:31 agenda+ Preparing for first public working draft. 14:56:47 agenda+ Any other business. 15:00:06 gautierchomel has joined #pcg-a11y 15:01:22 gpellegrino has joined #pcg-a11y 15:01:32 present+ 15:03:23 George has joined #pcg-a11y 15:03:38 present+ 15:05:23 scribe+ 15:05:29 present+ 15:05:41 zakim, next agendum 15:05:41 agendum 1 -- Updates to the Principles and techniques documents. -- taken up [from AvneeshSingh] 15:05:57 Principles: https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/?updated 15:05:58 ChrisOliverOttawa has joined #pcg-a11y 15:06:09 George: I made a PR for the Legal consideration new section 15:06:48 Present+ 15:06:53 ... I had some comments from editors and I'm waiting for other feedback 15:07:26 ... I have a question about this section, do we want to say something about the jurisdiction 15:07:28 q+ 15:07:38 ack next 15:08:09 Simon_Mellins has joined #pcg-a11y 15:08:16 present+ 15:08:20 q? 15:08:32 gpellegrino: I don't think it's only a matter of jurisdiction 15:08:50 George_ has joined #pcg-a11y 15:09:04 ... it's also about end user information, supply chain information 15:09:18 ... I think we shouldn't be strict 15:09:36 q? 15:09:48 q+ 15:09:59 ack next 15:10:36 Hadrien has joined #pcg-a11y 15:10:45 present+ 15:10:58 George: is there any metadata where the metadata the publisher can tell if the metadata has to be displayed or not 15:11:09 ...? 15:11:31 gpellegrino: no way to target the audience of a specific metadata 15:11:47 q+ 15:12:07 George: I can add information about the supply chain 15:12:17 ack next 15:13:00 ChrisOliverOttawa has joined #pcg-a11y 15:13:13 q? 15:13:27 q+ 15:13:28 q+ 15:14:26 AvneeshSingh: I see another use case from national agencies that have to use this information in their work of enforcement 15:14:35 ack next 15:15:19 Hadrien: I've already heard organization that are basing their procurement of ebooks based on accessibility and accessibility metadata 15:15:50 ack next 15:15:51 ... like in education and public libraries, more and more organizations are enforcing it 15:17:11 gautierchomel: I think publishers we'll use the guidelines to decide of what to put in their metadata for having something displayed 15:17:12 q+ 15:18:39 ... in our guidelines we have always focused on readers and information that are meaningful for them 15:19:11 q+ 15:19:21 ... I think we can get consensus in a generic phrase to put 15:19:28 ack next 15:23:45 q+ 15:24:08 gpellegrino: We already have in the guidelines indications for different type of implementations (B2C, B2B) and both user-friendly and detailed information (like for Conformance) 15:24:59 George: ok, what may we put if the publisher do not provide any metadata, but only the exception one? 15:25:01 ack next 15:25:36 gautierchomel: a generic phrase that say that the title is not compelled to be accessible 15:25:55 Hadrien: I think that we need to have a broader view, not only B2C 15:26:33 ... because no one else will work on other guidelines 15:27:14 ... as a distributor operating in Europe I would ask the publisher title-by-title if they're compliant with the EAA 15:27:17 ack next 15:27:49 Simon_Mellins: I think it's crucial that the user knows if a title is exempted 15:28:15 ... but also we should say that the publisher "claims" to be excempted 15:28:27 ... because it has to be proven 15:29:23 ... another important thing would be the publisher contact information, for leaving the user the possibility to contact the publisher 15:29:53 George: about the claim: at the end every metadata is a claim from the publisher, so I removed "claim" from the statements 15:30:32 ... and added a section telling that the whole section of metadata is about claims 15:30:38 q? 15:31:08 ... and we are suggesting to call the whole section in the UI the "accessibility claims" or "accessibility declaration" 15:31:56 Simon_Mellins: is it only VitalSource that will do that? 15:32:16 George: we are suggesting for all implementers to call that section in the UI "accessibility claims" 15:33:03 q+ 15:33:48 q+ 15:34:06 ack next 15:34:06 George: if as a publisher I put the exception metadata, do I want to display something? 15:34:34 gautierchomel: My proposal is that any exception metadata trigger one common sentence 15:34:52 ... like "this ebook is excempted..." 15:34:54 ... rather than indicating which type of exception is being claimed 15:35:26 ... then we're making a guidelines, so every implementer can decide what to display 15:35:33 ... or not display 15:35:52 ack next 15:36:12 Hadrien: I think that the complex thing about this conversation is that publishers don't have control on what metadata will be displayed 15:36:48 ... I think that having a simple sentence is important 15:37:13 ... at the same time I think that micro-enterprise is really different from disporpotionated burden 15:37:50 ... because in the first case you don't have do prove it, in the second you need to make calculations 15:37:57 q+ 15:38:07 q? 15:38:23 q+ 15:38:31 AvneeshSingh: I suggest to make a generic statement, and then link to issuue tracker 15:38:41 ack next 15:39:32 ack next 15:39:57 gpellegrino: I think that then the part of the sentence about what publishers want is misleading 15:40:56 q? 15:40:59 Simon_Mellins: I think publishers may not want to display this information, at the same time we should be on the readers side, and for them having this information may be important 15:41:33 George: do we want to suggest to contact the publisher 15:41:34 q+ 15:41:38 q+ 15:42:27 may we suggest to use the accessibility summary to give publisher contacts? 15:42:55 ack next 15:44:07 ack next 15:44:50 gpellegrino: It seems a little bit misleading to give direction to publishers in this guidelines, seems they are not the target audience 15:45:38 gautierchomel: I think that don't listening publishers' voice is not a good thing for this guidelines 15:45:59 q? 15:46:16 George: do we want to open a new issue and link to the new issue? 15:46:57 gautierchomel: I think having a new issue is good, since now we have reached consensus and we have a new discussion 15:47:07 George: I'll do it 15:47:27 gpellegrino: no updates on the ONIX side of techniqes 15:48:07 George: no updated on the EPUB metadata side 15:48:16 zakim, next agendum 15:48:16 agendum 2 -- Preparing for first public working draft. -- taken up [from AvneeshSingh] 15:48:28 ... I think we'll then have to make sections on both techniques for Legal considerations 15:48:57 AvneeshSingh: we are nearly ready to publish the first public working draft 15:49:16 ... the scope is to present it to the industry and get feedback 15:49:25 q? 15:49:41 ... do you think we're missing something before publish the draft? 15:49:53 George: the only question I have is about sample implementation 15:49:59 q+ 15:50:16 ... maybe we need to have the draft published before having the implementations 15:50:19 ack next 15:50:48 gautierchomel: we have an implementation in French 15:51:02 ... but maybe it's better to wait 15:51:39 q? 15:51:44 AvneeshSingh: yes, I think we can wait and than update the draft 15:52:06 gautierchomel: maybe is better to have a separate page for list of implementations 15:52:47 AvneeshSingh: we made this section for giving the reader different type of implementations of there guidelines 15:52:57 ... with different flavours 15:53:19 q? 15:53:42 q+ 15:53:53 ack next 15:54:29 gautierchomel: my concern is if we have too many implementations 15:54:55 gpellegrino: I think we have an issue for listing all the implementers, we can reference it from the Implementation section 15:55:10 q? 15:55:21 q+ 15:55:36 ack next 15:56:49 q? 15:56:52 AvneeshSingh: when will we be ready to publish the first draft? 15:57:36 gpellegrino: if we're in a rush, we can publish it by the end of the next week 15:57:52 George: I will tell BISG, for their webinar 15:59:05 AvneeshSingh: maybe we can ask people from the group to give feedback on specific sections of the document 15:59:15 George: we can ask Matt to read it 16:00:06 AvneeshSingh: do we need another call two weeks from now? 16:00:25 q? 16:00:44 George: I don't think a lot of people will partecipate 16:01:06 q? 16:01:50 rrsagent, make minutes 16:01:51 I have made the request to generate https://www.w3.org/2024/07/11-pcg-a11y-minutes.html AvneeshSingh 16:02:01 rrsagent, make logs public 16:02:59 zakim, leave 16:03:00 leaving. As of this point the attendees have been AvneeshSingh, gpellegrino, George, gautierchomel, ChrisOliverOttawa, Simon_Mellins, Hadrien 16:03:00 Zakim has left #pcg-a11y 16:13:04 George_ has joined #pcg-a11y