Per the 10 July UAI TF meeting, this section is supposed to be converted into a table with the current bullets as the IAccessible2 bullets. But I'm concerned that these steps are only valid for IA2. Parking the text and markup here until we determine whether this is true.


4.1. Exposing Supplemental Interfaces

In general the base markup should determine what interfaces are exposed for an accessible object. However, in the following cases WAI-ARIA markup changes which interfaces should be exposed:

    * AccessibleValue: as discussed in Value, the value interface should be exposed for objects with an aria-valuenow property when one of the roles on the elements supports that. Because the Value interface allows values to be set, aria-valuenow is really read/write. The browser needs to set aria-valuenow if the value is changed to a valid value, and the current element is not readonly or disabled.
    * AccessibleTable: should be exposed for role="grid" and role="treegrid" (XXX note: not done in Mozillaknown bug)
    * AccessibleSelection: should be exposed when a role supports aria-multiselectable, and aria-multiselectable="true"
    * AccessibleHypertext: this should not be exposed if the elements descendants have been trimmed off based on the role characteristic "Children Presentational: True":
          o button
          o img
          o math
          o progressbar
          o separator
          o slider

Although it is not a WAI-ARIA-specific issue, for the purposes of accessible web applications it is worth mentioning some additionally useful rules for exposing interfaces:

    * AccessibleAction: should at least be exposed for anything with a "click" handler, although future versions of WAI-ARIA may bring more precision to the handling of actions. Also need to support doDefaultAction in MSAA (same as action #0)this maps to a click.
    * AccessibleEditabletext: should be exposed for any region made editable via contenteditable or designMode


<h2>Managed States</h2>
	<div class="section" id="managed-states_interfaces">
		<h2>Exposing Supplemental Interfaces</h2>
		<p>In general the base markup <span class="rfc2119">should</span> determine what interfaces are  exposed for an accessible object. However, in the following cases <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr>  markup changes which interfaces should be exposed:</p>
		<table>
          <caption></caption>
            <tr>
              <th></th>
              <th></th>
        </table>
        <ul>
			<li><span class="api-interface">AccessibleValue</span>: as discussed in <a href="#mapping_special_widget-value">Value</a>, the value interface <span class="rfc2119">should</span> be exposed for objects with an <span class="property-reference">aria-valuenow</span> property when one  of the roles on the elements supports that. Because the Value interface  allows values to be set, <span class="property-reference">aria-valuenow</span> is really read/write. The  browser needs to set <span class="property-reference">aria-valuenow</span> if the value is changed to a valid  value, and the current element is not readonly or disabled.</li>
			<li><span class="api-interface">AccessibleTable</span>: <span class="rfc2119">should</span> be exposed for role=&quot;grid&quot; and role=&quot;treegrid&quot; (XXX note: not done in Mozilla&mdash;known bug)</li>
			<li><span class="api-interface">AccessibleSelection</span>: <span class="rfc2119">should</span> be exposed when a role supports <span class="property-reference">aria-multiselectable</span>, and <span class="property-reference">aria-multiselectable</span>=&quot;true&quot;</li>
			<li><span class="api-interface">AccessibleHypertext</span>:  this <span class="rfc2119">should not</span> be exposed if the elements descendants have been trimmed off based on the role characteristic "Children Presentational: True":
              <ul>
				<li>button</li>
                <li>img</li>
                <li>math</li>
                <li>progressbar</li>
                <li>separator</li>
                <li>slider</li>
			  </ul>
            </li>
		</ul>
		<p>Although it is not a <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr>-specific issue, for the purposes of  accessible web applications it is worth mentioning some additionally  useful rules for exposing interfaces:</p>
		<ul>
			<li><span class="api-interface">AccessibleAction</span>: <span class="rfc2119">should</span> at least be exposed for anything with  a &quot;click&quot; handler, although future versions of <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> may bring more  precision to the handling of actions. Also need to support  doDefaultAction in <abbr title="Microsoft Active Accessibility">MSAA</abbr> (same as action #0)&mdash;this maps to a click.</li>
			<li><span class="api-interface">AccessibleEditabletext</span>: <span class="rfc2119">should</span> be exposed for any region made editable via contenteditable or designMode</li>
		</ul>
	</div>