14:52:29 RRSAgent has joined #pcg-a11y 14:52:34 logging to https://www.w3.org/2023/06/22-pcg-a11y-irc 14:52:40 Zakim has joined #pcg-a11y 14:52:55 zakim, this will be pcg-a11y 14:52:55 ok, AvneeshSingh 14:53:08 present+ 14:53:18 chair: AvneeshSingh 14:53:56 agenda+ Proposal for refactoring the principles document of User experience guide for accessibility metadata. 14:54:16 agenda+ Schedule for July and August? 14:54:29 agenda+ Any other business. 14:57:35 gpellegrino has joined #pcg-a11y 14:58:25 gautier has joined #pcg-a11y 14:58:34 Makoto has joined #pcg-a11y 14:58:39 GeorgeK has joined #pcg-a11y 14:59:20 present+ 15:00:44 present+ 15:00:53 present+ 15:01:06 laurab has joined #pcg-a11y 15:01:15 CharlesL has joined #pcg-a11y 15:01:25 present+ 15:01:33 scribe+ 15:01:33 present+ 15:01:35 Makoto_ has joined #pcg-a11y 15:01:42 present+ 15:01:49 zakim, next agendum 15:01:49 agendum 1 -- Proposal for refactoring the principles document of User experience guide for accessibility metadata. -- taken up [from AvneeshSingh] 15:01:55 present+ 15:02:06 paulgilius has joined #pcg-a11y 15:02:13 https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/?updated 15:02:13 GeorgeK has joined #pcg-a11y 15:02:17 https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/?updated 15:02:19 mgarrish has joined #pcg-a11y 15:02:19 present+ 15:02:39 AvneeshSingh: 4 sections the editors have worked on. 15:02:41 Naomi has joined #pcg-a11y 15:02:51 … Visual Adjustments 15:03:09 present+ 15:03:19 gautier: As Nav section, quick definition, and some examples. 15:03:35 … Visual adjustments one key info vs. Nav with multiple. 15:03:47 Hadrien has joined #pcg-a11y 15:04:07 present+ 15:04:08 GeorgeK has joined #pcg-a11y 15:04:15 … 4.2 Visual Adjustments 15:04:15 15:04:15 A Yes/No/Unknown answer to the question "Can a user change the aspect of textual contents". 15:04:15 Indicates if the appearance of the text and the page layout can be modified according to the possibilities offered by the reading system. 15:04:54 Readers with visual impairment or cognitive disabilities rely on the ability to change color of background and texts, font family and font size as well as spaces between letters, words, sentences or paragraphs. 15:04:54 The reflowable information alone is not sufficient to make sure that modifications operated will not result on text overlaying or unreadable colors. 15:05:03 … See the 4.2.1 Examples 15:05:25 present+ 15:06:08 GeorgeK has joined #pcg-a11y 15:06:14 q? 15:07:01 gpellegrino: this information, we don't use only the positive information 15:07:31 q+ 15:07:55 … what would be there if one can not change the appearance of the text. 15:08:08 GeorgeK has joined #pcg-a11y 15:08:21 … text on visual and we don't have displayTransformability. 15:08:35 … we can say the User can not change the display of the content. 15:08:43 ack next 15:09:36 Naomi: if displayTransformabiltiy is present then we can use the first example. We do save text as images, and if the lack of metadata would imply a fixed layout and close to the print version. 15:09:48 q+ 15:10:06 ChrisOliverOttawa_ has joined #pcg-a11y 15:10:08 George: you aren't putting in displayTransformability in your EPUBs? 15:10:08 GeorgeK has joined #pcg-a11y 15:10:23 q+ 15:11:10 Naomi: No because there are text overlayed as an image but a manuscript or poem we would put in the image. Highly desinged titles does happen. so we don't use that accessibilityFeature. 15:11:13 q- 15:11:48 gautier: I agree DisplayTransformability is for all reflowable files because parts may not be. 15:11:49 q+ 15:12:08 GeorgeK has joined #pcg-a11y 15:12:13 … many books will get an unknown value. which is not good for communication / selling books 15:12:16 ack next 15:12:54 Hadrien: did a presentation where extracted numbers for Spanish markets 160K EPUB files only 200 of them had DisplayTransformability. I have partial data for other markets. 15:12:58 q+ 15:13:17 q+ 15:13:23 … we are seeing DisplayTransformability is used that much. We see that this is missing. 15:14:06 q+ 15:14:09 GeorgeK has joined #pcg-a11y 15:14:13 … this is tricky. default situation if there is nothing its unknown. FXL or PDF we would assume then NotDisplayTransformability would be implied. 15:14:22 … this one is hard to infer. 15:14:29 ack cha 15:15:07 GeorgeK has joined #pcg-a11y 15:16:27 ack next 15:16:54 Charles: Add an accessibilitySummary if there are images with text but keep DisplayTransformability 15:17:21 ack geo 15:17:21 q+ 15:17:40 gpellegrino: if most of the main content can be transformed then include that metadata and make a note in the summary. 15:17:51 ack next 15:17:59 George: I agree as long as the image has proper alt text this is fine. 15:18:08 GeorgeK has joined #pcg-a11y 15:18:54 Avneesh: Principals document there were no negative comments. interpretation of the metadata, and if the metadata is common or not. 15:18:57 q+ 15:19:11 … how to achive / interpret it. 15:19:14 ack cha 15:20:08 GeorgeK has joined #pcg-a11y 15:20:14 Charles: I think there are two many examples? 15:20:31 gpellegrino: At least Yes/No and Unknown. we can discuss in editors call 15:20:33 Charts, Diagrams and Formulas 15:20:44 Topic: Charts, Diagrams and Formulas 15:21:23 gpellegrino: this wasn't present in excel file, this info was in big group of book features. We needed to subdivide it into smaller set of features. 15:21:48 … important info of Charts, Diagrams, and Formulas in STEM. 15:22:08 GeorgeK has joined #pcg-a11y 15:22:28 … 4.4 Charts, Diagrams and Formulas 15:22:28 15:22:28 This group of metadata is used to indicate to end users the presence of formulas and complex graphs, charts and diagrams within the title and whether or not these are usable in accessible format: for example, whether formulas are navigable with assistive technologies, or whether extendend descriptions are available for complex images. 15:22:28 This group should be displayed only if the metadata indicates the presence of formulas or charts and graphs within the title, otherwise it can be hidden. 15:22:56 … see 4.4.1 Examples 15:23:59 q? 15:24:18 GeorgeK has joined #pcg-a11y 15:24:39 … I can express these schema.org values, but same information in ONIX 15:25:24 … metadata accessMode ChartsOnVisual, etc. MathML or describedMath, longDescriptions can create this output from that info. 15:25:30 q? 15:26:46 George: important to point out that these can be determined depending on the metadata present same for other groups. importnat to point out in principals that it may require more than 1:1 mapping and its a combination 15:27:17 GeorgeK has joined #pcg-a11y 15:28:18 gpellegrino: we have two positive values describedMath and MathML can be used with Formulas, but if those are present only. Charts and Graphs can only be provided if Charts/DiagramsONVisual but longDescriptions must also be present 15:28:19 q? 15:28:42 Conformance 15:28:49 Topic: Conformance 15:30:40 GeorgeK has joined #pcg-a11y 15:30:42 George: 4.7 Conformance 15:30:42 15:30:42 The conformance group provides the assertions made concerning the accessibility of the publication. The language should be simple and report if accessibility recommendations are being met or if the publication is below suggested recommendations. At a minimum, the specification which it conforms to and the party doing the certification must be provided. It is also possible to determine if the certification is done by a third party. If t 15:30:43 he publisher and the certifier property are different, then this indicates the certification was done by a third party. The credentials of the certifying party and the date of the evaluation will be of interest and should be provided. If there is a link to a report of the evaluation, that can also be provided. 15:30:43 Conformance Statement 15:30:43 Identifies the accessibility specification and the conformance level to which the publication assertions are made. When the publication conforms to more than one specification, additional conformance statements may be provided. 15:30:44 Certifier's name 15:30:44 This provides information about the organization providing the certification review or process for certification. Having third party certification is of high interest and should be provided. Third party certification can be determined by comparing the name of the publisher and name of the certifier. If the values are different, then third party certifications are true. This can be provided as a parenthetical expression, i.e., inside pa 15:30:44 rentheses. 15:30:44 Certifier's Credentials 15:30:44 If the certifier has a badge or a credential, then the text is provided. If there is a link to their credential, then this can be provided as a link. 15:30:45 Certification date 15:30:45 If the date of the certifiers evaluation is provided, then this would be of interest. This is normally associated with the certifier. 15:30:45 Certifier's Report 15:30:46 If a link to a report is provided, this may be of interest. 15:30:46 15:31:40 see 4.7.1 Examples 15:33:22 George: some countries may have A as the standard but others at AA, but the 1.1 specifies AA. 15:33:42 … we talked about not being so technical to understand what WCAG is. 15:33:57 AvneeshSingh: This is a little complex. 15:34:08 GeorgeK has joined #pcg-a11y 15:34:19 … Example 1: • This publication meets accessibility recommendations and reports (EPUB Accessibility 1.1 and Web Accessibility Content Guidelines (WCAG) 2.1 Level AA.) 15:34:34 q? 15:34:34 … Example 2: • This publication falls below the accessibility recommendations and reports (EPUB Accessibility 1.1 and Web Accessibility Content Guidelines (WCAG) 2.1 Level A.) 15:35:32 Next example is a combination of all this information in a paragraph form. 15:36:08 GeorgeK has joined #pcg-a11y 15:36:12 q+ 15:36:25 q? 15:36:40 q+ 15:36:45 George: I think this paragraph can but generated automatically depending on the metadata provided. 15:36:49 ack cha 15:37:06 GeorgeK has joined #pcg-a11y 15:37:52 ack next 15:38:03 GeorgeK has joined #pcg-a11y 15:38:04 Charles: the date of the certification is a new concept using a new metadata / refines property. 15:38:40 gpellegrino: instead of falls below we should make this a more positive spin. 15:39:07 q? 15:39:10 ChrisOliverOttawa has joined #pcg-a11y 15:39:13 George: I used below but strugged at this. how to inform the user but its at a single WCAG-A not AA 15:39:20 q? 15:39:53 q+ 15:40:09 GeorgeK has joined #pcg-a11y 15:40:25 gpellegrino: WCAG itself states A is the minimum. that would be easy if A is our minimum. but AA meets the recommended conformance level. 15:40:45 ack next 15:40:56 gautier: minimum is a good idea as WCAG states this as well. 15:41:08 q+ 15:41:09 George: are we going in the right direction? 15:41:25 q? 15:41:34 ack next 15:42:07 Hadrien: I think its a bit much. we have implemented the previous guidelines and the conformance section is confusing for people. This publication is "Fully Accessible" (loaded term) 15:42:08 GeorgeK has joined #pcg-a11y 15:42:32 +1 to Hadrien 15:42:33 … book retailer will be difficult to display this information. Things will get lost. 15:42:35 q+ 15:42:39 q? 15:42:41 q+ 15:42:44 … too much of a massive info dump. 15:42:54 ack cha 15:43:40 ack next 15:44:08 GeorgeK has joined #pcg-a11y 15:44:21 Charles: thats where GCA / LIA certification would all would be is needed if present. 15:44:54 tzviya: What happens for those not 3rd party certified? we need something more simplified use-case 15:45:27 … something more meaningful for other publishers. I am trying to figure this out for Wiley. 15:45:30 q? 15:46:00 … lets think about how this works in the real world, asume folks don't have GCA or small publishers. easy to use. 15:46:08 GeorgeK has joined #pcg-a11y 15:46:30 q+ 15:46:33 Chris: from the Library point of view have no expertise in this area at all. We could just rely on this metadata if it meets the standard. 15:46:34 q? 15:46:46 ack next 15:47:09 q+ 15:47:14 Hadrien: When we tested this metadata we had users who didn't even know what EPUB is or what a certification program / WCAG is. could be a blocker / oppertunity. 15:47:39 … users don't know that an epub with Fixed layout you can't modify the text in the book. 15:48:07 q? 15:48:08 GeorgeK has joined #pcg-a11y 15:48:18 … we need to use this line of thinking with those who don't have this expertise. I think we can make this an opportunity. 15:48:19 ack next 15:48:50 gautier: standard accessibility conformance reached. might be something 15:49:15 AvneeshSingh: We can take this up in the editors call to flesh this out. 15:49:18 q+ 15:49:45 George: meets the recommendation or minimum recommendation. 15:50:09 GeorgeK has joined #pcg-a11y 15:50:23 q+ 15:50:36 ack next 15:50:36 … seems like what that short paragraph needs to be clear and says it either meets or doesn't meet the specification, but what about self certification vs. 3rd party. 15:51:29 tzviya: I like example 17, but I would simplify it more "This publication meets the accessibility recommendations" if there is a report link to that. 15:51:36 ack next 15:51:49 AvneeshSingh: we can create a github issue. 15:52:08 GeorgeK has joined #pcg-a11y 15:52:33 Hadrien: boils down to trust. international organizations different countries will do things a little different. may not be a one size fits all cross boarders. 15:52:54 q? 15:52:59 AvneeshSingh: these are examples and can update it as those countries see fit. 15:53:42 q? 15:54:01 George: appropriate publisher provided certification, multiple things are provided. ie. "Certification information is provided" which can then be viewed in greater detail upon request. 15:54:08 GeorgeK has joined #pcg-a11y 15:54:19 Hadrien: that info is useful when you don't trust. 15:54:36 q? 15:54:42 q+ to talk about trust 15:54:54 … if you recognize some certification program thats when it becomes more useful. could vary from publisher to publisher etc. 15:55:03 ack next 15:55:04 tzviya, you wanted to talk about trust 15:55:52 tzviya: in the world of a11y a certification report has been established. university / libraries may requires some certification. populating this metadata before it becomes a requirement. is smart 15:56:08 GeorgeK has joined #pcg-a11y 15:56:24 q? 15:56:36 George: is self certification meeting recommended standard and if that is self-certified would you say that. only put "Certified" if its 3rd party certified. 15:57:11 … agreement on meeting requirements, but do we put in "certify" if its 3rd party vs. self-certified (gets to the trust thing). 15:57:51 tzviya: I would think certify if it comes from a 3rd party, vs. something internal 15:57:56 zakim, next agendum 15:58:00 agendum 2 -- Schedule for July and August? -- taken up [from AvneeshSingh] 15:58:08 GeorgeK has joined #pcg-a11y 15:58:20 q? 15:58:43 AvneeshSingh: Should we have one more call in July? 13th of July then take a break for a month 4th week of August. 15:59:00 … next call July 13th. 15:59:28 AvneeshSingh: George you can add a github issue with the examples asking for more feedback. 15:59:59 rrsagent, make logs public 16:00:09 laurab has left #pcg-a11y 16:00:09 rrsagent, draft minutes 16:00:11 I have made the request to generate https://www.w3.org/2023/06/22-pcg-a11y-minutes.html CharlesL 16:01:22 rrsagent, make minutes 16:01:23 I have made the request to generate https://www.w3.org/2023/06/22-pcg-a11y-minutes.html AvneeshSingh 16:01:28 rrsagent, make logs public 16:01:29 thanks charles 16:01:58 zakim, bye 16:01:58 leaving. As of this point the attendees have been AvneeshSingh, GeorgeK, Makoto, gpellegrino, CharlesL, gautier, Makoto_, laurab, tzviya, mgarrish, Naomi, Hadrien 16:01:58 Zakim has left #pcg-a11y 16:02:35 CharlesL has left #pcg-a11y 16:36:00 CharlesL has joined #pcg-a11y 16:46:09 CharlesL has left #pcg-a11y