- From: Jeanne Spellman <jeanne@w3.org>
- Date: Fri, 23 Jan 2015 16:49:25 -0500
- To: public-dpub-accessibility@w3.org
Minutes: http://www.w3.org/2015/01/23-dpub-minutes.html
Text of minutes:
[1]W3C
[1] http://www.w3.org/
- DRAFT -
DPub Accessibility
23 Jan 2015
See also: [2]IRC log
[2] http://www.w3.org/2015/01/23-dpub-irc
Attendees
Present
Deborah, Mia, clapierre, Jeanne, Liam
Regrets
Chair
Charles, Deborah
Scribe
jeanne
Contents
* [3]Topics
* [4]Summary of Action Items
__________________________________________________________
[5]http://www.w3.org/2001/12/zakim-irc-bot.html
[5] http://www.w3.org/2001/12/zakim-irc-bot.html
<scribe> scribenick: jeanne
<clapierre> [6]https://github.com/w3c/dpub-accessibility/wiki
[6] 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 <- [7]http://w3c.github.io/UAAG/UAAG20/
[7] http://w3c.github.io/UAAG/UAAG20/
Jeanne: I recommend using UAAG 2.0. UAAG 1.0 is very out of
date
ATAG 2.0 <- [8]http://www.w3.org/TR/ATAG20/
[8] http://www.w3.org/TR/ATAG20/
Charles: I will put the success criteria from ATAG and UAAG in
the chart.
[9]http://w3c.github.io/UAAG/UAAG20-Reference/
[9] 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
Summary of Action Items
[End of minutes]
Received on Friday, 23 January 2015 21:48:58 UTC