<marcjohlic> test

<Loretta> Ugh - just lost networking on my laptop, which is where skype is installed...

<Loretta> I'm working on it...

<Loretta> yes, please don't wait!

Techniques and mapping to guidelines

adam: no precise rule of thumb. The range technique seemed too all encompassing, but do agree that if have one attribute then one techqnique could cover a number of success criteria
... the headers technqiue which have discussed often in WCAG. When we do have a consensus that there is one implementation. With headers there is a difference between the implementation.

JN: I am the opposite

<adam> im gone for 4-5 minutes, sorry

marc: there are different situations to use it, but the technqiue is always the same, so maybe one simplified technique to apply to different success criteria.
... purpose is to describe whatever that element is

loretta: somewhat case by case

marc: if look at the label one in particualt

james: one major difference i am aware of is in support of label when labelling different things

<adam> back

james: as far as I know some AT will or wont support using aria-label on certain elementsw

<Loretta> why is skype being so flaky!

james: concerned about muddying the waters by including too much in a single techqnique where there may be things like best practices, AT support etc that differ when using for different elements

marc: if something has poor support but it is the intended purpose should we created techniques

loretta: replacing the link text sounds confusing for a link

<Loretta> ,...and I have conducted some screenreader tests on the aria-labelledby for link purpose technique: http://www.3needs.org/en/testing/code/aria-labelledby-for-link-purpose.html Not sure whether that is worth discussing - it seems that aria-labelledby is poorly supported on non-form elements, as James (I believe) already noted in his comments.

james: doesn't it depend on what you are replacing it with
... labelledby makes that easier as you can point to itelf and something elsde

marc: almost impossible to fail 2.4.4. This would allow the "more" link to refer to a header

loretta: the information would be different for sighted and non-sighted users
... this is why links feel different from other things
... a link should be some kind of text
... this is why i'm having this reaction to folding link in with other objects
... If we create link techniques should we add this

joshue: image without an alt not a complete structure. Need to talk about some things sooner or later.

marc: why i go back to the readmore scenario

loretta: could image we do one for links which includes the original link text
... if the technqique is just to include aria-label then only need one technique

<Loretta> brb

<Loretta> back

aria-activedescendant

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)

No ScribeNick specified.  Guessing ScribeNick: jamesn
Inferring Scribes: jamesn
Default Present: James_Nurthen, Marc_Johlic, Loretta, [IPcaller], Joshue, adam_solomon
Present: James_Nurthen Marc_Johlic Loretta [IPcaller] Joshue adam_solomon

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: 08 Oct 2012
Guessing minutes URL: http://www.w3.org/2012/10/08-html-techs-tf-minutes.html
People with action items: