– DRAFT –
FXL TF, 4 Dec 2023

<gautierchomel> present§

<gautierchomel> https://www.w3.org/WAI/EO/wiki/Minute_Taking_Tips

First item in agenda to discuss content of current document. Has not been updated yet. Waiting for Wendy. Would like to recap last weeks discussion

If time discussion of switiching ot reflowable and reversable

<gpellegrino> * What level of WCAG to base the document on?

on last call we agreed to base document on WCAG level A and all the criteria from AA that is possible

<gpellegrino> * Reorganize the whole document based on the WCAG Success Criteria?

We agreed to reorganize doc based on groups of success criteria. Starting with these groups and adding what is tricky in FXL and maybe having index at end

<gpellegrino> * Find a way to indicate how difficult it may be for an EPUB Creator without extensive code knowledge to be able to satisfy a Success Criteria?

<gpellegrino> https://www.w3.org/WAI/GL/wiki/WCAG_2.x_Priority_levels_discussion

We had some discussion, but did not arrive to resolution. To integrate it with outside supplier is tricky and this is hard to express. There is a doc linked about where similar work was done

This includes information if it is easy or not. Easy is something that can be done without too much effort. out of Success criteria that includes 40 hours of training

<gpellegrino> * Reinsert a section on font-face choices?

We agreed that this should not adjust to one font face to another, but maybe include info on how font-face influences readablitiy. and a note about how to embed font faces

<gpellegrino> * Is the use of multiple spans disruptive to assistive technologies?

Charles reached out to eline reader. It is not disruptive to TTS. Clean code practice is still best practice. It can impact re-sizing font and font can overlap when resized

Hadrien: found example of organization makes FXL to reflowable. Found another example. When you have FXL and you have a side panel that displays extracted text similar to reflowable

<CircularKen> @hadrien can you spell or provide a link please to that frenhc compnay

We should consider inviting companies to explain how they do this and why. It is a bit outside of what we do, but could be beneficial

<gpellegrino> storyplayr.com

<CircularKen> thanks (my internet connection is patchy today, sorry)

<gpellegrino> https://www.storyplayr.com/en/histoire/hansel-et-gretel/playr?p=1

Hadrien: Mobidys is in interactive epub, not sure about Storyplayr. Believes it is feasible with normal EOUB. Using epub with media overlays.

Gregorio: looks similar to apporach to PDF. There is spec for standardization of PDF and some rules can me changes to reflowable.

<CircularKen> does it depend on reading order ste in FXL?

Hardien: Readium does the same. Also works for Alt-text. It has been available sometime on mobile and reading web. Going to be stable soon. It is same code we use for TTS and works best with reflowable. Use for reflowable PDF and FXL

<CircularKen> *set*

Hadrien: Reading Order is extremely important and surrounding tags is also important.

Hadrien: in this case it is closer to screenreader than OCR approach.

Gregorio: Thinking htis approach is helpful for HTML FXL and may need some changes for SVGs and wont work for roster images (eg PDF) OCR approach may work as a starting point for those

Gregorio: user can read the same content or see the same content in FXL layout and reflowable in all adaptations. Tricky part is if user wants to use a note or highlight this would be difficult to sync. Even only in read mode it would be a great step forward

Hadrien: not necessiarliy impossible to do. The way it is done in Readium it is possible, not perfect.

Gregorio: storyplayr example with one side is book and one side is the reflowable that you can change

Ken: thinks is it good, but is is worried about how the code is arranged.

Ken: whenever you see a demo as shown, it is a demo document created. We need other examples to test it properly. Does like the idea, and has suggested for some time. It is mainly getting the document in order.

Gregorio: has included Ken's request to highlight this important.

Hadrien: this is not a demo. it is a production website with a few thousand books to sell. It does mean they curated the content. But will well documented accessibility metadata you can easily select a good text.

Hadrien: imagine reading environment with proper a11y metadata is set then the readr knows they can use these readers. General comment, FXL is not compatiable with reflowable. Not possible to transfer FXL into something it is not, but is option to do side by side, panel by panel, or a equivilant option.

Hadrien: media-overlay is similar to this idea. Both options will be necessary to help solve FXL issue

Jonas: comment on document. Noticed in paragraph 2.1 Consideratsions for FXL development. The doc does not go into SVG on the document side, only more on reading system part. Either edit paragraph, or go into more about different ways to build content

Gregorio: That sentence in question was written in begining, moved HTML code into another doc, agreed this sentence is not addressed. We should better write about other techniques (SVG and roster images in spin). Should include what is achievable based on what technique creater uses

Jonas: in FInland, HMTL doc in spin but only image on page.

Gregorio: Hadrien has mentioned the same thing