<trackbot> Date: 22 April 2014

<MichaelC> scribe: Wilco

Publication timeline update

Josh: next publishing coming up
... May 15th is the deadline

Andrew: Techniques should be sent in by the 15th

Josh: Try getting techniques in in a relatively complete state in the next two weeks

WCAG @ TPAC 2014? https://www.w3.org/2002/09/wbs/35422/wcagtpac14/

Josh: TPAC is on October 27th, where there will be a WCAG face 2 face meeting
... Fill in a questionnaire if you haven't already

Michael: Space must be reserved in a week

Josh: TPAC is a good opportunity to meet with other working groups.

James: Don't know if i can make Sunday but I can make week days

Miscellaneous responses to survey items and 1 new technique: https://www.w3.org/2002/09/wbs/35422/misc22April2014/

LC2917

Resolution: accepted as proposed LC2917, LC2920

John: We should make sure link text can be used to describe the link purpose

<jon_avila> Check that the combined value of the text referenced by the one or more ID's in the aria-labelledby attribute properly combined with the link text describes the purpose of the link element.

Josh: Looks ok John

<jon_avila> Check that the combined value of the text referenced by the one or more ID's in the aria-labelledby attribute properly with the link text describes the purpose of the link element.

<AWK_> before: Check that the combined value of the text referenced by the one or more ID's in the aria-labelledby attribute properly describes the purpose of the link element.

Andrew: If you use labelledby on a link the label is not announced

John: i thought it was best practice to include the link text in the aria-label

Josh: I suggest we leave this open a little, it is not as easy because of voice recognition software

Jon: Is it a failure if you don't include aria-label in the nearby header

James: Content user won't care if it's really a header

Josh: I suggest we accept the resolution and take on the issue of speech recognition later

James: I'm fine with the proposed solution

Andrew: If aria-label is used does it become the link text?

Loretta: The link text is the content inside the link

James: If screen readers do it correctly aria-label is read in place of the content of the link

.Jon: There is perhaps some wording to change in the technique

<scribe> ACTION: Jon will suggest a text change for ARIA7 at a later time [recorded in http://www.w3.org/2014/04/22-wai-wcag-minutes.html#action01]

<trackbot> Created ACTION-255 - Will suggest a text change for aria7 at a later time [on Jon Gunderson - due 2014-04-29].

Resolution: Accepted as proposed LC2920

<Joshue108> https://www.w3.org/2006/02/lc-comments-tracker/35422/NOTE-WCAG20-TECHS-20140306/2916

LC2916

Josh: change 'the table header' to 'table headers'

<AWK_> New: H79: Identifying the purpose of a link in a data table using the link text combined with its enclosing table cell and associated table header cells

Andrew: Change it to header cells

RESOLUTION: LC2916 accepted with the proposed change from Andrew

LC2918

Jon: It was confusing when talking about description and label

RESOLUTION: LC2918, accepted as proposed

LC2919

<jon_avila> +1 with Michael

Michael: Techniques should also link to understanding, or understanding should not link to technique

<AWK_> ARIA1: http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140311/ARIA1

<AWK_> understanding 2.4.4: http://www.w3.org/TR/2014/NOTE-UNDERSTANDING-WCAG20-20140311/navigation-mechanisms-focus-order.html

<Joshue108> http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140408/ARIA1

<jon_avila> http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html

<AWK_> http://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-refs.html

David; ARIA1 is not linked to 2.4.4 because ARIA 8 (or 9?) is linked

<David> ariq 7

<David> aria 7 is labelledby for link purpose

Andrew: I wrote the resolution with the idea that techniques should be specific

Michael: For 2919 I agree with the commenter's issue, which is different from what the response addressed

<Joshue108> +q

Michael: The issue is that ARIA1 does not say it is a criteria for 2.4.4

Josh: If ARIA1 addressed 2.4.4 it should link from understanding

<AWK_> https://www.w3.org/WAI/GL/wiki/ARIA1:_Using_the_aria-describedby_property_to_provide_a_descriptive_label_for_user_interface_controls

Andrew: The task force dropped ARIA1 from 2.4.4, that means the error is in the understanding document

<David> https://github.com/DavidMacDonald/wcag/blob/master/wcag20/sources/ARIA-tech-src.xml#L2375

David: I wrote a technique to use describedby with link text

<Zakim> MichaelC, you wanted to note this sort of error I hope to eliminate with the source format reformat ;)

Michael: This is an editorial issue that should be resolved with source formatting in the future

<David> oop[s here is it https://github.com/DavidMacDonald/wcag/blob/master/wcag20/sources/ARIA-tech-src.xml#L2488

Andrew: We should remove it from 2.4.4 understanding, if ARIA1 should belong with 2.4.4 it is a separate issue

David: I agree, there is a better technique for that already

<David> Mark can you mute?

<marcjohlic> I'll dial back in

Andrew: The response should be a little simpler, saying it was an error and we'll remove the link

<jon_avila> +1

RESOLUTION: LC2919 is accepted as ammended

New Technique: Using the region role to identify a region on a page

Andrew: In general the technique seems good, tweaks are suggested

Adrew: I'm not sure this needs aria-label for 1.3.1

Andrew: The aria specs however do require this

Loretta: We maybe should not write the technique to be applied on the entire page but on a specific place on the page

David: We should avoid having many regions without labels

<AWK> http://www.w3.org/TR/WCAG20-TECHS/html.html#H37

Andrew: H37 also talks about 'each image in the content'

<Loretta> Proposed modification: "For each region of a page..." -> "For a region of a page..."

Loretta: That is an old technique which I think should be cleaned up

<David> For a part a part of the page not identified in another way:

David: it is fine to limit it to role=region

Loretta: I think part of a page is too soft

David: I agree, take it back

Andrew: To meet 1.3.1 the region does not need a label, this is required for 4.1.2

Loretta: I don't think regions don't apply to 4.1.2 because they are not interactive
... For future proofing we should not say what method should be used for labelling a region

John: I think 1.3.1 does apply to a label

James: Just because this technique requires a label does not mean not having a label is a failure

Wilco: Maybe if you iniclude a limit on using region in incorrect ways

Michael: If there are cases where authors may not use label then we should not push too hard on that

Andrew: leave the issue open for the next meeting

<AWK> RESOLUTION: leave open

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Wilco
Inferring ScribeNick: Wilco
Default Present: Andrew_Kirkpatrick, Joshue, Kathy_Wahlbin, Jon_avila, Michael_Cooper, Wilco_Fiers, kathleen, Katie_Haritos-Shea, Gregg_Vanderheiden, Marc_Johlic, Tim_Boland, Loretta, James_Nurthen, David_MacDonald
Present: Andrew_Kirkpatrick Joshue Kathy_Wahlbin Jon_avila Michael_Cooper Wilco_Fiers kathleen Katie_Haritos-Shea Gregg_Vanderheiden Marc_Johlic Tim_Boland Loretta James_Nurthen David_MacDonald
Regrets: Bruce Sailesh John_Foliot
Found Date: 22 Apr 2014
Guessing minutes URL: http://www.w3.org/2014/04/22-wai-wcag-minutes.html
People with action items: jon

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