Revised complementary definition re: DOM hierarchy (#1779)

scottaohara · web-flow · commit ece14a16453b · 2022-08-25T08:49:09.000+02:00
resolves #1396 Clarifies that complementary content at a 'similar level' could be a sibling to the main content, or a direct child of the main content. This better aligns with the permissiveness of HTML's `<aside>` element which has no requirements of not being allowed within a `<main>`. Related: w3c/html-aam#350
diff --git a/index.html b/index.html
@@ -2603,7 +2603,7 @@ <h2>Definition of Roles</h2>
 		<div class="role" id="complementary">
 			<rdef>complementary</rdef>
 			<div class="role-description">
-				<p>A <rref>landmark</rref> that is designed to be complementary to the main content at a similar level in the DOM hierarchy, but remaining meaningful when separated from the main content.</p>
+				<p>A <rref>landmark</rref> that is designed to be complementary to the main content, but would remain meaningful if it were to be separated from the main content. Complementary content is ideally placed at a similar level in the DOM hierarchy to the main content. For instance, as a sibling in the DOM hierarchy, or as a direct child of the main content.</p>
 				<p>There are various types of content that would appropriately have this <a>role</a>. For example, in the case of a portal, this may include but not be limited to show times, current weather, related articles, or stocks to watch. The complementary role indicates that contained content is relevant to the main content. If the complementary content is completely separable from the main content, it may be appropriate to use a more general role.</p>
 				<p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>complementary</code>.
   				[=user agents=] SHOULD treat elements with role <code>complementary</code> as navigational <a>landmarks</a>.
