Meeting minutes
Review of PR for restructuring FXL techniques.
<AvneeshSingh> w3c/
<AvneeshSingh> w3c/
Gregorio P. provided an overview of PR 2878 and issue 2908.
… This section has generic references to various documents.
… Now we have a package metadata document, so we should place a reference to this package metadata document here.
AvneeshSingh: Charles L. can take an action item to review this section and make an appropriate decision about referencing the correct section of the package metadata document.
<gpellegrino> https://
<AvneeshSingh> w3c/
CharlesL These techniques should be in the EPUB accessibility techniques document
Charles L.: Decision: Synchronize names of this heading of EPUB Accessibility and fixed layout techniques, refer to EPUB Accessibility Techniques 1.2, and then decide whether specific guidance is needed for spreads in fixed layout techniques, while remaining technology-independent.
<AvneeshSingh> w3c/
DaleRogers: why would any xhtml doc not have a title.
… its a required element.
gpellegrino: fixed layout each page is and xhtml file and each file has to have a title.
… page 2 is page after title page usually blank or illistration.
… what do we tell the publishers what is the title of page 2 thats blank?
… title of story, what do you put for the 2nd page title.
DaleRogers: right need guidelines.
AvneeshSingh: Refer to the title section of EPUB Accessibility Techniques 1.2 and determine what specific guidance we want to provide for fixed layout techniques.
<AvneeshSingh> w3c/
Gregorio P.:… We should refer to EPUB Accessibility Techniques 1.1 because it is a stable document.
… Challenges include discussion of reading order.
… We need to determine which document will address reading order techniques.
AvneeshSingh: Do we have relevant WCAG techniques that we can link here?
Gregorio P.: Yes, EPUB Accessibility Techniques point to some WCAG guidance.
AvneeshSingh: So, we should refer to EPUB Accessibility Techniques 1.2 and it already includes links to WCAG guidance.
<AvneeshSingh> w3c/
gpellegrino: in fixed layout some tables get exported as images.
… we don't have specific things about tables in EPUB Accessibility techniques 1.1 we don't have tables have to be made as tables in HTML.
AvneeshSingh: is there a WCAG section we can point to?
gpellegrino: yes.
AvneeshSingh: We can state: Use proper HTML table markup and include a reference link to WCAG techniques.
<AvneeshSingh> w3c/
gpellegrino: sometimes you can't control the reading order and was the order when you add element to the page for authoring tools.
… may give guidance using css for visual order with z index
AvneeshSingh: stacking order problem issue with some production tools. we need to make the decision at the principal level.
… Should we have production tools specific guidance in this document, or should we consider separate document for specific production tools if community really need it?
gpellegrino: authoring tools change a lot over time.
… hard to keep up
… fair to ref. to HTML / CSS code to be generated and those tools need to adapt. this has always been our approach.
… for this case we have a section authoring the reading order which discusses CSS / HTML with things with different orders visually / programatically
DaleRogers: I agree
<AvneeshSingh> proposed: We should have production/authoring tools independent techniques in fixed layout techniques document, if there is a strong demand from community to have production tool specific guidance, then we can consider a separate document.
<gpellegrino> +1
<GeorgeK> +1
<CharlesL> +1
<DaleRogers> +1
<Jonas> +1
<gautierchomel> +1
<MiiaK> +1
RESOLUTION: We should have production/authoring tools independent techniques in fixed layout techniques document, if there is a strong demand from community to have production tool specific guidance, then we can consider a separate document.
<AvneeshSingh> w3c/
AvneeshSingh: This section is pointing to old IDPF spec.
gpellegrino: region based spec was defined 11years ago.
… especially to fixed layout, zooming in/out and combo with media overlays
… is this an active spec? is it still valid, can we reference it?
AvneeshSingh: its quite risky to reference to the IDPF page and it hasn't migrated to W3C space.
CharlesL: there is a case maybe to moving it over to W3C?
GeorgeK: I agree if we are going to ref it it should be moved over and vetted.
AvneeshSingh: do we really need it, if so we will ask Matt/Ivan to move it.
AvneeshSingh: yes lets ask Matt to review it
Review of extended descriptions explainer:
gautierchomel: I addressed all issues
… the document is fine, thorium reader is not possible in an imaging window to put something with styles.
… maybe a missunderstanding what they will display is like footnotes. ext. desc. can not be styled. can not display HTML the RS needs to rebuild the HTML, to have image desc. in separate file.
AvneeshSingh: The main objective of this document is to put forward the case to provide semantic information.
gautierchomel: maybe not keep the footnote precedent?
… not possible to implement a specific ux
gpellegrino: I think that example charles was in a separate HTML then you bring up an iframe but if the extended description in the same file this gets complicated.
… for foot notes they remove all the css but this might not be possible for extended descriptions since CSS is inter-dependant.
gpellegrino: displaying the ex. description in a popup is just one solution but could be other UI solutions.
AvneeshSingh: are we ready to invite APA to review
gautierchomel: should I close this issue or keep it open.
… good to let people know this limitation.
Charles L.: Why couldn't there be an extendedDescription CSS class for all extended descriptions? We did some successful experiments for displaying descriptions in pop-ups some years ago.
gautierchomel: there may be push back by RS wanting the same CSS for all pages not certain ones.
AvneeshSingh: footnote is just and example and we want to have the roles for extended descriptions in a similar way. we need to add to the issue.
gautierchomel: I like keeping the issue open so RS dev. point of view maybe different solutions.
GeorgeK: good to get this explainer in front of people maybe CSUN?
AvneeshSingh: I will invite Janina and Mathew.