Hi Rich,
Joseph, fyi: assuming Joanie and Alex agree on an object attribute,
see below.
Based on reading the rest of the email, I believe the proposal is:
"When @placeholder and @aria-placeholder are both present, and
@placeholder is non-empty, the user agents MUST expose the value of
@placeholder, and ignore @aria-placeholder. If @placeholder is empty,
then user agents MUST expose the value of @aria-placeholder."
I'm fine with that. Note that the Core-AAM has a section on conflicts
between ARIA and equivalent native markup semantics. It states that,
"... to prevent providing conflicting states and properties to assistive
technologies, host languages will explicitly declare where the use of
WAI-ARIA attributes on a host language element conflict with native
attributes for that element. When a host language declares a WAI-ARIA
attribute to be in direct semantic conflict with a native attribute for
a given element, user agents MUST ignore the WAI-ARIA attribute and
instead use the host language attribute with the same implicit semantic.
" [1]
Thus, the text above regarding @placeholder vs. @aria-placeholder
belongs in the HTML-AAM.
[1] http://w3c.github.io/aria/core-aam/core-aam.html#mapping_conflicts
(third paragraph, just after the editorial note).
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
