<scribe> scribe: clapierre

Now you just need to get the audio connected.

or call in.. we see you in webex

<tzviya> access code: 642 567 899

title: ARIA-describedAt

George, the mandate is sometime in Aug. PF is saying they will have a Thur call with us. They want a commitment from Publishers for describedAt

…, thats what RS said in a conference call this past week.

…, deborah was tasked to write something up from DPUB.

…, otherwise describedAt will be dropped out of 1.1

…, RS said they would invite other publishers that are not apart of W3C

tzviya, (last comment was from Tzyvia)

George, using the Diagrammer that could be accessed from annotations. but we don't have annotations yet.

…, how would publishers would use this.

Deborah, I have a draft of this document which has this specifically stated.

…, 3 parts (1. use cases, 2. publishers can't commit to this, what we can offer instead of this we could commit to a couple Proof of Concepts). B. We have a new relationship with BISG which could be used to help communication between the two groups.

…, use cases. Semantic Markup / Multi Language markup. Extended explanation of linked pages. multiple lengthy descriptions in a single page.

…, all material should be accessible to all (Not just disabled)

…, only Screen Readers have ways to skip to main content etc… so that is an issue.

George, so why are we looking at describedAt which is an A11Y construct.

deborah, eg. Tumbler allows you access to alt-text but only if there is a caption, which Tumbler users don't want to have that caption.

…, UA could make this accessible to all

…, longdesc / alttext are only for images

…, describedAt is more robust

tzviya, annotations could be used but is not a recommendation yet and may not be fully accessible.

george, 3D printing / models will push this for everyone not just people with disabilities.

deborah, annotations are important, descriedBy has issues. longdesc/alttext can only be used on images, annotations does not exist yet…

<tzviya> I recommend that we create sample markup for a few use cases

george, Apples objections (they are vocal) objecting to longdesc and describedAt.

…, will cause this to be delayed if not dropped entirely

…, would love to see publishers add enhancements to content to improve A11Y.

…, put more resources into open annotations

tzviya, show markup in your draft deborah will really help, and then we can go to BISG with this document.

tzviya, was unfortunate that we didn't discuss our relationship with BISG in our meeting this past week… full agenda.

…, RS will want a # of publishers together, but if we can't commit to this then this is a problem.

George, if this isn't implemented others will create workarounds.

…, if it stays in ARIA 1.1 (we have a better chance) if it doesn't go into 1.1 then we have to look at workarounds to do this.

…, Apple would say to add links on the page or use other methods to accomplish the same thing

Deborah, do we know what the problem really is for the formal objection?

George, I think it has to do with UI design, and the ability to get back

Tzviya, it doesn't need to be that way, they could bring the external page into the current page.

…, should you ever have to link outside of the current page.

George, next steps…

…, review Deborah's document and then reach out to publishers

Tzviya, RS sooner the better, and names of publishers would help put more weight on this when its not just the DPUB.

…, the people who need to see this needs to see publishers they recognize

Deborah, its reasonable for us to say, asking trade publishers to sign-on will not happen?

George, RS says he would go to bat for us if he has a document that is endorsed by big publishers and not just DPUB.

…, killer application is 3D printing

deborah, can you elaborate for usecases

George, got a picture of the sphinx and then a link to a 3D image file of that. Maps is a great use case.

Tzviya, 3D printing is becoming a lot more affordable.

…, we don't want to describe how the UX would work

George, relief maps with 3D printing would be great!

charles, no meeting next Friday due to holiday

tzviya, we should have deborah's note and hopefully will discuss this in a couple weeks at our DPUB meeting.

George, will be away until August

tzviya, BISG WG call, Deborah would you like to be a member?

Deborah, sure… if it is going to be a huge time commitment, I would have to ask my manager.

tzviya, not really once ever 2-4 weeks.

…, I will add Julie Morris to add Deborah.

Deborah, I will send this note to Charles, George, Tzviya, Mia and Ivan.

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

WARNING: No "Topic:" lines found.


WARNING: No "Present: ... " found!
Possibly Present: dkaplan3 title tzviya
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


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: 26 Jun 2015
Guessing minutes URL: http://www.w3.org/2015/06/26-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