13:46:14 RRSAgent has joined #epub-a11y 13:46:14 logging to https://www.w3.org/2021/06/10-epub-a11y-irc 13:46:29 Zakim has joined #epub-a11y 13:46:43 zakim, this will be epub-a11y 13:46:43 ok, avneeshsingh 13:46:53 present+ 13:47:05 chair: avneeshsingh 13:50:31 ok @tzviya 14:00:25 wendyreid has joined #epub-a11y 14:00:42 MattChan has joined #epub-a11y 14:01:20 present+ 14:01:33 present+ 14:01:59 CharlesL has joined #epub-a11y 14:02:11 present+ 14:02:33 gpellegrino has joined #epub-a11y 14:02:43 Will has joined #epub-a11y 14:02:47 present+ 14:02:47 scribe+ 14:03:39 Cristina has joined #epub-a11y 14:03:41 mgarrish has joined #epub-a11y 14:03:56 Bill_Kasdorf has joined #epub-a11y 14:04:04 present+ 14:04:19 George has joined #epub-a11y 14:04:33 Topic 1: Explainer document for the european union representatives. 14:04:38 present+ 14:04:54 https://www.fondazionelia.org/wp-content/uploads/2021/06/20210609_european_accessibility_act_report_on_the_state_of_the_art_of_publishing_standards.pdf 14:05:08 avneeshsingh: cristina, gpellegrino, and luc updated this doc, and gpellegrino sent today 14:05:19 ... feedback from community has been incorporated 14:05:29 q? 14:05:32 present+ 14:05:34 George has joined #epub-a11y 14:05:45 present+ 14:06:10 George has joined #epub-a11y 14:07:16 q+ 14:07:27 ... if the Explainer has to be updated based on our discussion of the table, gpellegrino can do this 14:07:44 ... in the last section, we are explaining how standards are developed with openness, etc. 14:07:49 q? 14:07:49 q+ 14:07:56 ... is there a need to explain similar process for Schema metadata 14:07:58 ack cris 14:08:22 Cristina: we decided to leave the table within the document even if the table exists elsewhere to make it more simple for commission 14:08:32 q+ 14:08:34 George has joined #epub-a11y 14:08:51 ... if there are just minor changes to the document, we don't need to update the commission, this can be quite static now 14:09:09 ... and we refer to Schemas as W3C managed, but we're open to change in language if you want 14:09:16 ack next 14:09:19 s/Schemas/Schema 14:09:34 George has joined #epub-a11y 14:09:46 gpellegrino: can mgarrish help us with language to describe how Schema is managed? 14:10:16 ... and we don't explicitly say that those spec are from Schema 14:10:31 we are discussing heading of Compliance with ICT TECHNICAL SPECIFICATIONS regulation (Annex II of 1025) in the document 14:11:11 q+ 14:11:14 q+ 14:11:25 Cristina: what is relevant from point of view of the commission is that the standard is managed, open (not copyrighted), and that there is a community around it 14:11:41 ... and that there is no already existing European standard 14:11:48 George has joined #epub-a11y 14:12:17 mgarrish: it probably meets most of those, its managed on github, there are mailing lists for it 14:12:41 ... but it is highly controlled. Not sure that you can just join Schema.org 14:12:57 ... off the top of my head I don't have language to describe that 14:13:05 ... and even within W3C we can't cite Schema.org 14:13:34 George has joined #epub-a11y 14:13:48 ... not considered maintained by official standards organization 14:13:55 Cristina: similar to Editur 14:14:18 q? 14:14:41 ack bill 14:14:45 ... it might be okay for us to be vague on this, mgarrish please have a look and let us know what you think 14:15:13 Bill_Kasdorf: i think the key point is that these things were developed collaboratively 14:15:17 ack char 14:16:01 CharlesL: there are a handful of Schema.org properties we've introduced, and those are locked down, not changing 14:16:23 ... its the vocabulary that goes into those properties that have changed 14:16:41 q+ 14:16:47 ... in the CG we are trying to come up with a standardized way to introduce new values for these properties 14:16:53 ... and we control that 14:17:01 ... there's a distinction there 14:17:28 Bill_Kasdorf: yes, the properties are controlled by Schema, we specify the values 14:17:43 ack gp 14:17:52 avneeshsingh: well, yes, for the accessibility values, not all the values 14:18:13 q+ 14:18:20 mgarrish: to clarify, where EUAA refers to metadata, I mapped to package metadata 14:18:45 s/mgarrish:/gpellegrino: 14:18:48 ack mg 14:19:38 q+ 14:19:45 mgarrish: for a number of years we had these values on a wikipage, but there was no formal control procedure 14:20:45 ... we may want to find a more formal process and place for these 14:21:06 avneeshsingh: is there any working group for Schema.org in W3C? 14:21:10 mgarrish: there's a CG 14:21:33 avneeshsingh: I will discuss with with people who are writing W3C process 14:21:55 ... back to main topic, do we have to explain how Schema.org meets the requirements of the Commission? 14:22:00 +1 to Matt :) 14:22:06 ack bill 14:22:27 Bill_Kasdorf: i'd trust mgarrish to make that call about the Explainer 14:22:53 ... but it seems the most important thing is that the same metadata is used to describe website a11y and epub a11y 14:23:47 ack cris 14:24:53 Cristina: i'm not sure the Commission will go into such detail. It is important for the document to be accurate, but I think what they really want is to be sure that the standards are already in line with EUAA, and what is already in practice 14:25:15 ... but yes, please, mgarrish have a look and let us know 14:25:34 ... and we can update the document in the future, but for the Commission I think what we have is enough 14:26:40 george: agreed. What we're proposing isn't controlled by some single company, not a proprietary standard 14:26:43 q? 14:27:07 Cristina: we've also prepared an article that we have published on LIA website, but if Inclusive Publishing wants to use it or a shortened version of it, we are okay 14:27:19 ... it is a less technical summary of what is in the Explainer 14:27:27 ... we can share link 14:27:44 Topic 2: Mapping of the requirements of European accessibility act to EPUB Accessibility specifications. If we are satisfied with it, then we should approve sending it to whole EPUB 3 WG for approving it as working group note. 14:28:00 https://github.com/w3c/epub-specs/tree/main/reports/eu-a11y-mapping 14:28:15 https://w3c.github.io/epub-specs/reports/eu-a11y-mapping/ 14:28:27 avneeshsingh: can we approve in this group so that we can share with the bigger group? 14:29:19 gpellegrino: we might add more detail to the media overlay section 14:29:33 ... and maybe add some info about pagelists? 14:29:48 ... pagelists are not a requirement of EUAA, but it is a feature that can help accessibility 14:30:14 https://w3c.github.io/epub-specs/reports/eu-a11y-mapping/#annex-I-section-IV-f-iii 14:30:23 ... we would add to this section 14:30:38 avneeshsingh: and that section is about navigation, which relates to pagelist 14:30:40 q? 14:30:49 ... any objection to these two suggestions? 14:30:54 present+ 14:31:07 ... okay, gpellegrino please make those changes 14:31:14 (iv) Allowing alternative renditions of the content and its interoperability with a variety of assistive technologies, in such a way that it is perceivable, understandable, operable and robust 14:31:26 q+ 14:31:28 q+ 14:31:32 ... this is a requirement of EUAA about renditions 14:31:51 ... it has two parts: 1) allows rendition, and 2) interop with variety of AT 14:32:34 https://w3c.github.io/epub-specs/reports/eu-a11y-mapping/#annex-I-section-IV-f-iv 14:32:56 ... a number of WCAG principles address the interop point, but not necessarily the allows rendition point 14:32:57 q+ 14:33:40 gpellegrino: we have a problem with this statement in EUAA, because in epub world rendition has a specific meaning 14:33:51 ... but in EUAA, rendition means only the ability to get the same content in different ways 14:34:07 ... so I didn't link directly to our rendition spec 14:34:42 ... especially since other specs like for PDF, HTML, they also don't have renditions in the way epub spec means 14:34:48 q+ to suggest providing a definition of rendition 14:35:03 avneeshsingh: well HTML can have a link to a more accessible version of the webpage 14:35:46 CharlesL: I think we need to add more information to the headings of the mappings document, more than just the identifying section numbers 14:35:59 gpellegrino: i had a lot of trouble making this document readable 14:36:26 ... in each section I want to put the entirety of the EUAA text, but that text is too long to fit 14:36:35 ... if you have any ideas, please let me know 14:36:58 ack CharlesL 14:37:01 ack gpellegrino 14:37:03 ack Bill_Kasdorf 14:37:22 Bill_Kasdorf: the fundamental enabling technology for this is HTML because it is designed to be rendition independent 14:37:37 Avneesh_ has joined #epub-a11y 14:37:42 ... and epub content is HTML 14:37:45 q+ 14:37:50 ... makes braille readers possible, etc. 14:37:52 ack tzviya 14:37:52 tzviya, you wanted to suggest providing a definition of rendition 14:38:16 +1 14:38:17 +1 I can add a note 14:38:23 ack mgarrish 14:38:28 tzviya: i think the problem here is that word "rendition", and we can't change EUAA, but maybe our document can disambiguate how that term means something different in epub spec 14:38:49 +1 to WCAG as a whole 14:38:52 mgarrish: the EUAA rendition requirement is basically requiring WCAG, right? 14:39:55 ... I would refer to all of WCAG, instead of just particular pieces of it 14:40:26 +1 to mgarrish 14:40:34 Avneesh_: so what do we think about 1) referring to the 4 principles of WCAG, and 2) disambiguating the term rendition? 14:40:39 q? 14:40:41 gpellegrino: yes, agree. I can do that. 14:40:49 Topic 3: Review guidance on success criterion 1.3.2 : 14:41:02 https://github.com/w3c/epub-specs/issues/1695 14:41:37 actual text is at: 14:41:40 https://w3c.github.io/epub-specs/epub33/a11y-tech/#access-001 14:42:09 mgarrish: this is about meaningful sequence of content, and meaningful sequence of documents 14:42:38 ... sequence of documents isn't specifically an a11y issue, it's a basic requirement for the epub to function 14:42:51 q+ 14:43:23 q- 14:43:25 q? 14:43:29 q+ 14:43:33 ... going into spine ordering and all this other stuff in this part of the Techniques might be irrelevant here 14:44:41 q+ 14:45:00 ack gp 14:45:19 ... maybe we can just strip this stuff 14:45:40 gpellegrino: does it also apply to the hierarchical order of the headings? 14:46:13 gpellegrino: I don't think that's an issue for this section, that would fall under headings 14:46:29 s/gpellegrino:/mgarrish: 14:46:57 mgarrish: this is more about having the reading order matching the visual sequence of the epub 14:47:37 Avneesh_: so we keep statement that the logical reading order applies across the epub, but leave out the stuff about spine, etc. 14:48:54 q? 14:49:18 ack charl 14:49:43 CharlesL: how would this affect choose your own adventure style books where you might not have a logical progression? 14:50:00 mgarrish: I think that's again a separate issue 14:50:30 q+ 14:50:45 ... in that example, there's still a reading order, its just that you decide that order based on your ability to access the links 14:50:55 q? 14:52:04 ack me 14:52:05 tzviya: this just explicitly spells out what most publishers do anyway, so there should be no problem with removing the example about the spine 14:52:18 proposed: approve request in issue #1695 14:52:34 +1 14:52:36 +1 14:52:37 +1 14:52:39 +1 14:52:44 +1 14:52:48 +1 14:53:04 +! 14:53:06 +1 14:53:18 resolved 14:53:28 TOPIC: AOB? 14:53:35 q+ 14:53:53 q+ 14:53:58 https://www.w3.org/TR/WCAG22/#changelog 14:54:18 ack tzviya 14:54:19 tzviya: there's a call for review of WCAG 2.2, they are requesting comment by tomorrow, but this isn't the final round of revisions 14:54:24 ack mg 14:55:06 Avneesh_: we'll defer discussion of a11y note in the main group to next week's meeting then, since we have to make revisions 14:55:34 ... okay thank you everyone 14:55:59 rrsagent, draft minutes 14:55:59 I have made the request to generate https://www.w3.org/2021/06/10-epub-a11y-minutes.html Avneesh_ 14:57:31 zakim, bye 14:57:31 leaving. As of this point the attendees have been avneeshsingh, wendyreid, MattChan, CharlesL, gpellegrino, Cristina, George, mgarrish, Bill_Kasdorf, tzviya, ! 14:57:31 Zakim has left #epub-a11y 14:57:44 CharlesL has left #epub-a11y 14:58:04 zakim, leave 15:00:11 rrsagent, make logs public