RE: [REVIEW REQUESTED] Rewrite of the text role

Is this really a common enough use case that we need it for 1.1?

From: White, Jason J [mailto:jjwhite@ets.org]
Sent: Tuesday, June 28, 2016 5:05 PM
To: James Nurthen <james.nurthen@oracle.com>; public-aria@w3.org
Subject: RE: [REVIEW REQUESTED] Rewrite of the text role



From: James Nurthen [mailto:james.nurthen@oracle.com]
Sent: Tuesday, June 28, 2016 4:21 PM
This is clearly text and not an image, so I would want to use the text/static/statictext role for this. I would not want to use the img role here.
[Jason] It’s a good use case. What are the use cases of this role where the content supplies the accessible name? I can appreciate a desire to provide a label that replaces the content in the platform accessibility API, but what are the use cases of the default condition where the name is taken from the element’s content?
I agree with Joanie that “text” is a confusing name for this role. I think its use cases would benefit from further elucidation either as a brief comment in the spec, or in the Authoring Practices guide. It isn’t the purpose of the spec to answer the “when should I use this feature” question, but the reasons for using this role are less obvious than most. Maybe I’m just unimaginative, but, after reading the very clear description of the role, no good applications of it sprang to mind, and I was left wondering…


________________________________

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.

________________________________