<scribe> scribe: clapierre

A11Y Note

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

Mia: Sorry I did not get to my items.

Charles: I didn't find anything in our Google Doc from our WCAG techniques which need to be included in our NOTE.

George: all we need to say is WCAG A/AA apply to Digital Publishing

Tzviya: I don't think we need to get into the Levels of WCAG, we are talking about relevance not implementation.

George: I worry about long desc and long descriptions for images not being possible today for publishers.
... which is a A req.

Tzviya: The content will still be accessible without the descriptions. it may be difficult to implement.
... WCAG doesn't specify how a text desc. should be handled it just needs to be there.
... I think I didn't have any topics… since I was in meetings for 2 weeks.

Deborah: I got some drafts done and want to polish this up before adding to our wiki.

Charles: should we put the Diagrammer be moved into the appendix.

Deborah: there was others at the end of our last meeting should be added to the appendix.

Mia: Like assessments be added to the appendix.

George: Testing in General?

Deborah: there is a ton of issues with tests / assesments timing etc… Markku H. with ETS is working on these issues, and we do need to raise the issue with DPUB. and a NOTE will say that this work is being done but outside of W3C

George: I agree we need to reference it but not endorse it, but is relevant to DPUB
... the link here will become our Note correct?

Deborah, Charles did you go through and make sure all our DPUB specific issues in our Google Doc make it into our Note?

Charles: Yes they are all part of our main note.

Deborah, someone will need to wordsmith.

Tzviya: is it still possible to finish by end of year?

Deborah: we are still missing our deadlines and thanksgiving to end of year is short.

Tzviya: the text in there is not publishable as is. and we won't have enough time by year end to finish that.

Charles: does it seem possible by end of year to at least have our main meat done by end of year.

Tzviya: lets talk about what goes into the appendix. Diagrammer going into appendix is 1.

George: putting diagrammer into the appendix sounds right.

Tzviya: work ETS is doing is a future / Web Components is a solution to a set of problems.

George: but Diagrammer is the container to hold the info and Web Components will be the linking mech.

Tzviya: Charles needs to reach out to Mark to look at this so far and help write the paragraph to go into the appendix.

George: is the 3D work same as Diagrammer? Someone could link to 3d / description an STL file and how to use it . Is there anything in Digital publish library of America for long descriptions.

Mia: there is a way to point to 3d object file and how to use it and could be applied to diagrammer.

George: sounds like there isn't enough guidance on how to do that in an appendix.

Mia: the only think we could have is a link to a zip file with a 3d file/text description file on how to use it.

Charles: anything else to move over to the Appendix?

Tzviya: by the time we publish this we may want to point to epub 3.1 metadata

Charles / George: ya

Tzviya: css wg & ARIA making generating content accessible. something that is used in the real world, and its not just decorative. We may want to mention it here.

Mia: yeah.

George: where is that in WCAG?

Tzviya: I don't know that it is..
... make content readable under perceivable / understandable

Mia: may be able to be shoehorned into someplace. Dynamic content

George: Pre/post generated content… list items bullets / numbering.

Tzviya: section 222 of WCAG assuming the content is not that meaningful. But if the whole website is a .write file then you loose out on everything
... I could try to write a little second on generated content, but it might not be possible, since this is being discussed by ARIA/CSS WG

Tzivya: I will reach out to George and start adding to the appendix.

Charles: feel free to scrap the current appendix and start over

George: I will be around til Christmas.
... tightening up of 3.1… do we reference EPUB 3.1 from our Note. or even EPUB in general / successors. Since it is based on web, referencing it is important. The links also between this and the 508 refresh and digital publishing

Tzviya: whos the audience of this Note.

Deborah: audience: is WCAG/UAG/ATAG/Outreach totally an internal document.

Tzviya, we can mention EPUB but our audience are not people who are writing EPUB

scribe: , PWP any mention of EPUB was an issue and we need to be cautious

Charles: gave a brief update on the webinar yesterday.

Mia: I though the 508 refresh as all information that is presented in an electronic format would apply. I would expect it will apply to DPUB.

George: are any of you been asked to go to meetings?

All: No

Tzviya: Before Ed McCoy left, he tried to get an A11Y team in place in AAP.

George: an industry wide standard would be better than a Law
... Baltimore in Feb for meetings IMS are.

Charles: Thanks everyone, and Happy Thanksgiving.
... there won't be a meeting next week due to the holiday, will meet back in 2 weeks.

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: clapierre1
Found Scribe: clapierre
Present: TzviyaSiegman GeorgeKerscher MiaLipner DeborahKaplan Charles_LaPierre

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


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

Got date from IRC log name: 20 Nov 2015
Guessing minutes URL: http://www.w3.org/2015/11/20-dpub-minutes.html
People with action items: 

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