RE: The use of aria-readonly on contenteditable elements

>-----Original Message-----
>From: Joanmarie Diggs []
>Sent: Monday, May 09, 2016 5:02 PM

>I do not believe it would clear up this issue. It would address the unsupported
>role use. But we'd still have the situation in which the author put aria-
>readonly="true" on the contenteditable causing screen readers to present an
>editable element as not-editable/readonly.

Would there be strong objections to declaring contenteditable as providing strong native host language semantics?


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.


Received on Tuesday, 10 May 2016 17:18:30 UTC