<trackbot> Date: 13 March 2015

<scribe> scribenick: liam

clapierre: initial work nearly done but we have questions for WCAG as it related to dpub

that and we also asked our IG to look for dpub-specific items that may not be included already in WCAG

I'm wondering if we should the list out of non-related technique from WCAG as well as the one we still had qq regarding

and send to whom?

to try & figure what's relevant to dpub

George: is this a q of what's missing from WCAG?

clapierre: no, that's a different question

it's where it wasn't a simple yes/no it affects dpub but there was a question

Do we bring it up in our own TF or in the DPUB IG

tzviya: looks like you have about 20 questions

clapierre: no, there's more than was in my email

tzviya: in the email you sent me there were actual items, I'm guessing between 20 & 30

Perhaps we should go through them on this call

George: I'm focused on epub3, in the consensus of what's an accessible product, there's standards & techniques and also an agreements about what's inside the publication
... whether it's online, or downloadable.

I was tasked with this by DAISY; publishers keep asking what they should do.

clapierre: I think that's what we're trying to do here too.

We were planning on a Note on dpub best practices wrt a11y.

GK: if we're using HTML techniques then I think we're good with epub and publishing on the Web

dkaplan3: we're trying to verify that

Are there concerns specific to publishing that WCAD has not thought of

GK: so when we talk about images there's extensive guielines; I've not seen imagemaps in digital publications.

dkaplan3: E.g. annotations or pagination are things publishing has to care about but W3C a11y specs dont' speak about much yet

<Livio> hi

so what's in publishing and not well-handled is what we're looking for

tzviya: I think the disconnect is George is used to dealing with publishers; we've been looking at publishing a document that can describe best practices today for publishers;

we need a survery of W3C's documentation - is is relevant, does it address all the needs for publishers

And talking about best practices for publishers is a little different.

<Livio> this is true liam

tzviya: so the immediate charter of the dpub IG is to include the survey of existing docs, we're almost done

step 2 is to change the future

GK: I'm still thinking what I'm talking about is different, not just technology, it's conformance and guidance to students on how they get more if the documents are not fully accessible but conform to A or AA but doesn't get the students passing grades

mia: that makes sense but I think it's something else

we're not only considering students. It's important.

It's sort of like providing alternatives; Old 508 said if you can't make this accessible you must provide an alternative that has the same information/functionality

Maybe having something like that, if you can't make this publication fully accessible you must provide some kind of guidance for a user on how they might obtain something in accessible format

including professional learners

<clapierre> akk liam

<Zakim> liam, you wanted to say we can change the future

Liam: [reminder] we're here to talk about how to change the Web, all of the Web as necessary, to achieve the accessibility that pulishers & readers need

tzviya: George is saying, if the content isn't accessible enough, maybe that's a recommendation we cam make to WCAG

GK: I think when we get into bookmark or annotation or pagination do we ask WCAG?

tzviya: one fundamental thing is if the content is not accessible we need to tell users how to make content accessible

so recommending that WCAG include that is itself a recommendation

Similarly we can comment on fragments/pagination and the whole annotations model

and say what needs to be addressed

clapierre: and we'd reference these things in our note.

GK: is there any discussion about pagination being an annotation?

e.g. to annotate print page boundaries

tzviya: in the context of CSS, pagination means chunking into specific fragments, and interaction with DOM and scripts, doesn't just mean page numbers from print

mia: so would that cover helping to reflow text when magnified?

tzviya: yes. Work is being done in CSS to make a cleaner model

clapierre: [discussion of meeting topics]

Next meeting same time next week

If you can please respond to Deborah's email today re. what could be missing from WCAG and friends

[adjourned]

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)

Succeeded: s/clapierre,/clapierre:/
Succeeded: s/tzviya/dkaplan3/
Succeeded: s/dkaplan3/mia/
Succeeded: s/GK/clapierre/
Succeeded: s/dkaplan3/mia/
Found ScribeNick: liam
Inferring Scribes: liam

WARNING: No "Topic:" lines found.

Default Present: +1.415.400.aaaa, +1.617.235.aabb, clapierre, George_Kerscher, Tzviya, Jeanne, Liam, +1.415.400.aacc
Present: +1.415.400.aaaa +1.617.235.aabb clapierre George_Kerscher Tzviya Jeanne Liam +1.415.400.aacc

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 13 Mar 2015
Guessing minutes URL: http://www.w3.org/2015/03/13-dpub-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