[html-techs-tf] Techniques Task force Minutes 2012年02月20日

Please find attached minutes from this mornings meeting both as text 
(below) and in the following link (as html).
http://www.w3.org/2012/02/20-html-techs-tf-minutes.html
Minutes from the last meeting of 2012年02月06日 which were not previously 
sent out to the list can also be found at
http://www.w3.org/2012/02/06-html-techs-tf-minutes.html
Note - Zakim was not logging attendance so no attendees are noted for 
this week's meeting.
 [1]W3C
 [1] http://www.w3.org/
 - DRAFT -
 HTML Techniques Task Force
20 Feb 2012
 See also: [2]IRC log
 [2] http://www.w3.org/2012/02/20-html-techs-tf-irc
Attendees
 Present
 Regrets
 Chair
 Joshue
 Scribe
 James, jnurthen
Contents
 * [3]Topics
 1. [4]Review submitted Techniques
 2. [5]Review of HTML5 Required Technique (URI above)
 * [6]Summary of Action Items
 _________________________________________________________
 <Joshue108> scribeNick: James
 <jnurthen> scribeNick: jnurthen
Review submitted Techniques
 JOC: A couple of techiques submitted
 ... I have started a couple of draft techniques
 <DavidTodd>
 [7]http://trace.wisc.edu/wcag_wiki/index.php?title=Using_the_html5_r
 equired_attribute_to_indicate_that_a_value_is_required_in_an_input_f
 ield
 [7] http://trace.wisc.edu/wcag_wiki/index.php?title=Using_the_html5_required_attribute_to_indicate_that_a_value_is_required_in_an_input_field
Review of HTML5 Required Technique (URI above)
 LGR: Trace wiki - will be there until it stops working
 ... better to use the w3c wiki - but if you have credetntials can
 use it
 JOC: be aware that not everyone can edit on the trace wiki
 DT: Just used this because this is what I had available
 ... just let me know where tyo transfer it to
 JOC: Straightforward technique
 DM: Whole user agent support issue
 ... There are a whole bunch of different ways of specifying required
 ... want a few examples rather than one
 JN: as long as our exmaples are correct I think that is enough
 ... isn it enough to link to the spec?
 ... I think we should use best practice
 LGR: don't want to jst refer to the spec
 JOC: Both syntaxes are correct
 Adam: can't be comprehensive - but as developers are used to using
 values for their attributes may want to add this here
 JOC: issue of multiple syntaxes is going to come up again
 Adam: If using required by iteslf should also include the other
 required is the same as required="true" which equals
 required="false" which equals required=0
 Adam: required="required" seems to be used
 <Loretta> Is this the right link?
 [8]http://dev.w3.org/html5/spec/Overview.html#attr-select-required
 [8] http://dev.w3.org/html5/spec/Overview.html#attr-select-required
 LGR: asking about relationship to aria-required
 JN: I think if in the same techiqiue we confuse the user aganet
 support
 [9]http://john.foliot.ca/required-inputs/
 [9] http://john.foliot.ca/required-inputs/
 ??: Is this AT only or all user agents?
 JOC: some are pretty accessible
 LGR: what is is supposed to be doing according to the spec?
 JOC: in some places the spec defines the user experience but on
 other places it doesn't
 LGR: wouldn't expect to define the visual experience but would
 perhaps expect that if trying to submit it would fail
 <Joshue108>
 [10]http://www.w3.org/TR/html5/common-input-element-attributes.html#
 the-required-attribute
 [10] http://www.w3.org/TR/html5/common-input-element-attributes.html#the-required-attribute
 [11]http://www.w3.org/TR/html5/common-microsyntaxes.html#boolean-att
 ribute
 [11] http://www.w3.org/TR/html5/common-microsyntaxes.html#boolean-attribute
 JN: what are we going to do for boolean attributes in html5? Both
 styles or one?
 JOC: I think we should think about it a little more
 <David> [12]http://www.eramp.com/david/html5/required.html
 [12] http://www.eramp.com/david/html5/required.html
 LGR: we should include the link to the correct place in the spec but
 should also help people in plain english
 ... Is it clear what kind of modifications need doing?
 DT: have a few notes about UA support, test procedure and ....
 LGR: needs some work on the test prodedure
 Adam: we assume that the presence of the required attribute
 satisfies the success criteria
 DT: poerhaps take out step number 2
 <David> [13]http://www.eramp.com/david/html5/html5_forms.html
 [13] http://www.eramp.com/david/html5/html5_forms.html
 JN: depends what success criteria you are trying to meet
 LGR: This could also be a 3.3.2 techique with user agent notes
 <Loretta> But 3.3.2 would still need a label, in addition.
 LGR: sounding less like a 3.3.2 candidate even for partial
 Adam: would like to see more visual discussion
 JOC: can add CSS to the field.
 LGR: could do a sufficient technique for this - need to look at H90
 <Loretta> [14]http://www.w3.org/TR/WCAG-TECHS/H90.html could be a
 model for how to write a 3.2.2 technique.
 [14] http://www.w3.org/TR/WCAG-TECHS/H90.html
 <Loretta> It would need CSS and label as well as required attribute.
 LGR: H90 discusses what the group thought was minimally acceptable
 <Loretta> For each indicator of required status that is not provided
 in text, check that the meaning of the indicator is explained before
 the form control that uses it.
 LGR: concern is that * is easy to miss
 JOC: I like having the text required in the label
 JN: I think this should be a seperate technique
 LGR: agree
Summary of Action Items
 [End of minutes]
 _________________________________________________________
 Minutes formatted by David Booth's [15]scribe.perl version 1.136
 ([16]CVS log)
 $Date: 2012年02月20日 18:13:46 $
 _________________________________________________________
 [15] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
 [16] http://dev.w3.org/cvsweb/2002/scribe/
Scribe.perl diagnostic output
 [Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136 of Date: 2011年05月12日 12:01:43
Check for newer version at [17]http://dev.w3.org/cvsweb/~checkout~/2002
/scribe/
 [17] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/
Guessing input format: RRSAgent_Text_Format (score 1.00)
Succeeded: s/parialt/parital/
Succeeded: s/parital/partial/
Found ScribeNick: James
WARNING: No scribe lines found matching ScribeNick pattern:<James> ...
Found ScribeNick: jnurthen
Inferring Scribes: James, jnurthen
Scribes: James, jnurthen
ScribeNicks: James, jnurthen
WARNING: No "Present: ... " found!
Possibly Present: DM DT David DavidTodd David_ JN JOC Joshue Joshue108
LGR Loretta adam html-techs-tf inserted jnurthen left marcjohlic scribe
Nick
You can indicate people for the Present list like this:
 <dbooth> Present: dbooth jonathan mary
 <dbooth> Present+ amy
Got date from IRC log name: 20 Feb 2012
Guessing minutes URL: [18]http://www.w3.org/2012/02/20-html-techs-tf-mi
nutes.html
People with action items:
 [18] http://www.w3.org/2012/02/20-html-techs-tf-minutes.html
WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.
 End of [19]scribe.perl diagnostic output]
 [19] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm

Received on Tuesday, 21 February 2012 00:30:46 UTC

AltStyle によって変換されたページ (->オリジナル) /