Meeting minutes
Continue refinement of FXL accessibility documents.
Avneesh Singh: Continuing the refinement of the FXL document.
<Avneesh Singh> PR: w3c/
Gregorio P.: Wendy created this PR.
Gregorio P.: The PR touches the FXL accessibility document and techniques.
… related to two issues.
… moving discovery metadata to the techniques section.
… addressing other missing accessibility hazards in examples.
… from myself and Charles.
… Wendy made changes; I identified two issues to be fixed.
… the techniques document uses manifest fallbacks, which are currently under discovery metadata, but that is not the correct section for fallbacks.
… second point: metadata references WCAG 2.1 and should be updated to 2.2.
… then we can merge once fixed.
… I was not one of the original reviewers.
Charles L.: I agree with the comments.
… not sure about the fallbacks, but okay with the WCAG 2.2 update.
Jonas Lillqvist: I have a comment about the metadata examples: there is an example about accessibility metadata for children's books with media overlays.
… it lists "auditory" as an access mode, which is not aligned with the new best practices defined in the metadata authoring guide.
… the same applies to access mode sufficient.
Avneesh Singh: Do we want to go into details now, or merge first and address small fixes afterward?
George K.: I understand the issues with "auditory" for access mode and access mode sufficient. I think it depends on how much the media overlays cover the full text of the book.
Jonas Lillqvist: Yes, I agree, but in Matt's proposal for the metadata authoring guide I saw a different suggestion.
… but I agree we should not go too deep into details right now.
Ken Jones: For children's books, you would expect many images, so media overlays could cover both image descriptions and text.
Charles L.: I think we need Matt to discuss these points.
… in the PR there is also a comment from Susan about linking to EPUB 3.4.
… I think we can merge the document and create separate issues for Gregorio's comments.
Gregorio P.: Fine with me.
Wendy Reid: I agree with the comments.
… but it may be simpler to merge and then create a separate issue and PR.
… I would leave references to EPUB 3.3 for now.
… since the goal is to publish this document soon.
Avneesh Singh: With a new document, we may have additional points to discuss.
Issue 2968: WCAG 3.2.3 Consistent Navigation in reflowable EPUB?
<Avneesh Singh> w3c/
Gregorio P.: Some success criteria are difficult to map to the EPUB context.
In Accessibility 1.1 and 1.2 we have clarifications on WCAG in EPUB, which differs from web pages, although the content is expected to conform to WCAG.
… SC 3.2.3 (Consistent Navigation) states that navigation mechanisms repeated across multiple pages should appear in the same order unless changed by the user. This includes skip controls, menus, submenus, headers, footers, and page numbering.
… this is difficult to interpret for reflowable EPUB. If there is no navigation other than the TOC, this SC may pass without additional checks.
… this warrants further discussion; perhaps we should draft text and request feedback from the Accessibility Guidelines (AG) group. Publishers may struggle with this SC.
Wendy Reid: I think this is a success criterion where the reading system plays an important role.
… the EPUB creator must do their part.
… mainly ensuring the TOC and spine are properly structured.
… then it becomes the responsibility of the reading system to ensure the SC is met.
Charles L.: Yes, the page list is another way to achieve this.
… the same applies to lists of tables and figures.
George K.: I agree that the spine and navigation document fulfill the requirements.
… we should not push publishers to add content that is not present in the book (e.g., indexes).
Avneesh Singh: Some clarification would be helpful.
Gregorio P.: Looking at the current document, there are references to multiple approaches.
… something could be added in the techniques.
… there is currently no mention of this specific criterion.
… 1.3.2 (Reading Order) is particularly relevant, especially for FXL.
… 2.4.5 (Multiple Ways) is covered, but nothing for SC 3.2.3; adding a paragraph may be useful.
… Makoto may identify additional WCAG criteria that are not applicable (e.g., Accessible Authentication), which are outside EPUB scope.
Charles L.: I think Matt has already done some work for SMART.
… we can review that work to identify SC that do not apply.
… I can compile that list.
I have updated the issue title: WCAG Success Criteria That Don't Apply to EPUB #2968.
<Wendy Reid> The PR has also been merged :)