George will scribe.

<Avneesh> https://github.com/w3c/publ-a11y/wiki/Description-of-Accessibility-Requirements-for-WP

Navigation requirements is the first topic

We are at a higher level and not getting into the details.

Reading order and navigation are clarified in the wiki.

Tzviya, we can just put a placeholder for first draft and fine to point to the wiki. Alternatively we can open an issue or point to an existing.

It is too soon to get into this level of detail. We should wait.

Avneesh, if we can wait and provide guidelines.

What are the main issues.

Should we go into detail or wait.

<rdeltour> +1 on waiting

The group agrees that we should wait rather than go into detail.

Action item is to create an issue in the tracker and point to the issue tracker to keep a place holder.

<BenSchroeter> George: presentations need to be in by )ct. 3. Not seen an extension yet. Rachel has sent us a proposal that we could do on Publishing @W3C. Judy has not responded yet. Call later today. CSUN presentation things on the agenda.

<BenSchroeter> Goerge: we are talking about overview of publishing at W3C including merger of IDPF and W3C, and EPUB.

<BenSchroeter> recommend that this session be given early in the conference, to provide background for other sessions.

<BenSchroeter> Goerge: other sessions may be on reading systems (epubtest.org) and we may see individual companies like Dolphin and Vitalsource present. VST might present on ecosystem. Also theme of conformance and DAISY ACE accessibility checker, which will be released by that time. Benetech will likely present on A11y certification.

<BenSchroeter> Goerge: need for DSS offices to be advocated for EPUB insteadf of afraid of it.

<BenSchroeter> DSS offices should encourage EPUB and become familiar with reading systems that support it.

<BenSchroeter> Gorge: short window to put this stuff together.

Avneesh, the publishing at W3C is the first session that sets the stage.

List of people we have to do this, from our other notes.

The peoople working on the presentation will put together the draft.

<BenSchroeter> Avneesh: first draft of proposal should be sent to this group for feedback.

The group can comment on the proposal.

TPAC

One session with WCAG for the road map.

What about synced media?

The primary purpose in bringing up the topic is to gague interest.

What group do we go to for that?

Ivan suggested annimations.

Romain, the interest is to borrow brains. The difficult part is who to engague with.

It is interesting to gather people to discuss this issue. What about the wednesday?

What about TV?

Concept sessions may be a good way and we should connect with Ivan on the right approach.

Daniel the technology we envision for synced media is probably going to enable audio books.

There were questions about chapters on the list.

Discussion about chapter, metadata.

Metadata may be required to describe any part of a book.

Deborah step from the word chapter. All publications have two types of segmentation.

There are files and there parts of the publication. All publications are subject to segmentation. This is different from the files.

<clapierre> +1 to Deborah's comments

The metadata describes the logical parts of a publication.

. Metadataat the publication level happy to go back to media overlays and define what we mean

is October 11.isNext call

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Avneesh tzviya George Bill_Kasdorf Luc dkaplan3 BenSchroeter Daniel_Weck jasonjgw clapierre
No ScribeNick specified.  Guessing ScribeNick: George
Inferring Scribes: George

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 27 Sep 2017
Guessing minutes URL: http://www.w3.org/2017/09/27-pwg-a11y-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report