<scribe> Scribe: Andi_Snow-Weaver

<scribe> ScribeNick: Andi

<input aria-required="true">

CS: in HTML4, this will map to required; in HTML5, this will map to not required because HTML5 @required will override aria-requied

DB: author error - Firefox will default to obeying the aria-required

CS: different from behavior for checked
... before HTML 5, the only way to get required is to use aria-required
... but if these behave differently in HTML 5, it seems goofy

DB: even for checked, we would go with aria

https://lists.w3.org/Archives/Member/w3c-wai-pf/2012JulSep/0012.html

CS: IE has implemented - aria-required overrides
... HTML TF making decisions about interaction of ARIA and HTML5
... compromise on checked because it already exists in HTML 4

DB: ARIA has a lot of special cases, would like to simplify

CS: that's why I made a general rule about Boolean attributes
... think required is the only one that wasn't there in HTML 4

DB: if ARIA is there, think we should assume there is a reason

CS: if aria-checked="false" and a checked attribute ...

DB: probably an author error.

<davidb> (discussion)

<davidb> (more discussion about spec work happening in too many different places)

CS: role not required to use aria attributes in HTML 5

AS: do we put the missing rule in the UAIG in the rules above the state/property mapping table

CS: don't think we should put it in the UAIG

AS: seems weird to have a rule in the spec for which we will need 2 implementations but not have it in the UAIG

DB: don't agree with the rule

Global states and properties are supported on any element in the host language. However, authors MUST use a WAI-ARIA role on an element in order to use non-global states and properties on that element. When a role attribute is added to an element, the semantics and behavior of the element, including support for WAI-ARIA states and properties, are augmented or overridden by the role behavior. User

agents MUST ignore non-global states and properties used on an element without a WAI-ARIA role.

<richardschwerdtfe> can't get in

<richardschwerdtfe> says conference is full

<richardschwerdtfe> well, can you conference me in?

<richardschwerdtfe> ?

<davidb> oh i see thanks

<davidb> richardschwerdtfe ^

Global states and properties are supported on any element in the host language. However, authors MUST use a WAI-ARIA role on an element in order to use non-global states and properties on that element. When a role attribute is added to an element, the semantics and behavior of the element, including support for WAI-ARIA states and properties, are augmented or overridden by the role behavior. User

agents MUST ignore non-global states and properties used on an element without a WAI-ARIA role.

Global states and properties are supported on any element in the host language. However, authors MUST use a WAI-ARIA role on an element in order to use non-global states and properties on that element. When a role attribute is added to an element, the semantics and behavior of the element, including support for WAI-ARIA states and properties, are augmented or overridden by the role behavior. User

agents MUST ignore non-global states and properties used on an element without a WAI-ARIA role.

http://www.w3.org/TR/wai-aria/host_languages#state_property_processing

From December 2009: http://www.w3.org/TR/2009/WD-wai-aria-20091215/host_languages#state_property_processing

in Feb 2009, we had very little info in the spec about conformance and host language: http://www.w3.org/TR/2009/WD-wai-aria-20090224/#conformance

RS: in ARIA 1.1, role will not be required in order to use aria attributes
... one way to get around this - say in UAIG that if an element that has a role that matches an aria role, it's equivalent to having assigned an ARIA role

DB: difficult to explain ARIA because of special cases that make it complex
... think we should say that if you have these attributes, we should expose them

RS: but it's meaningless in some cases

DB: can do the same thing with a custom control in Windows

RS: can't create a validation tool that would address that

CS: decided in HTML task force that for ARIA in HTML 5, if you have aria-requried, it will be honored regardless of whether the HTML 5 required attribute is there
... rule is that for new Boolean attributes, their absence can't be interpreted to be false in all cases

RS: ARIA CR requirement is HTML 4 implmentations, not HTML 5

CS: IE doesn't treat them any differently

RS: what do you do about things that didn't exist in HTML 4

CS: try to use them if we know what they are

RS: aria-required allowed only on certain elements in 1.0
... think the best we can do for 1.0 in the UAIG: if the element has an implied host language semantic that matches an ARIA role, you treat it as equivalent to having the aria role applied.

<input aria-required="true">

CS: in HTML 5, because required is not there, it would default to false and would override aria-required
... not reasonable because required is a new attribute
... <input type=checkbox aria-checked="true">, in HTML 5 would be false because HTML attribute overrides aria attributes
... want required to work differently because it is a new attribute

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/deleting the aria-required/obeying the aria-required/
Succeeded: s/note/not/
Found Scribe: Andi_Snow-Weaver
Found ScribeNick: Andi
Default Present: Andi_Snow_Weaver, Cynthia_Shelly, David_Bolter
Present: Andi_Snow_Weaver Cynthia_Shelly David_Bolter
Got date from IRC log name: 10 Jul 2012
Guessing minutes URL: http://www.w3.org/2012/07/10-aapi-minutes.html
People with action items: 

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