<scribe> scribe: clapierre

DescribedAt meeting tentative August 13 @ 12:30 eastern

paul, will describedAT be part of ePub spec?

tzviya, well it will be contingent on ARIA 1.1 keeping it in the spec.

tzviya, we need more publishers, and we will reach out to Benetech.. who should I contact regarding Bookshare supporting describedAt?

charles, probably Ahn Bui.

Note A11Y DPUB

deborah, we should review of where we were with the Note.

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

…, we had a skeleton of the Note and and then had a meeting with Jean Spellman, and then got derailed with ARIA.describedAt

tzviya, we should review the current Note as

deborah, we have some formatting which was auto generated.

…, initially we are talking about WCAG and DPUB. Should also look at ATAG and UAG

…, content creator side is usually huge and disorganized, UAG should be pushed more since they are more organized smaller and they should implement what is standardized.

…, we looked at what currently isn't addressed in WCAG, (eg. footnotes, dropcat, phonetic spellings, heading levels best practices, escapability / skipability, …)

…, we think this is more UAG driven, and should adjust the NOTE initial focus potentially.

…, appendix: charles is looking into bringing all the WCAG google docs we created into that appendix.

tzviya, not sure if this should be a separate document or keep it as an appendix.

mia, thinks this should be kept in the appendix so it can be found.

deborah, this note keeps changing, was aimed at publishers and now it has switched to be more W3C focused.

…, modern digital publishing is websites so WCAG is relavent.

<tzviya> http://w3c.github.io/wai-quick-start/

tzviya, W3C education outreach is working on their own documentation,

… this may be starting a whole new rabbit hole

… there is a section on writing accessibility.

… she knows Robin and Julie from BISG will share this information.

…, we already did the WCAG review but we may need to review this and make links to this note from our note.

deborah, this is why this is a W3C note, and we should be working with WAI, and we should get Shawn on board with the issues we want addressed, and if they will support that would be great.

…, the reason why the appendix is there is that we did this work and it should be recognized.

…, we don't want to create a new note describing WCAG.

…, and our note to publishers is: here are all the documents you should be be looking at and here is all the quickstart guides, and here is the note we submitted to the W3C

deborah, we don't want to loose the data / information we have in our google docs.

…, 1. out of the things we are talking about that is not in our list (eg. mathml etc..), 2. write text (ie. fill out the body of the note), 3. We need help with making it W3C pretty

…, we are basically saying: "Browser manufacturers you need to address these issues"

tzviya, focus on first part of the document, and worry about the appendix initially

…, and if there is something specific we should then pull into the main note.

…, with every document we are working on. We need to prioritize the specific issues

…, annotations is huge and maybe we need to reach out to that new working group and say this is something crucial to DPUB.

…, there is a CSS spec for DROPCAP

deborah, how to organize the Note… list out the WCAG, and UAG this what we want you to do, and Unaddressed items list them out specifically.

tzviya, also fill out the information.

deborah, agreed this is just a skeleton.

deborah, should we give people chunks on their own?

tzviya, lets remember we are writing to a non-publishing audience.

…, I can do footnotes and list-heads

mia, I am willing to do one or two…but don't have the doc infront of me.

tzviya, nesting headers will be mine too.

mia, I can do page #'s, layout & comprehension

charles, diagrammer I will take this on.

george should take on skipability / escapability.

deborah, who should take on annotations?

tzviya Rob Sandersons, or Markus.

…, I have a vague understanding there … it may just be review the recomendations

…, Ivan may also be able too.

pual, Johnathan Thurstan has joined Pearson.

…, may be able to recruit people to help

deborah, I can take on phonetic spelling, dropcap

deborah, positional location… unclear ones, and I will take that on.

deborah, should we talk about mathml?

tzviya, we will discuss this Monday during our DPUB meeting.

mia, we need to keep this in our note

deborah, I will take on that to add a generic topic about mathML.

+1 on non formal!

…, hopefully we can do this by mid-august.

charles, will be giving a diagrammer talk August 11, and will let people know if they want to join in :)

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 Scribe: clapierre
Inferring ScribeNick: clapierre
Present: Tzviya_Siegman Charles_LaPierre Deborah Kaplan Mia Lipner Paul Belfanti

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: 24 Jul 2015
Guessing minutes URL: http://www.w3.org/2015/07/24-dpub-minutes.html
People with action items: 

WARNING: Possible internal error: join/leave lines remaining: 
        <scribe> pual, Johnathan Thurstan has joined Pearson.



WARNING: Possible internal error: join/leave lines remaining: 
        <scribe> pual, Johnathan Thurstan has joined Pearson.



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