Skip to content
This repository has been archived by the owner on Apr 26, 2022. It is now read-only.

Minutes 19 October 2017

Dave Cramer edited this page Oct 19, 2017 · 1 revision

W3C Logo

Meeting: EPUB 3 CG Telco

Date: 2017-10-19

See also IRC Log

Attendees

Present: Laura Brady, Avneesh Singh, Rachel Comerford, Bill Kasdorf, John Costa, Tzviya Siegman, Dave Cramer, Garth Conroy, Brady Duga, Wolfgang Schindler, Romain Deltour, Marisa Demeglio, Tobias Fischer, Charles LaPierre, Mira Bossowska, Evan Owens

Regrets:

Chair: Rachel Comerford, Dave Cramer

Scribe(s): Tzviya Siegman

Content:


Dave Cramer: Meeting: EPUB 3 CG Telecon

1. Update from Accessibility Task Force

Dave Cramer: Avneesh sent an email summarizing. BillM is working with W3M on ISO standardization. If things progress, we will work with CG to ISO standardize EPUB A11y 1.0

2. ACE Accessibility Checker

topic: ACE Accessibility Checker

https://inclusivepublishing.org/news-and-events/news/announcing-ace-beta-release/

Dave Cramer: Beta testing has begun. You can download and install the tool to participate in beta testing. I got it working and it's pretty cool. It generates a JSON file identifying accessibility problems. I encourage all of you to test it Rachel Comerford: I have been pressuring vendors to test it as well

Romain Deltour: ACE is a tool to check conformance to EPUB Accessibility 1.0 tools. It's for power users. The tool has 2 facets. It does automated checks and data extractions. Automated checks are conservative to avoid false positives. data extraction is intended for later inspection of content. When using the tool, it's important to remember that it does only part of the job. Most things cannot be automated. There is also an HTTP install for larger workflows.

Ace's dev site: https://daisy.github.io/ace

Romain Deltour: For those not interested in the technical, there is also inclusivepublishing.org For higher-level news: https://inclusivepublishing.org and the issue tracker on GitHub: https://github.com/daisy/ace/issues Dave Cramer: any questions for avneesh or romain?

3. EPUB for Education

Rachel Comerford: I spent some time digging into existing EPUB for Ed. Especially as we discuss best practices, I think that a significant portion of the spec is just best practices. I am trying to come up with a recommendation for how we can break down this profile. Perhaps this will be best practices that differ by genre. There may be elements that should be merged with 3.1 spec. Some elements should be best practices or samples.

Dave Cramer: It seems that one of the only obvious things that would fit into the 3.1 spec is some of the metadata. Some of it might be a11y metadata, and some of it might be what type of ed material it is

Rachel Comerford: that is section 8

https://w3c.github.io/publ-cg/education/epub-education.html

https://w3c.github.io/publ-cg/education/epub-education.html#navigation

Rachel Comerford: I was also looking at section 7 about navigation and wondering if that might go into 3.1 as well. What's the best way to raise this?

Rachel Comerford:Section 8 Metadata: https://w3c.github.io/publ-cg/education/epub-education.html#publication-metadata

Dave Cramer: github issue

Dave Cramer: some of the navigation section is more best practices related (it is suggested, not MUST/SHOULD)

Tzviya Siegman: the navigation section includes some SSV terms "toc-brief". We need to know if there are other terms that need to go into an ARIA vocabulary

Rachel Comerford: where should we record that?

Tzviya Siegman: let's start recording that in the CG and bring it to the WG after tpac

Dave Cramer: does anyone know status of LTI stuff?

Tzviya Siegman: ask RickJ

4. Best Practices

Dave Cramer: One can get into a lot of trouble with EPUB. What can be done and by whom to help with best practices?

Rachel Comerford: I was looking at epub for ed spec. As i reach out to people for help, I've discovered that solutions are market-specific. I have been thinking that best practices might be an alternative to profiles. This would involve working with BISG

roles for BISG

  1. Help identify variations in market needs (higher ed versus trade, etc)
  2. Gather existing best practices documentation
  3. Identify pain points in implementation
  4. Socialize best practices documentation as it is finalized to members

garth Socializing over drinks is always fine.

Bill Kasdorf: This is on agenda for tomorrow's BISG Content Structure Committee meeting tomorrow

Evan: how generic is this best practices discussion? Is it tied to what readers will/won't support or more generic?

Rachel Comerford: I am hesitant to get into system support, especially considering how fickle they can be. I think it would be useful to say this is a best practice, but bear in mind that it won't work on X platform

Evan: This topic has come up in other groups, such as JatsML - is this a potential subset of EPUB?

Dave Cramer: I'm remembering working on BISG FXL guide. We had a broad set of guidelines, followed by systems restrictions. If we include systems, it greatly adds to the task. I am greatly interested in what the interoperable core of EPUB is. Finding out what the core is would be of great interest

Bill Kasdorf: Sometimes best practices can be about dealing with the inconsistency. How do we publish? I recommend a web-based living document, not a static document

[rachel] +1 to dynamic web publication

Tzviya Siegman: If you look successful docs we've seen in the past, the ones that have longevity don't address the fickleness of reading systems, like Matt's a11y guidelines

https://idpf.github.io/a11y-guidelines/

Tzviya Siegman ... we'll forever be updating if we deal with interop. maybe interop is a separate project

dauwhe +1

Rachel +1 to interoperability as a unique spec

Wolfgang +1

Dave Cramer: I was going to bring up Matt's a11y guide as a useful model. I wonder if we could build from that as a model, given how intertwined a11y and best practices already are

Bill Kasdorf: I recommend doing this in a modular fashion

http://kb.daisy.org/publishing/

Romain Deltour: Matt's guidelines have moved to accessibility knowledgebase. We welcome contributions to the a11y knowledgebase

https://github.com/daisy/kb

Romain Deltour: looking for reviewers and contributors, but this is not quite ready for publicizing

Dave Cramer : Everyone thinks best practices are a good idea. need volunteers

Tzviya Siegman I will help

Laura Brady I am happy to contribute and help however I can.

Rachel Comerford: I have volunteered

Laura Brady cool

Dave Cramer: next steps?

Rachel Comerford: we can pull in best practices from epub for ed

John Costa: I am happy to contribute also - based on profile work in IEEE Actionable Data Book research (interactive epub for education) we can pull in resources from http://ieee-adb.org

Tzviya Siegman: other resources to recommend?

Rachel Comerford: We can pull resources from IEEE, DAISY, Publisher specific (Macmillan), and of course the education profile