http://www.w3.org/WAI/GL/wiki/Techniques/ARIA

<marcjohlic> http://www.w3.org/WAI/GL/wiki/Techniques/ARIA

<marcjohlic> http://www.w3.org/WAI/GL/wiki/Using_WAI-ARIA_range_attributes_for_range_widgets_such_as_progressbar,_scrollbar,_slider,_and_spinbutton

<marcjohlic> http://www.w3.org/WAI/GL/wiki/Technique_Template

<scribe> scribe: jamesn

review 3.3.1 ARIA technique - http://www.w3.org/WAI/GL/wiki/Using_WAI-ARIA_range_attributes_for_range_widgets_such_as_progressbar,_scrollbar,_slider,_and_spinbutton

MJ: Guidance says to go ahead and review the general techniques and feel free to reuse the wording to avoid confusing the reader
... technqiue for link purpose - was going to pull from general technique on link purpose.
... is that how others approach it?

LGR: Helpful but not a requirement
... Have done enough now know the general shape

MJ: It is acceptable to borrow from another technique?

LGR: if the language is appropriate yes

JG: Are the tests at the level the author does in markup or are they at the AT level

LGR: I believe the tests should be independent of the AT but we need to know what AT is doing with it to know what the level of support is

JG: talking about ARIA - the ARIA group is concerned about what the browser does, not what AT actually does with it

LGR: purpose of the test is to help someone understand if they have implemented the technique
... we know from WCAG that even if a technique should work there may not be AT support
... The trouble is - if you add AT in, what it does is a moving target
... now you don't have a universal technique
... The missing part is the AT support DB
... we make things more complicated if we mix the AT support question into what is a technique

JN: other problem wqith using AT as a testing technique is AT does error checking

LGR: for discussion if a technique is sufficient then need demonstration that AT actually supports it

JG: should there be a rule that need to test on certain combo of UA and AT?

LGR: we like to have live examples so we can check if things work
... if you are working on techniques and have "support" info then include it in the UA notes

JG: tests for a slider... when focus goes to it, then make sure identified as a slider. then when keystrokes are pressed make sure output is correct

LGR: not the kind of test we put in the technque
... keyboard access not addressed here

JG: applicability section is not filled in

LGR: that is from the template - not done yet

http://www.w3.org/WAI/GL/wiki/Using_the_role_attribute_to_expose_the_role_of_a_user_interface_component

<Loretta> Oops - skype just cut me off!

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)

Succeeded: s/if/is/
Found Scribe: jamesn
Inferring ScribeNick: jamesn
Default Present: James_Nurthen, Loretta, Marc_Johlic, jongund, [IPcaller]
Present: James_Nurthen Loretta Marc_Johlic jongund [IPcaller]
Regrets: Detlev Adam
Got date from IRC log name: 01 Oct 2012
Guessing minutes URL: http://www.w3.org/2012/10/01-html-techs-tf-minutes.html
People with action items: