Handling Author Errors: form & region roles (#1683)

closes #1083

* adds initial draft content to the handling author error section to call out expected behavior for `form` and `region` landmark roles which have not been provided accessible names.
* update section to talk about fallback and implicit role
* add mention of naming to region/form landmark sentence

index.html

@@ -3538,7 +3538,7 @@ <h2>Definition of Roles</h2>
 				<p>Authors MUST give each element with role <code>form</code> a brief label that describes the purpose of the form. Authors SHOULD reference a visible label with <pref>aria-labelledby</pref> if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host language heading element or an instance of an element with role <rref>heading</rref>.</p>
 				<p>If an author uses a script to submit a form based on a user action that would otherwise not trigger an <code>onsubmit</code> event (for example, a form submission triggered by the user changing a form element's value), the author SHOULD provide the user with advance notification of the behavior.</p>
 				<p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>form</code>.
-  				<a>User agents</a> SHOULD treat elements with role <code>form</code> as navigational <a>landmarks</a>.
+  				<a>User agents</a> SHOULD treat elements with role <code>form</code> and have an accessible name as navigational <a>landmarks</a>.
   				<a>User agents</a> MAY enable users to quickly navigate to elements with role <code>form</code>.</p>
 			</div>
 			<table class="role-features">
@@ -6824,7 +6824,7 @@ <h5>Note regarding the ARIA 1.1 <rref>none</rref> role.</h5>
 				<p>Authors SHOULD limit use of the region role to sections containing content with a purpose that is not accurately described by one of the other <a href="#landmark_roles">landmark roles</a>, such as <rref>main</rref>, <rref>complementary</rref>, or <rref>navigation</rref>.</p>
 				<p>Authors MUST give each element with role region a brief label that describes the purpose of the content in the region. Authors SHOULD reference a visible label with <pref>aria-labelledby</pref> if a visible label is present. Authors SHOULD include the label inside of a heading whenever possible. The heading MAY be an instance of the standard host language heading element or an instance of an element with role <rref>heading</rref>.</p>
 				<p><a>Assistive technologies</a> SHOULD enable users to quickly navigate to elements with role <code>region</code>.
-  				<a>User agents</a> SHOULD treat elements with role <code>region</code> as navigational <a>landmarks</a>.
+  				<a>User agents</a> SHOULD treat elements with role <code>region</code> and have an accessible name as navigational <a>landmarks</a>.
   				<a>User agents</a> MAY enable users to quickly navigate to elements with role <code>region</code>.</p>
 			</div>
 			<table class="role-features">
@@ -13482,6 +13482,11 @@ <h3>Roles</h3>
 		<p>User agents are expected to perform validation of <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> <a>roles</a>.</p>
 		<p>As stated in the <a href="#role_definitions">Definition of Roles</a> section, it is considered an authoring error to use <a href="#abstract_roles">abstract roles</a> in content. User agents MUST NOT map abstract roles via the standard role mechanism of the accessibility <abbr title="application programming interface">API</abbr>.</p>
 		<p>If the <code>role</code> attribute contains no tokens matching the name of a non-abstract <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> role, the user agent MUST treat the element as if no <a>role</a> had been provided. For example, <code>&lt;table&nbsp;role=&quot;foo&quot;&gt;</code> should be exposed in the same way as <code>&lt;table&gt;</code> and <code>&lt;input&nbsp;type=&quot;text&quot;&nbsp;role=&quot;structure&quot;&gt;</code> in the same way as <code>&lt;input&nbsp;type=&quot;text&quot;&gt;</code>.</p>
+		<p>Certain landmark roles require names from authors. In situations where an author has not specified names for these landmarks, it is considered an authoring error. The user agent MUST treat such elements as if no <a>role</a> had been provided. If a valid fallback role had been specified, or if the element had an implicit ARIA role, then user agents would continue to expose that role, instead.  Instances of such roles are as follows:</p>
+		<ul>
+			<li><rref>form</rref></li>
+			<li><rref>region</rref></li>
+		</ul>
 	</section>
 	<section id="document-handling_author-errors_states-properties">
 		<h3>States and Properties</h3>