W3C

- DRAFT -

SV_MEETING_TITLE

15 Apr 2016

See also: IRC log

Attendees

Present
Deborah_Kaplan, Charles_LaPierre, George_Kerscher
Regrets
Chair
clapierre
Scribe
clapierre

Contents


<scribe> scribe: clapierre

title: Accessibility DPUB Task Force Weekly Meeting

A11Y Note Todo Items from last week

regrests+ Jean

1c) George ARIA does have heading guidance #16 https://github.com/w3c/dpub-accessibility/issues/16  (maybe this is really resolved in these techniques but I will check it out and provide details.) https://www.w3.org/WAI/GL/WCAG20-TECHS/ARIA12.html

George: I sent this in email, but it is obscure on finding it. we could put a pointer from out Note to this reference.

Deborah: we could say the gap is finding this information.

George: there is a technique on how to do this and it is in ARIA techniques but if people can't find it then it doesn't exist.
... , maybe we should put a link to it for discoverability

Deborah: this is a great link you provided George, but there are 3 things, role, headings and aria-level
... , what happens when you have different combinations or if they are nested.

George: we don't know what happens to the DOMs with these properties, in the various properties.. but this is the documentation provided.

Tzviya: this is ARIA practices are being completely rewritten now.
... , when I did research on this, I wasn't sure if it should be ARIA-level, ARIA- label, or ARIA-labelledby

<tzviya> https://www.w3.org/TR/wai-aria-practices-1.1/#kbd_layout_nesting

Deborah: there are different ways to put in headings in, HTML headings, or there are ARIA ways to do this. There needs to be a documentation explaning all of this.

George: because headings and structure is so important, should we recommend a best practice sample that eliminates the guesswork? some authoritative example. H1-6 then past 6 then it becomes a div with level with ARIA-role.

Deborah: I agree there should be a best practice technique, but we don't need to write this, we just say this is the gap and that is needed to help clarify this.
... , we shouldn't tell them what technique to use that is their call.

George: distributive object where object has its own structure, and how that integrates when it is placed is level 2.

Tzviya: we can't get into distributive objects, that is a production issue.

<tzviya> https://www.w3.org/TR/wai-aria-practices-1.1/

Tzviya: , this is a well written document

deborah: this is great and an important doc. ARIA is a fallback for HTML
... , the tecnique should be when to use ARIA.

Tzviya: this link aria practices document is great for static document. this is a preview to my talk coming up.
... , this is what I use for work.

deborah: I think we can say there is a gap here, and is a wider problem. I think we need to: there is a gap, no one knows how to do headers. what is the best practice when to use ARIA vs. HTML.

George: this is relevant to the topic of headers, but we have the same problem for a range of problems. On diagram center has best practices for images, it needs to be updated, but has always contradicted with what W3C says. so for publishing we need to find those documents in W3C

Tzviya: we don't want to tell people how to do things just the discrepancies. We need to just point them out, and not write them.

Charles: so for this topic whats the action item.

George: so for #16 someone needs to rephrase this.

Deborah: the action would be for someone to rephrase . I can but depends on what else gets put on my plate.

Tzviya: we need to look over this for tone, and we need to let go of this.

#2 Open Issues still left in GitHub

2c) what is confinement to AT? #17 https://github.com/w3c/dpub-accessibility/issues/17 

Tzviya: this should be a easy fix,

Deborah: we need to replace it with a sentence they will accept.

Tzviya: this is not a gap in the a11y documentation.

Deborah: I am not happy to taking it out.

George: isn't this covered in DPUB-ARIA?

Deborah: no this is something that browsers dont expose to other than AT.. I will rephrase this.

2d) incorrect characterisation of css speech in epub #18 https://github.com/w3c/dpub-accessibility/issues/18 

Charles: I will take this on and use Matt's sentence.

#3 Next Steps

Deborah: we will present this to DPUB on Monday and have them tell us if there are any issues.

Todo: Debora to handle #14/16 and #17 rewrite, Charles to do #18, and then on Monday present to DPUB the Note for their review

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/04/15 17:41:39 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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)

Found Scribe: clapierre
Inferring ScribeNick: clapierre
Present: Deborah_Kaplan Charles_LaPierre George_Kerscher

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

Got date from IRC log name: 15 Apr 2016
Guessing minutes URL: http://www.w3.org/2016/04/15-DPUB-minutes.html
People with action items: 

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


[End of scribe.perl diagnostic output]