Authors do not need to set aria-selected in single-selection containers…

index.html

@@ -12943,6 +12943,7 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
 					<li>Single-selection containers where the currently focused item is not selected. The selection normally follows the focus, and is managed by the <a>user agent</a>.</li>
 					<li>Multiple-selection containers. Authors SHOULD ensure that any selectable descendant of a container in which the <pref>aria-multiselectable</pref> attribute is <code>true</code> specifies a value of either <code>true</code> or <code>false</code> for the <sref>aria-selected</sref> attribute.</li>
 				</ol>
+				<p>Authors do not need to set <sref>aria-selected</sref> in single-selection containers where selection follows focus, unless <code>aria-selected="false"</code> is being used on the focused item to indicate that the container does not currently have a selection.</p>
 				<p>Any explicit assignment of <sref>aria-selected</sref> takes precedence over the implicit selection based on focus. If no <abbr title="Document Object Model">DOM</abbr> element in the widget is explicitly marked as selected, assistive technologies MAY convey implicit selection which follows the keyboard focus of the <a href="#managingfocus">managed focus</a> widget. If any <abbr title="Document Object Model">DOM</abbr> element in the widget is explicitly marked as selected, the user agent MUST NOT convey implicit selection for the widget.</p>
 			</div>
 			<table class="state-features">