W3C

– DRAFT –
FXL Accessibility Taskforce Meeting

02 May 2023

Attendees

Present
CircularKen, Cristina, gautier, gpellegrino, shadi, wendyreid
Regrets
-
Chair
wendyreid
Scribe
gautier

Meeting minutes

<wendyreid> date: 2023-05-02

@wendyreid: this is our last closed meeting, next will be open as a working group of the publishing community group.

CircularKen: I'll share my screen. It's about practically how to help publshers with no code tools to repond what they are asked to...
… I'm in indesign with greenlight and circularflo. I have created reading order within indesign with an extrapanel...
… I clic on one element identified on first reading order element. I clic then on an image, set it as decorative, then on another element i mark it as caption. This marks allows me to change easily reading order. It will fill the article panel for me (but article panel is not used in fxl)... This is where I was at the end of last year and presented in Frankfurt book fair... Autodefine of reading order works usually fine but in some cases I [CUT]
… the same image in one page and so I need three different descriptions...
… In that case I need to manually define reading order by regions, regions can overlap so I can get 6 elements in the reading order on one page with only one image...
… by using another of our tools, masterplan, I can get an online version of the book... Using it I propose a Simple Image Description Database (SIDD). an online simple centralised image description tool...
… I use airtable to get a clean and nice description editor. It allows us to not change the worflow with a free of charge and secure tool... It displays images extracted, allows to add short and long description, it's shareable with the team and author, allows to see the context page. Masterplan is linked to the airtable template and allows to import images descriptions back in InDesign...
… (showing result with TTS reading image alt in perfect reading order) ... you get the idea, I use region navigation to place correcly image descriptions.

@wendyreid: I like to see the worflow facilitating team work. It makes the process more usable because generally not one person does the book, it's a team work.

CharlesLapierre: as you cut the image in region, I understand the whole image is marked as decorative. I wonder how it works with screen reader (would it get the role image anunciated?)

CircularKen: description is on a region, not on image. I can share the epub so you can check the code and make tests.

JonasLillqvist: I see a field for extended description, how does it output?

CircularKen: good question, I'm not sure how to place extended descriptions in FXL. I don't know exemples.

gpellegrino: I would do a link to a non linear ressource with backlink.

CharlesLapierre: if it's an alt on a region and not on an image you could extend the alt text. But problem might be if you need strcuture in that long description.

gpellegrino: I would avoid visually hidden hack as long description are of use for more users than only screenreaders users.

CircularKen: it would be great to have a standardized way, I would like no to depend on javascript for creating popup long descriptions.

@wendyreid: it's a subject that will be easier to test in a community working group, make sure we have implementation possibles before adding it to epub spec.

CircularKen: visual to textual works in colibrio. We could re up this specification.

<CircularKen> Visual to Textual Explainer https://paper.dropbox.com/doc/Visual-to-Textual-Explainer--B3gdhXW873A4DxKF1eJFcRTAAg-Hhlb35fK3KZc5hpMbkCRz

@wendyreid: it's a perfect transition to our second subject about European Accessibility Act implementation and what in the industry we can do to help implementation.

ShadiAbou-Zahra: I think we need clarifications on mecanisms to make fxl responding to EAA (European Accessibility Act).

<CircularKen_> Colibrio https://demo.colibrio.com already has support for Region Navigation and Visual to Textual samples

@wendyreid: the text adjustement is actually not possible in fxl.

Cristina: some comment on the legislation, the Act says some kind of books (art, comics, ...) can be made accessible at the start of the art. It's usefull to understand what can be done in the state of the art.

<wendyreid> https://w3c.github.io/epub-specs/epub33/fxl-a11y/ <-- our documentation so far

@wendyreid: we could do a note on the subject.

shadi: a statement would be stronger than a note.

<Zakim> tzviya, you wanted to comment on statement

tzviya: WG publising a statement has never be tested.

shadi: I'm thinking about making sure our document is recognized by authorities. Let prepare something and see how to get recognition at a higher level (more formal)

@wendyreid: our goal is to have flexibility between CG and

shadi: we have 2 years before the entry in force. It's time to work to give publisher's a strong guidance. The earlier we get a concensus, the clearer we are, the better. We should be planning now.

Cristina: for this kind of books we have more time because publisher's already have a lot of work with reflowable books. We need to explain the state of the art, we have time for a specific standard for fxl.

Minutes manually created (not a transcript), formatted by scribe.perl version 210 (Wed Jan 11 19:21:32 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: gautier

Maybe present: @wendyreid, CharlesLapierre, JonasLillqvist, ShadiAbou-Zahra, tzviya

All speakers: @wendyreid, CharlesLapierre, CircularKen, Cristina, gpellegrino, JonasLillqvist, shadi, ShadiAbou-Zahra, tzviya

Active on IRC: CircularKen, CircularKen_, Cristina, gautier, gpellegrino, shadi, tzviya, wendyreid