<Joshue108> scribeNick: James

<jnurthen> scribeNick: jnurthen

Review submitted Techniques

JOC: A couple of techiques submitted
... I have started a couple of draft techniques

<DavidTodd> 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? 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

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> http://www.w3.org/TR/html5/common-input-element-attributes.html#the-required-attribute

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> 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> 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> http://www.w3.org/TR/WCAG-TECHS/H90.html could be a model for how to write a 3.2.2 technique.

<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

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at 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 scribeNick
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: http://www.w3.org/2012/02/20-html-techs-tf-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.