Meeting minutes
<wendyreid> date: 2024-01-15
<wendyreid> w3c/
<wendyreid> w3c/
Wendy: Start with reading systems. Link above is preview in more comfortable reading mode
Wendy: cleaned up grammar documents, and made some section decisions. Biggest one is not to mention reflow because it is still experimental and this doc is meant for publishers now
Wendy: wants to talk about fall backs, but wants a better way to word it. They need to be handled iwth attention. Looking for input
Gautier: is fine with what Wendy has done. Agrees for more feedback on multiple renditions. Not important to have there now ...
we have started describing it, and can build on later. Would really love more feedback on this section ...
maybe push question into community group so more people can discuss...
one point to include. Do not present three levels of WCGAG...
Wendy: Agree to send back to community. Had discussion on metadata side of reading system. Included with content. Retailer does not provide. Is there room for some discussion on what reading systems augment metadata with ...
it is all good it the book supports a11y, but how does the reading system provide this info, and how can there be a warning/notification what features are supported or well supported
<gpellegrino> w3c/
Gregorio: UX guidelines talks about metadata. Link above ...
we can add this. Task force is working on how to displaying info about book through ONIX ....
And also working on what is feasible with reading system....
example font size can be changed in book but not with reading system ...
working on reading system can actually tell you what the reading system can or can not do ....
UX with specific app you can add discription on what is actually available to the reading through the reading system
Gautier: Metadata will be controlled through distrbutors through contracts by some, and others will be through only through publishers ...
maybe the missing paragraph, can push it into community so we can get feedback on this warning about metadata
Wendy: with warning. Is okay with Reading Order, but TTS is not actually supported on web let alone on reading system. Does not want to necessarily tie a metadata warning to something not supported
Wendy: be carefule with what to include
Gregorio: in UX have guide enable no visual reading (includes things such as reading order) maybe refer to that without refering to WCGAG
Wendy: agrees
Wendy: any other comments? Will change this today ....
other thing is fallbacks, not sure how to do this, maybe link to other doc and mention to be mindful of how to use
Gautier: the point of fallback is mainly to say dont use unless you really know what you are doing ...
has seen EPUB with fallbacks is does not always work with reading system, and do not use fallback unless it is formatted properly for the support.
Wendy: that is how we have worded this for the spine
Jonas: Under Enable Fixed Layout display. Phrase about images in preview on paragraph 5.3.5. To him it sounds like there are multiple images used
Jonas: maybe change phrase to "contains" to be more clear. Some FXL EPUBS are really only composed of images.
Susan: has seen FXL composed of multiple images and texts. link rather than image link to view port of whole page and that the whole page needs to be visible rather than just image.
Wendy: was this about being about to isolate images?
Gregorio: Yes, when you double tap on image you can zoom in it. The idea behind is similar
Gautier: Yes it is. Many situations it will allow to zoom on portions of image.
Susan: It is not about seeing whole page, but seeing each image. Maybe FXL pages generally "include" one or two images, and can see full page on full screen
Wendy: will make this change
Gautier: Is this a good way to use the reflowable part as an issue?
Wendy: best way to comment on PR if related to PR itself.
Gautier: will ask for more comments on this point.
Wendy: Move to Media Overlay section. See link of preview above. Thank you Gautier for generating
Wendy: did not change very much at all. Wants to go back and clean up some up some of the references. Only other change so far maybe making sections about video, audio only etc more clear
Jonas: Speaks more about Reading System more than publication. When it says users must be able automatically skippable content, and all skippable structures be identified, and all users can escape. For him the skipping and escaping is part of the reading system, the markup for these is part of the publication
Jonas: should this be in this section for reading system?
Gautier: found nothing about skippablility. Regular question, can you add skip tags to skippability? We cant skip anything else what is skip tagged (like secondary content) ....
the only skippable elements are asides and it is easy for the publishers to add this that only one part is skipped
Gautier: have found not clear document citing this on the web ....
if any one has a clear doucment on skippable content, please share ....
<gpellegrino> https://
Skipped only works when the FXL has media overlays
Gregorio: see spec above, this is takes about specs for skippable and escape for multiple mark up. This is what our section is referring to, what to skip in media overlay, not inn TTS
Wendy: only type tied into epubtype and not epub ARIA ....
How many EPUBS are effectively using skippabilyt and escapability? Most media overlay seen are childrens books, would like to see more
Susan: Researched this. If this is something we want to address if it is not used as much? Do we need this right now?
Jonas: only ones using are the special libraries currently
Gregorio: from historical view this all comes from digital talking book from DAISY. Audio only and video only are digital talking books that are tranformed in EPUB. Mostly in libraries. Makes no sense in FXL world...
If in FXL there is a table, and when using media overlays, the user should be able to exit the table and move to next content. It is very important for all cases for non Fiction in media overlays ...
fiction is more edge case. Non fiction is important on the reader side.
Wendy: this is mentioned in TTS but maybe no one had defined TTS behavior, but no clear what it can and can not do. No clear definitions...
got a question today about a line break tag on FXL and if it will impact readability, probably not, but unknown as there is no info (for example)
Gautier: the readers of what we can skip. with screenreader is adding symantics, we do not do this ...
we have readers who do want more semantical access to more semantics. we need a better definition on what is skippable and what can and cant be done
Susan: in her experience readers ignore line break and need a visual for TTS.
Wendy: looking info for how screenreaders determine different levels of verbosity
Gautier: good question to ask wider group. Why is this not speficied?
Jonas: back to document about sych playback. Skimming and desired information. This section is a bit off topic, main point is escaping here. Does not know what skimming and locating elements have to do with synced audio
Jonas: last paragraph in section. Has hard time understanding this part without goign to source. It is about the issue of having audio for the navigation document, maybe make this more concise.
Susan: has colleague who makes children's books in media overlay, wants to share this with him but can't come to meetings.
Wendy: yes, documentation is public and can make comments.
Wendy: will make editorial fixes, clarify skip and escapablility. Maybe things that client needs to do, but the reading system has to make it clear there is a set of behaviours to be accounted for.
Wendy: will make changes this week and will have a draft that people can review and make comments and then start working on techniques side
Gautier: will be gone next few meetings, but will be keeping up on minutes
Wendy: January 29 no meeting, will meet next week, and again in February