http://www.w3.org/2001/12/zakim-irc-bot.html

<scribe> scribenick: jeanne

<clapierre> https://github.com/w3c/dpub-accessibility/wiki

Charles: Table of contents that breaks down wCAG techniques, same for UAAG and ATAG
... focusing on WCAG techniques.
... which are relevant to dPub
... there are two links for every section
... WCAG Technique, and dPub technique
... the dPub link links to a google doc sheet

CL: last week, George Kershner and I were on the phone and we went through the general techniques
... we worked together
... G174-end I assigned to myself. I got to G186 before this call.

Jeanne: the mobile group went through a very similar process
... It's hard to identify the things that are missing, encourage people to write down the items that are missing

Mia: Screenreader problems: I can only see a few columns, the headings are not preserved, so I have to memorize the column headings.

Deborah: I have problems with Dragon with Google doc as well

Mia: I am looking at Failure Techniques and I don't know what they are referring to.
... the quickest thing for me would be to work in my own tools and enter it later.

Charles: I was looking techniques up in the WCAG Techniques page and doing the running around

Mia: That is the problem with collaborative tools, they don't work well for accessibility
... if there is a factor keeping me from finishing by next week, this will be it.

Deborah: would transforming it to another format help?

Mia: No, it is clunky but I can deal with it.

[discussion of Jaws problems]

Charles: I don't think we will stay in Google docs for long. It was just a way to get the data in one place quickly.
... people were saying that Google docs was getting better, and did work with screenreaders,.

Mia: It does seem better

Liam: I didn't know things were assigned to me and I haven't seen that.
... I did go through some of the spreadsheet

Charles: we are asking people to look through and do 40 items by next week
... it looks like Liam has already done his part.

Liam: I only marked the ones where I was confident of my opinion.

Charles: We don't expect everyone to know everything.

Deborah: I expect that none of us are experts in Silverlight and Flash techniques

Charles: I don't think we would have Flash or Silverlight techniques in dPub

Deborah: Maybe Flash

UAAG 2.0 editor's draft <- http://w3c.github.io/UAAG/UAAG20/

Jeanne: I recommend using UAAG 2.0. UAAG 1.0 is very out of date

ATAG 2.0 <- http://www.w3.org/TR/ATAG20/

Charles: I will put the success criteria from ATAG and UAAG in the chart.

http://w3c.github.io/UAAG/UAAG20-Reference/

jeanne: UAAG Reference document has a section for each success criteria "typically applies to" where you could search for "readers". The working group already flagged each success criteria that they thought applied to dPub readers.

Charles: Jeanne, Mia, George will be at CSUN, Charles and Deborah are maybe

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found ScribeNick: jeanne
Inferring Scribes: jeanne

WARNING: No "Topic:" lines found.

Present: Deborah Mia clapierre Jeanne Liam
Got date from IRC log name: 23 Jan 2015
Guessing minutes URL: http://www.w3.org/2015/01/23-dpub-minutes.html
People with action items: 

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