<laudrain> do we connect through GoToMeeting?

<Avneesh> it is web ex

<Avneesh> should I send details?

<laudrain> yes please, I don’t find them back...

<scribe> scribe: clapierre

<laudrain> ok, thanks for the Webex

Avneesh: WCAG Item - proposed a11y metadata in option and conformance and last week there was a con-call which passed through. Publishing metadata will be optional, we should explain. now we have to polish it, going into WCAG 2.1

george: so its optional in metadata is it under AAA ?

avneesh: it doesn't have AA or A, its not a success criteria. it is optional. because it is optional a11y metadata went into the same structure.

George: metadata does not contribute to the a11y of the page, it helps with discovery.
... does not help to consume the webpage.

Avneesh: it can go aaa or optional conformance because most of the AAA is ignored. but if it remains in the conformance metadata then it will be enforced.
... there was resistance as a SC. does not adds to a11y it tells about accessibility. so we think this is our best option to get this into 2.1

luc: discovery metadata, we use discovery ONIX to distribution channels and there is a good a11y list in oNIX, Avneesh and Graham, and it looks to me it is not easy to sync information between metadata inside the publication and onix metadata, and I don't know where we are on this, and what this means in WCAG 2.1

Avneesh: 2.1 does not go into such details, it recomends schema.org it is at the abstract level. the sync between the two should be maybe in the community group, it is more related to the publications, and WCAG is at abstract level.

Jason: epub a11y spec inovates in this area, discovery req. distingt from conformance req. to be met in publications that don't meet a11y req. arg. it is inapropriate that web developers make an a11y claim in machine readable form, but we may consider the epub approach in WCAG guidelines how the reporting requirements and discoverability req. as apposed to the a11y requirements.

Avneesh: we should have this in silver tecnnically.

Bill: ONIX issue is really important. in other direction, recall updating onix codelist to exactly align with schema.org and w3c and not sure where that went? would this be useful the way the metadata is expressed is the same ONIX, Schema, or embedded in a publication. is there any potential on editure side?

Luc: very important for us in publicaitons that EPUB 3 files build natively that are inserted in the file, but know to the public which is why we need ONIX. I am not aware / comfortable that ONIX has been aligned with this information with the epub inside, but I think I will touch base with Graham on his side ONIX this sync is OK, he doesn't see that he has to do on his side, I think this should be re-touched, I will try to talk to Gr

aham.

Bill: I know he has done a lot on ONIX / schema.org. and all that existing ONIX out there.

Luc: we should raise this in the CG Right?

Avneesh: Yes

Luc: I will mail to Dave C.

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

Avneesh: user requirements on navigation
... answers many of the questions in this issue. lets discuss

George: did you add that paragraph to wiki?

Avneesh: Yes

George: getting the idea that Reading order is important the correct reading order in an article / section and is important / consistent. Ex: caution in the side bar is a good example, not sure if the WG understands that.

Bill: wiki pros are good to have. I think that there is some confusion on trational coding/tagging when people think of navigation they think of a navdoc. but once you are in a document it is HTML markup. Just working with HTML structural semantics, with the EPUB a11y spec it just states it must use the HTML semantics correctly.
... , typically in an HTML the aside would come before the paragraph so that should be covered, but what we don't have is navigation between documents.

Avneesh: should we specify more clearly that this is more important that navigation between multiple files.

Bill: we need to spell it out.
... , I have see EPUBS with everything as a div and there were no sections, this was a major publisher, so we need to really spell it out what it means to have good semantic structure

George: many of us are thinking HTML but there are others thinking about SVG, etc…
... , that does not have inherently have good structure.

<Avneesh> #39

<Avneesh> https://github.com/w3c/wpub/issues/39

Issue #39

avneesh: I believe that the comments answers this issue #39

<Avneesh> https://github.com/w3c/wpub/issues/39

avneesh: , do all the documents in the reading order must be accessed from the TOC

george: conclusion there was that they do not.

avneesh: the default reading order then there is no need that TOC must point to all the resources

George: long chapter broken up into 3 pieces, and the next two pieces may not be referenced in the TOC Only the initial page would be referenced.

<tzviya> rrsagent make minutes

Jason: standard practice, do people want something outside the TOC not from the author, reading system could scan for them for every page etc. Just trying to know what the expectation and what the requirements are. THoses things are normal

<DanielWeck> https://github.com/w3c/publ-a11y/wiki/Description-of-Accessibility-Requirements-for-WP#navigation-and-default-reading-order

Luc: we have some comments in the issues, that even for simple publication that this should be optional or unique concept, TOC to default RO , manifest etc. as we describe the goals of these allow us to separate the different ideas,

<Avneesh> ack geoq?

George: end of part of a publication I am at the end of the DOM, and I want to go to the next chunk, and VS Bookshelf it is CTRL + PD, I think that functionality is important, I don't want to have to go back to the TOC and remember where I am and go to the next element is too combersome.

Avneesh: yes this is important.

<Avneesh> https://github.com/w3c/wpub/issues/40

issue in WCAG #40

avneesh: are we happy with this conclusion?
... , what is the relationship WCAG multiple pages and WP? reply was that multiple pages doesn't represent WP fully but this is the nearest thing in WCAG which maps. but as we move to silver we will add more requirements.

Tzviya: that issue and others I raised were not needed to resolve now, but we would just add these different sections
... , we should add a "relationship to WCAG" this is why I raised this issue to have this as a placeholder.
... , if we add a11y requirements beyond WCAG this is where we would raise this.

<Avneesh> https://github.com/w3c/wpub/issues/36

is TOC sufficient for default Reading Order

Avneesh: but if TOC can only be defined by primary reading order is this an issue.

Tzviya: we should let the WG know about this wiki page

Synchronized Multi media

<DanielWeck> https://github.com/w3c/publ-wg/wiki/Requirements-and-design-options-for-synchronized-multimedia

Daniel: Marrisa wrote this document which we will review now
... , DAISY books / EPUB 3 media overlays
... , describe why this is useful to a broader audience and the a11y needs.
... , highlight why TTS is sometimes not sufficient and there is value to Human narration, and that it can be structured navicable and cam be syncroniced with text.
... , essential requirements: 3 usecases - text with pre-recorded audio narration.
... , 2nd - prerecorded audio but no text
... , audio only books, epub 3 MO is always sync with a html doc with/without text but only structure.
... , 3rd video with text transcript. video rendered on the page and the text…
... , we haven't decided on how we will do this
... , advance Requirements - didn't make it into 3.1 MO, support for multiple granularities, sync between audio / text (word , sentence, paragraph) we could have different granularities.
... , 2nd adv. req: sign language video
... , 3rd video with descriptive audio
... , we have a list of references of existing standards or standards to be, video captioning TTML v2. SMIL 3, in Readium, media fragment URIs for start/stop fragments of audio.
... , these are exploring a11y benefits and high level use cases at this stage.

george: text / audio sync we can provide a great publication. we have a screen play and the movie of that screen play do we envision that there is a sync between the screen play and the movie, next act next scene,

Avneesh: we are focused on a11y then this can go to the WG for dicussion.

Tzviya: we should bring this to the large group. good that you have the requirements. how should we proceed since SMIL is a w3c. is this part of the WP but if this is a piece of WP then we need to figure out how to proceed and bring to large group.

Daniel: George's comment about video/screenplay, structure betwen back and forth, this would be video / text transcript, text transcript is the a11y, but could be useful in other scenarios, for Tzviya's question, we will decide if this is specific to WP, or web at large, but previous attempts to define this on the web has failed.
... , now publishing industry can push this more aggressivly, we must use the Open Web platform: readiums own implementation is all using W3C standards.
... , the sync between audio/text that is where SMILE comes in. we must decide if we wnat to promote SMIL or depart from this ,
... , this has yet ot be explored fully, I don't want to mis-represent Marrisa's views.
... , we can wait until she is able to discuss this herself.

avneesh: do we want to bring this up to the main group on monday?

George: much like HTML structure good HTML provides great a11y, not much else to add. so depending on multimedia audio, video, screen plays in WP will determine what a11y needs.

avneesh: how should we move this fwd, it requires many working groups coordination to work on this not only publishing WG.

Tzviya: I have a call with Garth / Ivan next but not sure this will make it in the agenda, but this may not be urgent to bring up yet.

Avneesh: lets give feedback to Daniel, Marrisa, and George as you point out that if done correctly there may not be any a11y requirements.
... if nothing pressing then we can skip next wednesday.
... , so no call next week, we will discuss these issues brought up in email or on the wiki
... , clarify navigation document, and give feedback on multimedia to Daniel and Marrisa.

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: (no one) Avneesh Luc George Bill_Kasdorf DanielWeck pkra Charles_LaPierre jasonjgw tzviya
Found Scribe: clapierre
Inferring ScribeNick: clapierre

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: 23 Aug 2017
Guessing minutes URL: http://www.w3.org/2017/08/23-pwg-a11y-minutes.html
People with action items: 

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