Meeting minutes
date: 2023-08-08
https://
@Wendyreid: let's talk about the document we started
gautier: Added some comments on issue 60, the list of solutions we have discussed, not sure if this is the right place for it.
… I think this should happen in the issue tracker, but nothing is updating there, so I moved it here
… want more than my insight
… it's at the very end of the document
gautier: Fallbacks and Hybrid EPUBs, but we should add more information on any of the listed methods
… feel free to add to it
@wendyreid: i would like to see discussions in the issue.
gautier: I can comment a bit more on the methods
… I'm pretty sure it's crucial for us at EDRLab, depending on the method that's adopted, we'll need to decide how it looks in the reading system
… I'm thinking that we may end up with different methods, depending on the type of book published
… we'll see quick solutions, some that will be implemented, but others that need more time
… French Publishers Association, fallbacks are working, but no switch
… if the reading system accepts FXL, there is no means to display reflowable content
… so fallbacks are already used for other content, like audio, but they don't have a display
… but I'm not sure if it's a good option to have a fallback switch in a reading system
… the next one is the hybrid solution
… Vincent Gros from Hachette presented on this, they're already trying it
… seeing what happens in the market
… two main solutions out there today
… only thing missing for an experience is a switch of some kinds
… the other solutions are more technically advanced, which will take more time to implement
gautier: JS in files is possible, but it's quite challenging
… seen some demos
… can see different images or layouts
… people complain about making it work in any reading system
Naomi: that's what we do, JS on files and we just accept that some reatilers and RS don't accept it. It's not ideal.
@wendyreid: background on JS in epub: security and privaty review of W3C process runs flags. A lot of poor scripts complexify the job of RS rendering. CSS interactivity is now a much better option. Also, is JS really viable in an accessibility perspective?
Naomi: it's interesting way of moving forward.
gautier: One issue I hear when I listen to Naomi, training, how do we teach publishers to do this
… in house workflows already work, existing code already works, making changes to that is challenging
… that's what I see as a challenge with adding reflow into FXL too
… one responsibility we have is recommending things for now, and for the future
… what will people learn as they begin producing new books
… new technologies into the future
Naomi: yes, also about tool developement. Testing takes a lot of time. From our perspective, we should set up a limited set of property tested and validated. Content still need to be available without for exemple css animations.
@wendyreid: i agree we should test everything we recommand. Also WCAG always goes on top of our recomandations. W3C recommandation request for everything to be testable.
Naomi: we need the retailers to do testing too.
@wendyreid: I would add, if things do'n exist we can make that happen because inside w3c we have css wg and a lot of wg.
CharlesL: back in the nineteen working with diagram center, we used javascript to display extended descriptions in movable popups. I wonder how this could be done in CSS (presenting examples on the shared screen)
@wendyreid: I hope that CSS might look less scray than JS for some people.
@wendyreid: would anyone want to take the task of experimenting with CSS?
<CharlesL> I will be at TPAC
@wendyreid: PCG will meet in TPAC.
I will too :)