W3C

- DRAFT -

HTML5 & ARIA technqiues TF

22 Apr 2013

See also: IRC log

Attendees

Present
+1.254.247.aaaa, James_Nurthen, Marc_Johlic, Detlev, Paul_Adam, Loretta, Adam
Regrets
Chair
James_Nurthen
Scribe
Detlev

Contents


<Guest> hello

<scribe> scribe: Detlev

Agenda point 1: call time change

<jamesn> https://www.w3.org/2002/09/wbs/35422/New_WCAGWG_time_Last_WCAG2ICT_edit/results

There would be more participants if we move the call to the former WCAG slot on Thursday

Resolution: HTML5-WAI-ARIA Techs meeting to 4 pm Boston Time, Thursdays

Next meeting will be on Thursday 2. May

Next agenda item: Feedback on Test case DB (link via Shadi)

<jamesn> http://www.w3.org/WAI/accessibility-support/#testform

URL only accessible via W3C login (to members)

James: not quite clear yet how this DB will be helpful - will be use it for establishing new techniques?

Loretta: Seems pretty HTML specific
... If a PDF file is used for testing, would you just upload as test file

James (trying to upload a PDF file)

Detlev: use case may be for developers to document self-constructed techniques to prove they are accessible

Loretta: Alos provide test files that other people can run tests on to establish level of support
... would this upload interface meet the purpose?

James: if all files uploaded in one directory works, it should be fine - script & CSS may be in the same file to simplify things (or all files needed in same directory)

Loretta: Needs some way for removing things if they don't work

James: Where do you specify the expected result? May be the test criteria

Detlev: The logic of how all this hangs together is notz terribly clear right now

Marc: Not so clear at the beginning that you have to specify a technique (rather than a Success Criterion)
... If you create something not yet in existence on the level of WCAG Technique

James: Can you search techniques - the search icon in the field About the Test Case doesn't work yet - may just be an autocomplete
... is it valid to have a test that relies on jQuery UI - because then you won't show much code , its all under covers

Loretta: Calling these tests could be confusing because of the terminology of tests in Techniques - these are examples
... these are specific example for people to try, but different from a test of a technique (would not validate a technique)

Marc: Currently tests that are being submitted won't show up under "View tests"
... The purpose is for the community to pick them up and run them to determine whether they pass or not

James: Screenreaders may give you a false positive (if SR has repair behaviour built in)

Loretta: Its a difficult process, needs careful thought

James: Probably won't be ready for first pass of ARIA Techniques

Detlev: Not open to non W3C members?

James: if developers have a good technique they can submit it as technique proper
... for novel techniques, there is currently no way of specifying whether the example is meeting a success criteria

Loretta: Don't understand "run tests" page at all ATM

Detlev: This may be part of WAI-ACT project

Next point: Handling feedback to techniques

James: Did anyone handle feedback?

Loretta: aria-flowto won't need changes to Failure

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

Detlev: will pick up F65 add aria-LABEL / role presentation exceptions, for discusson
... will move F59 and F63 to "redy for review" section

James: encouraging Paul to write techniques if he can think of one missing

Paul: Is there a specific template / methof on writing techniques?

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

James: Yes there are general instructions / a template
... Any other business?
... Agenda will be sent out on Monday/ Tuesday

Loretta: suggests to never make a survey of a couple or three surveys

no more than 2 or three, that is

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2013/04/22 16:58:05 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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: +1.254.247.aaaa, James_Nurthen, Marc_Johlic, Detlev, Paul_Adam, Loretta, Adam
Present: +1.254.247.aaaa James_Nurthen Marc_Johlic Detlev Paul_Adam Loretta Adam
Got date from IRC log name: 22 Apr 2013
Guessing minutes URL: http://www.w3.org/2013/04/22-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


[End of scribe.perl diagnostic output]