14:57:54 RRSAgent has joined #epub-fxl 14:57:58 logging to https://www.w3.org/2023/11/20-epub-fxl-irc 14:57:58 RRSAgent, make logs Public 14:57:59 please title this meeting ("meeting: ..."), gpellegrino 14:58:28 meeting: FXL TF, 20 Nov 2023 14:58:59 present+ 15:00:42 present+ 15:01:57 SimonPRH has joined #epub-fxl 15:02:07 present+ 15:02:21 jgriggs has joined #epub-fxl 15:02:29 present+ 15:02:32 CharlesL has joined #EPUB-FXL 15:02:34 CircularKen has joined #epub-fxl 15:02:38 present+ 15:02:41 present+ 15:04:07 present+ 15:04:22 JonasLillqvist has joined #epub-fxl 15:04:48 scribe+ 15:05:10 https://github.com/w3c/epub-specs/pull/2592 15:05:23 Preview: https://cdn.statically.io/gh/w3c/epub-specs/fxl-editorial-2/epub33/fxl-a11y/index.html 15:05:43 Diff: https://services.w3.org/htmldiff?doc1=https://labs.w3.org/spec-generator/%3Ftype=respec%26url=https://w3c.github.io/epub-specs/epub33/fxl-a11y/index.html&doc2=https://labs.w3.org/spec-generator/%3Ftype=respec%26url=https://cdn.statically.io/gh/w3c/epub-specs/fxl-editorial-2/epub33/fxl-a11y/index.html 15:06:45 gpellegrino: this is last Wendy proposal. Is there any comment suggestion feedback? We can take 5 bminutes to read the Legibility section which is the major improvement here. 15:09:17 q+ 15:10:53 scribe+ 15:11:12 gautierchomel: I was lost by the list of success criteria 15:11:23 ... then the list is retaken in subsections 15:11:42 ... I would prefer to have one subsession for Sussess Criteria 15:12:12 ... or we want to keep the Success Criteria together, then I would remove the first list 15:12:28 q+ 15:12:36 ack gautierchomel 15:12:40 ack SimonPRH 15:13:33 SimonPRH: I might have lost a part of the discussion related to the removing of font related considerations. 15:14:09 gpellegrino: yes, font faces are not in WCAG requirements. 15:14:53 SimonPRH: that seems to me it shpould be in fxl guidelines because we can't change the font here. 15:15:00 q+ 15:15:42 ack CharlesL 15:15:51 sueneu has joined #epub-fxl 15:16:01 present+ 15:16:39 CharlesL: proposing a font instead of another may be diplomaticaly complex 15:18:38 p+ 15:18:59 gpellegrino: maybe it could be usefull to add links to the WCAG success criteria to help the uinderstanding like it's done in 2.5.2.2. If we agree on that, shall we add that on the other sections? 15:19:28 q+ 15:19:40 ack CircularKen 15:20:08 q+ 15:20:19 CircularKen: yes, i feel that's a good idea to have link to the riules we are refering to. 15:20:37 q+ 15:20:58 gpellegrino: is someone available this week to make proposals? 15:21:10 ack CharlesL 15:21:54 CharlesL: we all know fxl has issues, are we saying that clearly here that we can't reach wcag 2.2AA? 15:22:12 q+ 15:22:22 ack sueneu 15:23:03 sueneu: i'm willing to help but I don't understand the mecanism to contribute to this document. 15:23:10 q+ 15:23:13 ack CircularKen 15:23:44 q+ 15:23:54 ack JonasLillqvist 15:24:10 CircularKen: WCAG A is achievable, not AA because of resize / reflow. 15:25:37 JonasLillqvist: most of the sections under legibility are actually not specific to fxl if you look at to visual adjustement, there yes we have specific fxl things, but not in visual design where we see things that are true for reflowable epub too. 15:25:46 ack CharlesL 15:26:36 q+ 15:26:41 ack CircularKen 15:26:43 q+ 15:28:04 q+ 15:28:28 CircularKen: the complexity of fxl layouts imposes to go deeper in graphic design best practices like legibility. Also I've understood that multiple span is a problem for screen readers is that still the case? 15:28:31 q§ 15:28:33 q+ 15:28:53 q- 15:29:48 gpellegrino: it depends on the settings of the screen reader. But problem with span is when you change text display, it breaks. We can mention span difficulties in visual more than in screen reader section. 15:30:22 gautierchomel: we had this problem on TTS in thorium for quite a while 15:30:36 ... but now it's fixed 15:31:23 q? 15:31:32 ack SimonPRH 15:32:44 q+ 15:33:14 q+ 15:33:15 ack CharlesL 15:33:40 SimonPRH: back on wcag A target, we shall not make it too central but rather referencing where it is relevant. To make sure that people still want to do the best possible work. 15:35:11 ack CircularKen 15:35:12 CharlesL: line reader changes line colors to help reading. It will break up at every tag breaking the content. They might have insights on the issues they faced. I will ask them. 15:36:09 CircularKen: we could say "AA minus reflowable". 15:37:02 s/line reader/Bee Line Reader 15:37:11 https://www.w3.org/WAI/WCAG22/quickref/?versions=2.1#reflow 15:37:18 gpellegrino: there are still open questions but technically wa can say a pdf is AA compiant (the how to guide says that a success criteria will be written for pdf), we could say the same. 15:37:20 q+ 15:38:10 Here is the website for BeeLine Reader https://www.beelinereader.com/ 15:39:10 ack gautierchomel 15:39:14 q+ 15:39:30 gautierchomel: I think we should clearly say that FXL is fixed and cannot reflow 15:39:55 ... the fact that all the rest can be AA should be underlined 15:40:12 Q+ 15:40:18 ... we should focus on what is possible and don't foul the reader 15:41:46 ... this leads again on how to add reflowable content to FXL 15:42:14 "There are ongoing discussions about transforming visual publication into reflowable textual content for complete AA compliance. Whilst these are not in production yet, by creating our fixed-layout to AA we are preparing our files in the best way for these future developments." 15:42:17 ack gpellegrino 15:42:22 ack CircularKen 15:43:16 +1 15:43:19 CircularKen: how about that line of text clarifying? 15:43:21 +1 15:43:27 +1 15:43:35 ack SimonPRH 15:43:35 +1 15:43:35 There are ongoing discussions about transforming visual publications into reflowable textual content for complete AA compliance. Whilst these are not in production yet, by creating our fixed-layout to AA where possible we are preparing our files in the best way for these future developments. 15:44:26 q+ 15:44:31 SimonPRH: this document is to say the state of the art of fxl accessibility. We should be clear in what is achievable. 15:44:45 ack gpellegrino 15:45:35 gpellegrino: what if we say per criteria how difficult it is to achieve (simple medium, complex)? 15:47:11 gautierchomel: it's a great idea, but how to achieve that without naming one or other tool? 15:48:46 gpellegrino: to resume, i see open questions : refactoring the document per success criteria? ; do we want to stay on WCAG A line base or also mention AA (i feel we are on the second) : do we have the possibility to mention a difficulty level? 15:49:17 +1 15:49:22 +1 15:49:23 +1 to merge 15:49:24 q+ 15:49:27 gpellegrino: then we have a proposal from Ken we'll summit. Is that ok for everyone if we merge the actual wendy's work 15:49:30 +1 15:49:34 ack CircularKen 15:50:31 CircularKen: there's also an open question on the font (should we mention Font again) 15:52:01 gpellegrino: ok, i'll add that to the next agenda. 15:54:45 gpellegrino: thanks, see you next week. 15:55:08 zakim, end meeting 15:55:08 As of this point the attendees have been gpellegrino, gautier, SimonPRH, jgriggs, CharlesL, CircularKen, gautierchomel, sueneu 15:55:10 RRSAgent, please draft minutes 15:55:11 I have made the request to generate https://www.w3.org/2023/11/20-epub-fxl-minutes.html Zakim 15:55:18 I am happy to have been of service, gpellegrino; please remember to excuse RRSAgent. Goodbye 15:55:18 Zakim has left #epub-fxl 15:55:31 rrsagent, make logs public 17:05:42 gautier has joined #epub-fxl