Meeting minutes
<wendyreid> date: 2023-12-18
<wendyreid> w3c/
<wendyreid> https://
wendyreid: this is a pull request with the changes discussed during last call.
<wendyreid> w3c/
wendyreid: about the restructuring, I'm not sure I want to restructure exactly like wcag but i'm open to discussion.
gpellegrino: the structure is fine for me, we may just find a way to add which wcag criteria is not achievable. Maybe a specific section about what's missing.
sue-neu: I agree with a need to say clearly what's not achievable even if i understand it may become an excuse to not do more work. Also on another subject idnk if we want to include informations about media when they are non text replacement.
wendyreid: one section about limits of fxl accessibility looks a good way to me, so we have one list in one place and not pieces in different places. Maybe a note too about what does not apply to fxl.
gpellegrino: my first approach was to have the wcag list and past our texts in there but I like the idea of having wcag vocabulary (perceivable, operable, etc.) in each of our sections.
wendyreid: ok, I'll play with that idea and make a proposal.
gpellegrino: thinking this way may help us identify missings in the document.
wendyreid: most of the discussions we had where about HTML, but we know that fxl can be SVG or even Image only.
CircularKen: sorry, i'm returning to the precedent discussion, structuring like wcag seems to me far away from publishers vocabulary, hard to read and advise, it's inaccessible language to me, I would prefer to stick with the actual structure wich i find much more understandable from a publisher point of view.
gautierchomel: I'm wondering if one way we could think about would be to start with how the requirements translate into accessibility metadata, how they would appear on a bookseller's site
… it might be part of the discussion
… why are we talking about navigation? This is how it translates to metadata and user needs
wendyreid: ok, thanks for those additions. Let's talk about SVG and Image based contents.
<CharlesL> +1 to adding a note about images in spine not being accessible.
gpellegrino: I know that SVG can be made accessible the same way as HTML, with aria tags, etc. Maybe we can just say that what we are saying applies to SVG and HTML. Images in spine, we can add a big note saying it is very limited in accessibility.
gpellegrino: maybe a word about fallback too.
CircularKen: SVG is a mystery to me, who does that? and how?
SimonPRH: we did that at PRH :)
Hadrien: I've seen manga or comics where the draw is a bimap in svg and the bubble text are as SVG and a bit of everything. The reality is that larges collections exist this way. Eventually not displayed in epub reading system but in webviews or content specific RS.
<CircularKen> @gautier Simon said at PRH it was only a image format as part of a page e.g. a logo. not used for page layout
gpellegrino: I also see SVG fxl from PDF conversion workflows.
Hadrien: maybe it's an issue ti diuscuss in community Group,
jgriggs_prh: we used svg for text layout like in children books. it could be usefull for publishers to have some usecases axplored.
sue-neu: thinking about the public, for publishers this document is very technical.
gpellegrino: I think we need a very technical start (this document) to be able to do a simplified version later. This document is good to be complex, as it helps us find a technical consensus.
wendyreid: I would like to make it more readable but yes the subject is technic.
SimonPRH: vulgarisation will have to be done for publishers who don't have technical teams.
wendyreid: the word "publishers" is a very large umbrella, with large diversity of profiles.
DRogers_: As i have a background of webdesigner, I remember the browser war and to me our suggestions must be valid for RS to be of use.
wendyreid: RS are mainly build upon browser engines.
Hadrien: for comics, in japan and corea, digital sale are superiors to print sales. They use RS not based on browser engines. We shall extend our view to the whole world.
CircularKen: We can add a note saying that we focus on EPUB and XHTML but that other formats exist and may benefit from this guidelines.
gautierchomel: I found an accessibility features in SVG note, but it's from 2000, something more recent might be out there?
… that might be the way to proceed
… point to external resources
<gpellegrino> +1 to limit the scope to HTML, stating it in the introduction
gautierchomel: it would be good to have more up to date reference documents
gpellegrino: on SVG we can ask Ivan.
wendyreid: yes, and the wcag group too.