14:50:36 RRSAgent has joined #pcg-a11y 14:50:40 logging to https://www.w3.org/2024/06/27-pcg-a11y-irc 14:50:46 Zakim has joined #pcg-a11y 14:50:58 zakim, this will be pcg-a11y 14:50:58 ok, AvneeshSingh 14:51:17 present+ 14:51:20 chair: AvneeshSingh 14:51:59 agenda+ Next steps for Issue #280: Do we want to display Reason why the publication does not claim to meet the standards 14:52:16 agenda+ All the accessibility metadata displayed are the claims made by the publisher. How should we convey this fact in our guide. 14:52:29 agenda+ Review of further progress in techniques documents. 14:52:45 agenda+ Any other business. 15:01:01 gpellegrino has joined #pcg-a11y 15:01:08 present+ 15:04:08 MiiaK has joined #pcg-a11y 15:04:36 JonasLillqvist has joined #pcg-a11y 15:05:18 CharlesL2 has joined #pcg-a11y 15:05:29 present+ 15:05:32 scribe+ 15:05:42 zakim, next agendum 15:05:43 agendum 1 -- Next steps for Issue #280: Do we want to display Reason why the publication does not claim to meet the standards -- taken up [from AvneeshSingh] 15:05:49 Hadrien has joined #pcg-a11y 15:05:50 Madeleine has joined #pcg-a11y 15:06:03 https://github.com/w3c/publ-a11y/issues/280 15:06:18 Do we want to display Reason why the publication does not claim to meet the standards] 15:06:28 present+ 15:06:38 Avneesh: some publishers may not want this type of information displayed. 15:07:17 ... Editors call, Gautier suggested separate Conformance Section and Legal Discloser section which could be optional. 15:07:53 ... Gregorio suggested FAP which is meeting on July 5 to ask them about this topic. 15:08:42 q+ 15:08:50 George: this exemption information is not a conformance claim, we put it there inadvertently. Current draft 3 examples of conformance and removed the example of company claiming a hardship claim. 15:09:08 q? 15:09:17 ack next 15:09:38 gpellegrino: I agree, and lets way for legal, and when we get input we can improve it. 15:10:08 q+ 15:10:15 ..., statement ONIX 09 = inaccessible or known accessibility issues. 15:10:26 ..., where do we place this information? 15:10:53 George: if 09 is present is there the possibility the publisher could have put in other a11y features? 15:11:05 q? 15:11:15 ... or a valid onix means those other features would not be present. 15:11:24 ack next 15:11:57 rickj has joined #pcg-a11y 15:12:04 present+ 15:12:35 Hadrien: exemptions - I should have access to this information. if a publication is not accessible I may want to file a report to the regulator. having this information could influence my decision. I agree it doesn't need to be next to other metadata 15:12:39 q? 15:13:23 George, is 09 same as accessibilityFeatures = none. 15:13:30 ccarr has joined #pcg-a11y 15:13:34 q+ for code 09 and none in schema.org 15:13:55 ack next 15:13:57 Hadrien, you wanted to discuss code 09 and none in schema.org 15:13:58 ..., is accessmodesufficient textual is a property not a feature. 15:14:53 Hadrien: I haven't see that type of information. Publisher felt confident enough to add to summary but not in conformance or not accessible. Could change, and this was a large set of data I reviewed. 15:14:59 Q+ 15:15:16 ack ric 15:15:19 q+ 15:15:20 ... distributors / aggregators for small publishers. 15:15:44 ack next 15:15:45 rickj: I agree we don't see any publishers not saying they are inaccessible. but do see some information in the Summary. 15:16:22 gpellegrino: digital comic books of images, accessibility is challenging, Have seem some PDFs with that code for inaccessible. 15:16:44 gautierchomel has joined #pcg-a11y 15:16:45 q+ 15:16:58 AvneeshSingh: do we need to worry about it? not interpret 09 at this time for the first draft. if publishers want it we could include it. 15:17:02 ack next 15:18:18 present+ 15:18:24 q? 15:18:24 gpellegrino: we can skip code 09 comic book for example 09 with our guidelines we will end up with "Unknown" for all required fields. since 09 can add free text can include in the accessiblitySummary section. from the free text in 09 as well as the accessibilitySummary. 15:18:32 Charles: works for me. 15:19:27 q+ 15:20:10 ack next 15:20:32 AvneeshSingh: so this is the ONIX techniques : AccessibilitySummary (addendup, summary and free text from 09) 15:20:50 Hadrien: I have never seen anything useful in those text fields. 15:21:21 q? 15:21:26 AvneeshSingh: lets include it in first draft. this is a compromised instead of leaving it out 09 completely. if they start using it a lot we can revise this. 15:21:28 +1 15:21:48 zakim, next agendum 15:21:48 agendum 2 -- All the accessibility metadata displayed are the claims made by the publisher. How should we convey this fact in our guide. -- taken up [from AvneeshSingh] 15:23:18 gpellegrino: should we add "claim" to each item, but everything in metadata is a claim, even the title, subtitle and all a11y metadata, they could claim mathML but there is none in the file itself (copy/paste) 15:23:33 q+ 15:23:42 ... maybe we can add a note that this metadata is from the publisher and in all claims made by them. 15:23:42 ack gaut 15:24:04 rickj0 has joined #pcg-a11y 15:24:08 q+ 15:24:20 gautierchomel: difference with conformance, claiming could be from a 3rd party certifier. 15:24:37 ... or from a service provider / aggregator etc. 15:24:53 q+ 15:24:55 ... we don't need to specify claim. 15:25:00 rickj 15:25:01 ack irck 15:25:42 ack rick 15:25:58 ack next 15:25:58 rickj: we add a badge "Accessibility claims" for each title with a11y metadata. 15:26:35 q+ 15:26:45 gpellegrino: I like Rick's approach that they whole section is claims made by the publisher. this book claims to be accepted conformance etc. 15:26:51 ack rick 15:27:24 rickj: we like the short wording is made localization much easier in 37 languages they support. we are using compact statement but if you hover over it shows the full statement. 15:27:45 AvneeshSingh: what about screen readers? 15:27:51 q+ 15:28:00 q- 15:28:00 q? 15:28:09 rickj: this is just internal currently but yet we will do that testing. 15:28:21 q? 15:28:33 AvneeshSingh: Accessibility Claims then simplify. 15:29:49 q? 15:30:04 gautierchomel: Claim translated in french doesn't work but "statement" does work well. "Accessibility Decoration" good for French / Italy 15:30:18 zakim, next agendum 15:30:18 agendum 3 -- Review of further progress in techniques documents. -- taken up [from AvneeshSingh] 15:30:40 AvneeshSingh: Onix / EPUB 15:30:53 https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/techniques/onix-metadata/index.html 15:31:14 gpellegrino: nothing to update we have a PR on conformance but we wanted to wait for the decision about conformance / legal. 15:31:54 ... Waiting for Chris to finalize the draft and then we can finalize the PR for ONIX. most of the work has been done. 15:32:06 https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/techniques/epub-metadata/index.html 15:33:02 Charles: holding pattern waiting for ONIX to finalize Conformance / Legal sections. 15:33:08 zakim, next agendum 15:33:08 agendum 4 -- Any other business. -- taken up [from AvneeshSingh] 15:33:27 George: guidance from editors for Principals doc. 15:34:25 rrsagent, make minutes 15:34:26 I have made the request to generate https://www.w3.org/2024/06/27-pcg-a11y-minutes.html AvneeshSingh 15:34:36 rrsagent, make logs public 15:36:31 zakim, leave 15:36:31 leaving. As of this point the attendees have been AvneeshSingh, gpellegrino, CharlesL, Madeleine, rickj, gautierchomel 15:36:31 Zakim has left #pcg-a11y