RE: aria-readonly and plain elements

From: Aaron Leventhal [mailto:aleventhal@google.com]
Sent: Thursday, July 27, 2017 12:16 PM

HTML-AAM currently states: "If the element has the contenteditable attribute and aria-readonly="true", User Agents must expose only the contenteditable state.".
[Jason] The rationale for this which immediately comes to mind is the general principle that host language features take precedence over ARIA features in cases of conflict. If an element is declared to be contenteditable and aria-readonly, this is an apparent contradiction, and thus the host language attribute, contenteditable, is given priority.
Now Aaron may well wish to argue that in his special case, it makes good sense to supply both attributes, and then the question would be whether to make an exception to the general principle.

________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________