<jamesn> https://www.w3.org/2002/09/wbs/35422/18_2_2013/

<scribe> scribe: Detlev

Looking at survey - few answers - apologies

This is rthwe link to the survey: https://www.w3.org/2002/09/wbs/35422/18_2_2013/

Walking through Loretta's comment

Loretta: not sure why they were related to SC 1.3.1
... should be applicable to SC 2.4.4
... Question what will show up in things like SR link lists

James: aria-describedby doesn't usually show up in link lists
... Why necessary to be in 2.4.4 rather than 2.4.9?
... Fear is that this technique will be seen as necessary for meeting 2.4.4

Loretta: unsure what the issue is

James: suggests to use an example where 2.4.4 would not be met without it

Loreatta: Every 2.4.9 technique is also a 2.4.4 technique

James: Proposes one example where 2.4.4 wouldn't be met without aria-describedby

Marc: possibly looking at failures (F63) adapting for aria-described by

http://www.w3.org/TR/WCAG20-TECHS/F63.html

James: suggestion was to amending one of the examples in F63 to add to this technique so it would help meeting 2.4.4

Loretta: willing to make edits but questions remain

Group making on-the-fly edits to technique http://www.w3.org/WAI/GL/wiki/Using_aria-describedby_for_link_purpose

James: aria spec does not prescribe behaviour how AT would handle info in aria-describedby

Loretta: Will give some indication that both the link text and description text will usually both be made available
... either available at the vey end of accessible name , states etc, or offered as option to explore
... Possibility to remove headings to meet 2.4.4 from sufficient to advisory

James: but this may not happen

Loretta: shall we drop example 7, and what do you think of ex. 3?

James: Example 3 not ideal, may be covered by other examples

Lortetta: suggest dropping Ex. 3 and 7

James: seconds that
... Example 7 may not actually work anyway

Same applies to example 6 - needs testing

Detlev: Proposes testing example 6 in that technique
... suggests links to AT support database once it's there

Loretta: Detailed level of support info not usually part of WCAG techniques - changes too quickly

Moving to Technique "Using aria-label for link purpose" http://www.w3.org/WAI/GL/wiki/Using_aria-label_for_link_purpose

James: If someone's using the A11y API to compute the list of links they would get the aria-label info, if they use the DOM, they wouldn't
... Could be 2.4.9 Candidate
... Accordign to aria spec aria-label should override / replace the link text
... Good practice to start aria-label text with the same text as the link text - "Read more.." replaced by "Read more about Seminole tax hike"

(On-the -fly changes to technique being made by James)

(...explaining/reinforcing the replacement rule according to the spec's acessible name computation)

Marc: should we include the link?

<jamesn> http://www.w3.org/TR/wai-aria/roles#textalternativecomputation

James: its called text alternative comutation

sorry, text alternative computation

<jongund> I have to go

James: adding reference to SC 2.4.9

Support notes need to be updated

This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Detlev
Inferring ScribeNick: Detlev

WARNING: No "Topic:" lines found.

Default Present: James_Nurthen, Jon_Gunderson, +49.404.318.aaaa, Detlev, Loretta, Marc_Johlic, [IPcaller]
Present: James_Nurthen Jon_Gunderson +49.404.318.aaaa Detlev Loretta Marc_Johlic [IPcaller]
Got date from IRC log name: 04 Mar 2013
Guessing minutes URL: http://www.w3.org/2013/03/04-html-techs-tf-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