Counter-proposal regarding aria-roledescription

aria/aria.html

@@ -10309,8 +10309,8 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 				<p>Some <a>assistive technologies</a>, such as screen readers, present the role of an element as part of the user experience. Such assistive technologies typically localize the name of the role, and they may customize it as well. Users of these assistive technologies depend on the presentation of the role name, such as "region," "button," or "slider," for an understanding of the purpose of the element and, if it is a widget, how to interact with it.</p>
 				<p>The <code>aria-roledescription</code> property gives authors the ability to override how assistive technologies localize and express the name of a role. Thus inappropriately using <code>aria-roledescription</code> may inhibit users' ability to understand or interact with an element. Authors SHOULD limit use of <code>aria-roledescription</code> to clarifying the purpose of non-interactive container roles like <rref>group</rref> or <rref>region</rref>, or to providing a <em>more specific</em> description of a <rref>widget</rref>.</p>
 				<p>User agents MUST NOT expose the <code>aria-roledescription</code> attribute if the value of aria-roledescription is empty or contains only whitespace characters.</p>
-				<p>If <code>aria-roledescription</code> is applied to a generic or semantically <em>meaningless</em> presentational element (for example, <code>div</code> or <code>span</code> in HTML), user agents SHOULD NOT expose <code>aria-roledescription</code> unless the author also defines an explicit WAI-ARIA role value.</li>
-				<p>If <code>aria-roledescription</code> is applied to a semantically <em>meaningful</em> host language element whose implicit role semantic is not defined by WAI-ARIA, user agents SHOULD expose <code>aria-roledescription</code>, even if the author does not provide an explicit WAI-ARIA role value.</li>
+				<p>User agents MUST expose the <code>aria-roledescription</code> attribute if a valid value is applied to a host language interactive control.</p>
+				<p>If <code>aria-roledescription</code> is applied to a host language container element, user agents MUST NOT expose <code>aria-roledescription</code> unless the author also defines an explicit WAI-ARIA role value, or the host language has explicitly identified the element as supporting <code>aria-roledescription</code>.</p>
 				<p><a>Assistive technologies</a> SHOULD use the value of <code>aria-roledescription</code> when presenting the role of an element, but SHOULD NOT change other functionality based on the role of an element that has a value for <code>aria-roledescription</code>. For example, an assistive technology that provides functions for navigating to the next <rref>region</rref> or <rref>button</rref> would allow those functions to navigate to regions and buttons that have an <code>aria-roledescription</code>.</p>
 				<p>The following two examples show the use of <code>aria-roledescription</code> to indicate that a non-interactive container is a "slide" in a web-based presentation application.</p>
 				<pre class="example highlight">&lt;div role="region" aria-roledescription="slide" id="slide42" aria-labelledby="slide42heading"&gt;