28582 2015-04-29 15:56:46 +0000 Applying aria-autocomplete="none" is applied to an element having autocomplete="on" the native host language semantics should win. 2015-06-24 08:20:43 +0000 1 1 1 Unclassified ARIA HTML AAM Future PC All RESOLVED FIXED P2 normal --- 1 schwer faulkner.steve dmazzoni jason jdiggs surkov.alexander oldest_to_newest 119992 0 schwer 2015-04-29 15:56:46 +0000 When aria-placeholder="none" is applied to an element having placedholder="on" The native host language semantics should win. Currently, the accessibility API will allow the aria attribute to win and incorrectly convey information to the AT. 119997 1 schwer 2015-04-29 20:08:23 +0000 Sorry, change placeholder with autocomplete. 120963 2 faulkner.steve 2015-06-13 10:32:39 +0000 added requirement to spec "If the element includes both autocomplete and aria-autocomplete attributes with valid values, User Agents MUST expose only the autocomplete attribute value. " https://github.com/w3c/aria/commit/ab0ad6b6e2a527779c88dac0bc6cb3cbdabff65d Alex, Dominic, Joanie - OK with you all? 121002 3 surkov.alexander 2015-06-15 15:58:04 +0000 (In reply to steve faulkner from comment #2) > added requirement to spec > "If the element includes both autocomplete and aria-autocomplete attributes > with valid values, User Agents MUST expose only the autocomplete attribute > value. " > > https://github.com/w3c/aria/commit/ab0ad6b6e2a527779c88dac0bc6cb3cbdabff65d > > Alex, Dominic, Joanie - OK with you all? I'm good with the approach, that ARIA steps away when it's in conflict with native markup. However the place to say that feels a bit inappropriate. I'd say all we need is HTMLaam spec says that autocomplete has same semantics as aria-autocomplete (and it does), and ARIA spec says that native markup takes over in conflict.