updates based on comments

index.html

@@ -610,12 +610,45 @@ <h3>Prohibited States and Properties</h3>
 			</section>
 		<section id="mustContain">
 			<h3>Allowed Accessibility Child Roles</h3>
-			<p>A list of roles which may be allowed on an <a>accessibility child</a> (simplified as "child") of the element with this <a>role</a>. For example, an element with the role <rref>list</rref> may own child elements with the role <rref>listitem</rref>, but not elements with the role <rref>option</rref>.</p>
-			<p>To determine whether an element is the <a>accessibility child</a> of a role, <a>user agents</a> MUST ignore any intervening elements with the role <rref>generic</rref> or <rref>none</rref>.</p>
+			<p>A list of roles which may be allowed on an <a>accessibility child</a> (simplified as "child") of the element with this <a>role</a>. For example, an element with the role <rref>list</rref> MAY own child elements with the role <rref>listitem</rref>, but MUST NOT own elements with the role <rref>option</rref>.</p>
+			<p>To determine whether an element is the <a>child</a> of an element, <a>user agents</a> MUST ignore any intervening elements with the role <rref>generic</rref> or <rref>none</rref>.</p>
 			<p>Descendants which are not children of an element ancestor are not constrained by <em>allowed accessibility child roles</em>. For example, an <code>image</code> is not an allowed child of a <code>list</code>, but it is a valid descendant if it is also a descendant of the <code>list</code>'s allowed child <code>listitem</code>.</p>
 			<p class="note">A role that has 'allowed accessibility child roles' does not imply the reverse relationship. Elements with roles in this list do not always have to be found within elements of the given role. See <a href="#scope">required accessibility parent roles</a> for requirements about the context where elements of a given role will be contained.</p>
 			<p class="note">An element with a <a href="#subclassroles">subclass role</a> of the 'allowed accessibility child role' does not fulfill this requirement. For example, the <rref>listbox</rref> role allows a child element using the <rref>option</rref> or <rref>group</rref> role. Although the <rref>group</rref> role is the superclass of <rref>row</rref>, adding a child element with a role of <rref>row</rref> will not fulfill the requirement that <rref>listbox</rref> allows children with <rref>option</rref> or <rref>group</rref> roles.</p>
 			<p class="note">An element with the appropriate <a href="#implicit_semantics">implicit WAI-ARIA semantic</a> fulfills this requirement.</p>
+			<p class="note">
+				Examples of valid ways to mark up allowed accessibility child roles include:
+				<ol>
+					<li>Direct DOM child:
+<!-- ReSpec needs these examples to be unindented. -->
+<pre>&lt;div role="listbox"&gt;
+	&lt;div role="option"&gt;option text&lt;/div&gt;
+&lt;/div&gt;</pre>
+					</li>
+					<li>DOM child with generics intervening:
+<!-- ReSpec needs these examples to be unindented. -->
+<pre>&lt;div role="listbox"&gt;
+	&lt;div&gt;
+		&lt;div role="option"&gt;option text&lt;/div&gt;
+	&lt;/div&gt;
+&lt;/div&gt;</pre>
+					</li>
+					<li>Direct <code>aria-owns</code> relationship:
+<!-- ReSpec needs these examples to be unindented. -->
+<pre>&lt;div role="listbox" aria-owns="id1"&gt;&lt;/div&gt;
+&lt;div role="option" id="id1"&gt;option text&lt;/div&gt;</pre>
+					</li>
+					<li><code>aria-owns</code> relationship with generics intervening:
+<!-- ReSpec needs these examples to be unindented. -->
+<pre>&lt;div role="listbox" aria-owns="id1"&gt;&lt;/div&gt;
+&lt;div id="id1"&gt;
+	&lt;div&gt;
+		&lt;div role="option"&gt;option text&lt;/div&gt;
+	&lt;/div&gt;
+&lt;/div&gt;</pre>
+					</li>
+				</ol>
+			</p>
 		</section>
 		<section id="scope">
 			<h3>Required Accessibility Parent Role</h3>