ack[s] avneesh

ack[s] Avneesh[speaker]

[chair] ack[s] next[speaker]

bye

Zakim: scribe Avneesh

scribe Avneesh

<scribe> scribe: Avneesh

Avneesh minute-taker

[please] help

<tzviya> scribenick: Tzviya

<laudrain> scribenick: laudrain

Avneesh: 4 topics, equal time
... 1. Update on WCAG
... background

WCAG 2.1 incermental relaese

scribe: rtry to add aas much as possible
... biggest place is a11Y metadata
... logical order
... multiple ways of nav, page number, techniques for it
... in the same state of 111Y technique IDPF

issues: deeply nested heading, escapabilitty if text and in audio, prononciation lexicon

George: we know what we can have in 2.1, and then continue
... we should have the requirement into ???

Tzviya: make sure that any docuement from DPUB is not the same from this group
... review that docs, with new people in the group

<tzviya> http://w3c.github.io/dpub-accessibility

Tzviya: see note and review with the larger PWG

<tzviya> https://lists.w3.org/Archives/Public/w3c-wai-ig/2017JulSep/0026.html

Tzviya: headings and iFrame : WCAG doesn’t address heading requirements

Avneesh: big picture : put the requiremnt to PWG and WCAG

Tzviya: put notes together in a wiki

<tzviya> final version of DPUB note: https://www.w3.org/TR/dpub-accessibility/

George: cnnaot be reuqiremtn in Publishing?
... If it cannot go to WCAG?

Avneesh: this group write with the same structure as WCAG
... collaboraiton PWG ans WAI
... what do we want to accomplish?
... what we want to add to ARIA, to WCAG

George: nested heading not WCAG, put in Pub?

More stringent in Pub than in general Web?

Avneesh: be modular
... tioday, what is the scope of this docuemtn?

Tzviya: not a formal docuemetn, oon a wiki
... refreshed regularly

Avneesh: it will mature as a workgroup note

Matt: make sure the WP is accessible, may feed technique on going

Avneesh: start inmmediately on this doc

+1

George: hard core req difficult to put forward, but with SHOULD, as company accomplish the best as possible

Avneesh: let’s put the high level req
... within this group

Charles: agreee wiki approach
... list of SHOULD or MAY, pu MUST in the publishing side of it

Avneesh: Start in conceptuel form, and put technqiue with PWG spec

BillK: recommandation differ from WP/PWP/EPUB4
... more stringent for EPUB

Tzviya: first draft as a struture, and fills gaps afterwards

Avneesh: peinciples are the same even if techniques differ

George: more req difficult to address if it doesn’t exist in WP

2. Horizontal review

Avneesh: check list from first draft
... comments?

<Avneesh> http://w3c.github.io/apa/fast/checklist.html

Tzviya: not a formal hor rev, keep an eye on ways to accomplish thing not accessible

Matt: need to ne involved in discussions
... s/ ne / be /

Avneesh: put an a11y label in GH?

Tzviya: Gh is now chaos
... more smaller issues easier to understand
... the name of the issue should alert on a11y

Avneesh: nav doc discussion, a11y don’t come in
... navigation shoudl be provided by the UA

Matt: we need clarity on req for the UA

Tzviya: philsophical questions not in GH, but in call

Avneesh: what it means to make things accessible for a UA?
... make that this is undertood, not only technology

3. Assign group members for acting as liaison with other W3C groups

Avneesh: WCAG: Avnessh, Matt, Romain

Tzviya: if you need me?

Matt: we need to do a review to he group for 2.1 progression

Romain: AG group but not in plenary

Avneesh: agenda is sent in advance

Charles: enough people monitoring, look agenda items, posting that wood be interesting
... ok for metadate discussion

George: let the grou know when we need to join

Avneesh: APA ?

George: ACT attends and chairs the APA

<clapierre> Isn't Jason White also on APA? not sure if Jason is also active or participating with this group

George: we should familiarise with their checklist

Tzviya: Jason also

Jason: just join from the WCAG meeting, on metadata

Avneesh: ARIA?

Jason: ARIA 1.1 goes to rec

Avneesh: Tzviya and Charles already there

George: relation between DPUB ARIA and ARIA?

Charles: co-chairing the personalization TF in ARIA

Tzviya: oen oher TF with ARIA : the CSS ARIA TF
... could someone join?

Jason: need to be strategic in group involvement

Avneesh: priority?

Tzviya: very helpful

Jason: new layout features and AT
... how screen reader lanage that, box and grid layout, CSS doen’t reflex the DOM order
... how to make things available for the AT

Avneesh: Silver TF?

Jason: incrementally add req, or larger scale revision : AG has not decided yet

Avneesh: right time to influence or wait?

Jason: wait after 2.1
... not possible to add in 2.1
... AG mostly developing suvey to gather req
... input in their survey process?

Avneesh: Task forces, Cognitiv TF?

Tzviya: cogo has become the personalisation TF

Jason: digital pub should be represented there

Avneesh: WAI?

Tzviya: I’ve the emails

Jason: EO group

<tzviya> EOWG charter https://www.w3.org/WAI/EO/2015/charter6-2015-09

Jason: AG request for review

Avneesh: liaison form this group or the business group?

Tzviya: the BISG is involved with EO
... be more familair with the work there

BillK: ACrep in EO, more engemenent

BiilK: liaison with this group

Avneesh: other groups?

George: EO, training materiel an best practices, would be great to have it for pub
... EO meets at CSUN

Mia: can join in for EO as well

4. Work on audio sync text.

Avneesh: MO is not W3C

<Mia> *Waves back at Tsviya :)

Marisa get away from SMIL, choice betwaeen flat list or something more structured

Avneesh: what are the minimal req for browsers?
... start with the req

Marisa: ok

Avneesh: work with Marisa and Daniel on this doc

Daniel: in Redium2, working with a replacement of smile in JSON syntax
... clipping in and out, reusing existing Web technologies
... slidly ahead in Readium2 project

Tzviya: great, but for the rec, we have to write

Avneesh: meeting every week? do we need a poll?
... poll tommorrow

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)

Succeeded: s/WACG/WCAG/
Succeeded: s/taht/as/
Succeeded: s/teh/the/
Succeeded: s/Avneesh/Tzviya/
Succeeded: s/lore/more/
Succeeded: s/nalme/name/
Succeeded: s/il/in/
Succeeded: s/Tzviay/Tzviya/
Succeeded: s/???/Silver/
Succeeded: s/???/ACT/
Succeeded: s/Tzvia/Tzviya/
Succeeded: s/???/Marisa/
Succeeded: s/smile/SMIL/
Default Present: Avneesh

WARNING: Replacing previous Present list. (Old list: (no, one), Avneesh, tzviya, mattg, laudrain, rdeltour, clapierre, George, Bill_Kasdorf)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ tzviya, mattg, Avneesh, laudrain, rdeltour, clapierre, George, Bill_Kasdorf

Present: tzviya mattg Avneesh laudrain rdeltour clapierre George Bill_Kasdorf
Found Scribe: Avneesh
Inferring ScribeNick: Avneesh
Found ScribeNick: Tzviya
WARNING: No scribe lines found matching ScribeNick pattern: <Tzviya> ...
Found ScribeNick: laudrain
ScribeNicks: Avneesh, Tzviya, laudrain

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: 20 Jul 2017
Guessing minutes URL: http://www.w3.org/2017/07/20-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