This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28582 - Applying aria-autocomplete="none" is applied to an element having autocomplete="on" the native host language semantics should win.
Summary: Applying aria-autocomplete="none" is applied to an element having autocomplet...
Status: RESOLVED FIXED
Alias: None
Product: ARIA
Classification: Unclassified
Component: HTML AAM (show other bugs)
Version: Future
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-29 15:56 UTC by Rich Schwerdtfeger
Modified: 2015-06-24 08:20 UTC (History)
4 users (show)

See Also:
faulkner.steve: needinfo? (jdiggs)
faulkner.steve: needinfo? (dmazzoni)

Attachments

Description Rich Schwerdtfeger 2015-04-29 15:56:46 UTC 
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.
Comment 1 Rich Schwerdtfeger 2015-04-29 20:08:23 UTC 
Sorry, change placeholder with autocomplete.
Comment 2 steve faulkner 2015-06-13 10:32:39 UTC 
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?
Comment 3 alexander surkov 2015-06-15 15:58:04 UTC 
(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.