Remove content related to unconditional exposure via name-value pairs

Addresses github issue #7.

Author: joanmarie

core-aam/index.html

@@ -2286,15 +2286,7 @@ <h2>General rules</h2>
         <li>User agents MUST continue to expose native semantics in addition to <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> state and property semantics except where an explicit WAI-ARIA override is allowed by the host language. For example, an <abbr title="Hypertext Markup Language">HTML</abbr> checkbox may have an <a class="property-reference" href="#aria-labelledby"><code>aria-labelledby</code></a> attribute but the native <abbr title="Hypertext Markup Language">HTML</abbr> semantics must still be exposed. </li>
         <li>User agents MUST expose additional states for certain <a class="termref">roles</a> as defined in the <a href="#mapping_role_table">Role Mapping Table</a>.</li>
         <li>User agents MUST compute states for the relevant <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> <a class="termref">attributes</a> and map to the <a class="termref" href="#dfn-accessibility-api">accessibility <abbr title="Application Programming Interface">API</abbr></a> as specified in the <a href="#mapping_state-property_table">State and Property Mapping Table</a>. To determine the relevant <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> attributes, refer to the <cite><a href="http://www.w3.org/TR/wai-aria/roles#role_definitions">Definition of Roles</a></cite> [[!WAI-ARIA]]]. Where the author has not provided values for required attributes, user agents SHOULD  process as if the default value was provided. </li>
-        <li>For forward compatibility with new <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> properties in future versions,  user agents SHOULD expose all properties not in the table below as a text string, removing the &quot;<code>aria-</code>&quot; prefix from the name, if the <abbr title="Application Programming Interface">API</abbr> supports it. For example, <samp>aria-foo=&quot;bar&quot;</samp> would be exposed with a text string <code>foo=bar</code> in <abbr title="User Interface Automation">UIA</abbr>, since <code>aria-foo</code> is  not a currently known <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property. The following list specifies the accessibility <abbr title="application programming interfaces">APIs</abbr> for exposing properties as text strings. 
-        <ul>
-          <li><abbr title="Microsoft Active Accessibility">MSAA</abbr>: not supported</li>
-          <li>IAccessible2: expose as an object attribute pair ( <code>property:string</code>)</li>
-          <li><abbr title="User Interface Automation">UIA</abbr>: expose an object attribute pair in <code>AriaProperties</code> (<code>property=string</code>) </li>
-          <li><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology-Service Provider Interface">AT-SPI</abbr>: expose as an object attribute pair (<code>property:string</code>) </li>
-        </ul>
-        </li>
-        <li>Some <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> properties are not global, and are only supported on  certain roles. If a non-global <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> state or property is used where it is not supported, user agents SHOULD NOT map the given <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property to the platform accessibility <abbr title="application programming interface">API</abbr>.  For example, if <code>aria-checked=&quot;true&quot;</code> is specified on <code>&lt;div role=&quot;grid&quot;&gt;</code>, it should not be exposed in <abbr title="Microsoft Active Accessibility">MSAA</abbr> implementations as <code>STATE_SYSTEM_CHECKED</code>. User agents MAY expose non-relevant attributes as a text string if the <abbr title="Application Programming Interface">API</abbr> supports it as described above.</li>
+        <li>Some <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> properties are not global, and are only supported on  certain roles. If a non-global <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> state or property is used where it is not supported, user agents SHOULD NOT map the given <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> property to the platform accessibility <abbr title="application programming interface">API</abbr>.  For example, if <code>aria-checked=&quot;true&quot;</code> is specified on <code>&lt;div role=&quot;grid&quot;&gt;</code>, it should not be exposed in <abbr title="Microsoft Active Accessibility">MSAA</abbr> implementations as <code>STATE_SYSTEM_CHECKED</code>.</li>
         <li>When an explicit or inherited role of <code>none</code> or <code>presentation</code> is applied to an element, the user agent MUST implement  the rules for the <a class="role-reference" href="#none"><code>none</code></a> or the <a class="role-reference" href="#presentation"><code>presentation</code></a> <a class="termref">role</a> defined in <cite><a class="specref" href="">Accessible Rich Internet Applications (WAI-ARIA) 1.0</a></cite> [[!WAI-ARIA]]].</li>
       </ol>
     </section>