14:44:16 RRSAgent has joined #pcg-a11y 14:44:16 logging to https://www.w3.org/2022/12/08-pcg-a11y-irc 14:44:26 Zakim has joined #pcg-a11y 14:44:40 zakim, this will be pcg-a11y 14:44:40 ok, AvneeshSingh 14:44:50 present+ 14:45:35 chair: AvneeshSingh 14:50:10 agenda+ Further discussion on the feedback for User experience guide for displaying accessibility metadata. 14:50:40 agenda+ Next steps for accessibility summary guide. 14:50:57 agenda+ Should we have meeting on December 22? 14:51:11 agenda+ Any other business. 14:54:18 gpellegrino has joined #pcg-a11y 14:57:50 gpellegrino has joined #pcg-a11y 14:58:12 ChrisOliverOttawa has joined #pcg-a11y 14:59:07 present+ 14:59:35 Gautier has joined #pcg-a11y 14:59:51 GeorgeK has joined #pcg-a11y 15:00:16 present+ 15:00:27 present+ 15:00:38 tzviya has joined #pcg-a11y 15:01:25 scribe+ 15:01:28 q+ 15:01:33 q- 15:01:38 present+ 15:01:50 MURATA has joined #pcg-a11y 15:01:57 +present 15:02:19 present+ 15:02:19 zakim, next agendum 15:02:20 agendum 1 -- Further discussion on the feedback for User experience guide for displaying accessibility metadata. -- taken up [from AvneeshSingh] 15:02:41 https://github.com/w3c/publ-a11y/issues/136 15:02:44 Terence has joined #pcg-a11y 15:02:47 JF has joined #pcg-a11y 15:02:49 Madeleine has joined #pcg-a11y 15:02:54 present + 15:02:54 Present+ 15:02:55 https://github.com/w3c/publ-a11y/issues/137 15:03:03 https://github.com/w3c/publ-a11y/issues/138 15:03:15 AvneeshSingh: the main issue is 136 and more issues are related: 137, 138 and 139 15:03:23 Naomi has joined #pcg-a11y 15:03:27 q? 15:03:35 present+ 15:04:44 gpellegrino: we tought about level and hired a designer to make mockups, starting by visual approach was usefull to get what place it takes, etc. I can share drafts with you... 15:05:11 ... on the screen you see 2 product pages, one on desktop and one on a phone screen... 15:05:49 ... it is to understand how level organisation could fit in a web page... 15:07:57 ... in thi scase we have a logo near the title that claims compliant with EAA... We think this is the more important information... Then we have a list of 6 tabs grouping informations as asscessibility properties, navigation, non textual content, vusal adjustements, audio and hasard. This is our second level... Certfier information is third level presented on the right of the page... 15:08:41 q? 15:08:47 q+ 15:08:48 Q+ 15:08:53 q+ 15:08:59 ack madel 15:09:22 Bill_Kasdorf has joined #pcg-a11y 15:09:46 present+ 15:09:56 laurent_ has joined #pcg-a11y 15:10:34 Madeleine: it looks good as a first look, and good job. My concern is that there is a lot of energy putted on the accessibility summary too. 15:10:41 q+ 15:10:46 ack jf 15:11:52 q+ 15:11:56 jamesY_ has joined #pcg-a11y 15:12:00 JF: iconography is a very high level information. my concern is related to the requirements of the EAA, is it the same as 501 in US? How to render multiple requirements? 15:12:13 q? 15:12:31 q+ to respond to JF 15:12:55 JamesY__ has joined #pcg-a11y 15:13:23 JF: we adress global market, it's difficult to localize differently. There are multiple conformances possibles, how to adrsse that? 15:13:29 q? 15:13:38 present+ 15:13:49 q+ to rispond to JF 15:14:21 Q+ 15:14:35 q+ 15:14:49 tzviya: it's a good point, but make sure we are not overloading. 15:14:55 ack next 15:14:57 q- 15:15:41 q- 15:16:44 ack me 15:17:12 q+ 15:18:26 q- 15:19:09 q? 15:19:58 Gautier: french publishers says they need more information and reflexion time about infering EAA conformity from Epubaccessibility 15:19:59 ack george 15:20:27 +1 George 15:21:03 q? 15:21:13 +1 George 15:22:26 Georges: local legislations should be the first priority. Also about use of level we maybe should just prioritize informations and says this must be displayed and this is suplementary. Just rank all metadata. 15:22:34 ack next 15:23:07 JamesY_: i agree too much information will be ignored. we have to simplify. What is important is the user... 15:23:23 q? 15:23:57 Q+ to note there are technical standards and "legal" standards 15:24:03 q- 15:24:09 ... for legal aspect, technical standards are probably the best way to express conformity 15:24:23 q? 15:24:32 ack next 15:24:33 JF, you wanted to note there are technical standards and "legal" standards 15:25:34 q+ 15:25:35 q+ 15:25:52 JF: poiting to technical standards is the goal and legal requirements don't point at standards. Having 2 reporting values is needed (one for each) 15:25:53 ack next 15:26:39 MiiaK_ has joined #pcg-a11y 15:27:09 +1 to Naomi 15:27:37 +1 to Naomi 15:27:39 q+ 15:28:16 Naomi: many books don't pass conformance, a user may buy a book partially passing but corresponding to his needs. And the two levels thing helps with that. If there is nothing at first level, then let seen what's in second level. It adress intermediary period 15:28:20 ack bill 15:29:17 Bill_Kasdorf: publisher need is can i sell this book vs user need is can i read this book? 15:29:51 q? 15:29:51 Bill_Kasdorf: even if it's not conformant details may tell me it feets my needs. 15:29:58 ack next 15:30:28 +1 to JamesY__ maintaining compliance badges is going to be complicated 15:30:49 JamesY_: technical and legal changes everytime and may not change in the same directeion. How do we maintain that in time? 15:31:15 q? 15:31:30 q+ 15:33:36 JF: 501 explicitly point to WCAG2.0, not 2.1 or 2.2. If any futur WCAG is not compatible with 2.0 it's regulaor problem, not our. 15:34:00 s/501/508/ 15:34:11 ack next 15:34:56 gpellegrino: what we invision here is similar to other european legislation (exemple is products with CE mark). 15:35:33 q+ 15:35:46 q- 15:36:18 q+ 15:37:20 q- 15:37:37 +1 to Avneesh to how to interpret metadata 15:37:47 +1 to Avneesh 15:38:31 q+ 15:38:32 @AvneeshSingh: there are so many users over the world and so many needs. When we started this document we had 22 objectives : provide a guidance to interpret and display machine readble information and how to prioritize the information needed? We should mainly focus on prioritization, then find labels and at the end build exemples. 15:38:38 q? 15:38:49 ack next 15:39:02 q+ 15:39:55 ack george 15:41:18 GeorgeK: it clearly needs to redivise and look at the language proposed (screen reader friendly don't work in french), i wonder if we could have a localization table in our recomandation. 15:41:50 q? 15:42:05 @AvneeshSingh: editors of the document willl meet to start the writing. 15:42:10 zakim, next agendum 15:42:10 agendum 2 -- Next steps for accessibility summary guide. -- taken up [from AvneeshSingh] 15:42:14 Gautier: I enlist as editor. 15:43:39 https://htmlpreview.github.io/?https://github.com/w3c/publ-a11y/blob/main/drafts/schema-a11y-summary/index.html 15:43:41 GeorgeK: i went thru the document and fixed everything. from my perspective it's done. I expect that when refactoring principles and techniques this will trigger more changes needs to the accessibility Summary. 15:43:47 zakim, next agendum 15:43:48 agendum 3 -- Should we have meeting on December 22? -- taken up [from AvneeshSingh] 15:44:26 q? 15:44:36 @all: skip it, meet next year 15:44:40 zakim, next agendum 15:44:40 agendum 3 was just opened, AvneeshSingh 15:45:18 so 12th of january 15:46:34 rrsagent, make minutes 15:46:34 I have made the request to generate https://www.w3.org/2022/12/08-pcg-a11y-minutes.html AvneeshSingh 15:46:48 rrsagent, make logs public 15:48:51 AvneeshSingh has joined #pcg-a11y 15:49:09 zakim, bye 15:49:09 leaving. As of this point the attendees have been AvneeshSingh, gpellegrino, GeorgeK, ChrisOliverOttawa, Gautier, present, tzviya, JF, Naomi, Bill_Kasdorf, JamesY__ 15:49:09 Zakim has left #pcg-a11y