Meeting minutes
Profile
Hadrien Gardeur: epub for comics. 1 bitmat per page.
… handled through conventions. how to author comics in Japan. receivers of those files they would have a good way to extract the bitmaps.
… another way fallbacks, we have seen comics in the spine, 1 html per page with fallback to a bitmap. If you know about that you can extract the bitmaps
… , or scrolled comics could be possible images in spine.
… there are RS content aggregators that need bitmaps but knowing different things or inspecting the files. but if we had a way to say this is a comic. Pre-paginated comics could get a bitmap per page, and scrolled would be a bitmap per tile.
… in Japan there could be some proprietary file formats.
… better to discuss together to discuss here and address.
Shinya Takami: we use a style HTML in spine each html is an image.
… image in spine with fallback, we plan to update BP?? version same html in spine for last 10 years
… image in spine extract images, we propose a solution however W3C its not good for a11y.
… we need to consider a11y
Hadrien Gardeur: Happy to bring up a11y for comics in a future call because the current solution does not work.
… sometimes you go back and forth between pages.
… may not be on a single bitmap or page
… a single description alt text wont be enough and doesn't meet EAA regs.
… we need to make those specialize RS / aggregators better.
… EPUB is a mediocre option for comics currently
Shinya Takami: we should move a11y to a future call. in Japan we had a discussion about a11y for Manga
… result was it is very difficult to create text / scripts for a11y.
… we discussed alternative approaches for Manga, audio book version we could link to those. we don't have a dedicated spec for that type of content.
… last year Hadrien proposed text for a11y for Manga but publishers difficult to prepare for a11y content.
<Shinya Takami> q>?
Brady Duga: images in spine without a fallback it is not making images accessible. other content like inaccessible children's books.
… are we opening a door to allow to ignore a11y.
… it would be a hard sell to just have images in spine, this is true for comics.
Hadrien Gardeur: this door was already open with fixed layout.
… even if they could add alt text they don't.
… a children's book could be made accessible. a regulator could go against a publisher since there is a technical way to make it accessible.
… understand your concerns about that including cost etc. EAA if the cost is too much there is an exemption for that.
… it is understandable although disappointing that comics are accessible.
… first step a11y comics to specialized organization could adapt and make comics accessible. and depending on cost then the publisher can adapt and make the content born accessible.
Shinya Takami: who can provide the text for Manga, authors can not prepare the correct text always.
Hadrien Gardeur: when you do an adaptation its not the author who is doing that work.
Dale Rogers: from a11y pov Hadrien says no real a11y tools, what level of a11y you are talking about. If I create a comic putting in alt on an image describing the images completely accessible? having something in the spine / fallback a lot has to do with production / time to create an asset and sell it and if using HTML or not / adding a11y in or not it takes more time than the publisher is willing to do that and ROI is worth it.
Hadrien Gardeur: we can't solve the problem with the current spec and alt text is not the answer either. you need to a11y for blind but also dyslexic user with text in visuals they may understand the image but they need the the ability to tweak how the text is presented / highlighted while speaking it with read aloud. Its wrong to produce fully accessible comics with the current spec and this needs to be addressed.
Hadrien Gardeur: is it necessary to have a Profile, prepaginated content the approach used today 1 html per page fallback 1 bitmap does sorta works if you know about it and it is not idea.
Laurent Le Meur: What do you expect a profile, it will be a burden for publishers and may not be there and what would the RS do / expectations and if they see comic as a profile. I don't see the adv.
Hadrien Gardeur: take Kobo: when they have a FXL they open all FXL images and they wouldn't need to guess, and you clearly say this is a comic.
… do you need a metadata that you conform to this profile or is the presence of images in the spine or not.
… could change how RS / aggregators would be able to use this.
Shinya Takami: in Japan all fixed layout tile in spine 1 image even if the content is not only Manga. prepaginated has same structure for RS to detect.
Hadrien Gardeur: you created a convention. not something official to be shared with the rest of the world.
… what if new version of profile is not only in Japan but from this WG we could make this global that the industry will adopt. and be a great step forward.
Shinya Takami: not easy to move to a global profile than Japanese style. We have a big Manga movement which is different than global needs.
Hadrien Gardeur: moving to anything new is painful. we get that. if Japanese is involved it is a good thing and there is a lot of content using your old ways.
Shinya Takami: I have reservations between global vs. Japanese needs.
Shinya Takami: only a few major publishers from Japan has joined the W3C
Hadrien Gardeur: what about a CG?
Shinya Takami: it is difficult for us to speak English and participate and express our views/ concerns / needs.
Hadrien Gardeur: if we did this 1:1 with a translator might help?
… Myself / LaurentLM will be in Japan and in Kobo / Tokyo for a good part of time in November and can meet with publishers directly.
Laurent Le Meur: Library for the Blind it would be great to speak to publishers directly while we are in Japan.
Laurent Le Meur: I do understand the need for a profile. but if we allow images in spine this requires specific handling from RS and not sure why we need this extra metadata.
Hadrien Gardeur: lot of content html in spine with images as a fallback, if we come up with images in spine or fallback to image we could have this documented we could validate against that profile. retroactively to fit the profile even without the extra metadata. we could also recognize other metadata to recognize this specific metadata in Japan, this could help RS to leverage this.
Brady Duga: not clear with the profile is telling me. 1 this is a comic and 2 there are performance tricks that could be used since the content is structured in a specific way.
… in playbooks there is a comics play mode, by looking at age, format, type etc. dedicated kids reader, is this for kids/comics and will send it to an appropriate reader.
… could take advantage of rendering or is it telling me just this is a comic.
Hadrien Gardeur: taking the guess work out is the major win. I agree there is a question if we are only targeting comics or content with images.
… we could prepossess when you know you have a Bitmap, I see pros/cons for both. limiting to comic but other content could benefit from it, but could be a con to cover kids book
Dale Rogers: Sue has talked about, ch 1 reflowable, ch 2 is fixed layout so when I hear this wondering if the usecase this is only for complete cover to end all that exists is images.
… Kindle create had issues which kept rejecting but KDP wont accept it because the so many images you must make it into a comic book and had to make the reflowable content into a PDF. Thorium/Readium could open it but KDP couldn't handle this.
… in real world if I knew about what the Japanese RS needed then I could maybe tap into that market.
… if we said this profile is comic does that mean we can't have any reflowable content in there.
… in my spine say this is an image, this is reflow, this is an image etc.
Hadrien Gardeur: Yes cover to cover is a bitmap.
… guess work is problematic, which you saw this KDP had to guess what your content was.
… your EPUB could be treated different ways because of the guess work. Good example of why we need this.
… spine overrides does allow in the spec but not widely supported.
… trap we have in the spec where we document ways but in practice (18 years) won't work.
… I think its a risk having this in the spec which is not really supported.