Update ARIA11.html

Author: JAWS-test2

techniques/aria/ARIA11.html

@@ -10,7 +10,7 @@
       <p>Landmarks are inserted into the page using the role attribute on an element that marks the section. The value of the attribute is the name of the landmark. These role values are listed below:
 </p>
       <ul>
-         <li>banner: A region that contains the prime heading or internal title of a page.
+         <li>banner: A region that contains mostly site-oriented content, such as the logo or a site-specific search tool.
 </li>
          <li>complementary: Any section of the document that supports the main content, yet is separate and meaningful on its own.
 </li>
@@ -20,11 +20,11 @@
 </li>
          <li>main: Main content in a document. In almost all cases a page will have only one role="main".
 </li>
-         <li>navigation: A collection of links suitable for use when navigating the document or related documents.
+         <li>navigation: A region containing a collection of navigational elements (usually links) for navigating the document or related documents.
 </li>
          <li>search: The search tool of a Web document.
 </li>
-         <li>application: A region declared as a web application, as opposed to a web document. (note: The role of application should only be used with caution because it gives a signal to screen reading software to turn off normal web navigation controls. Simple widgets should generally not be given the application role, nor should an entire web page be given the application role, unless it is not to be used at all like a web page, and not without much user testing with assistive technology.)
+         <li>region: Region of the page for which none of the above ARIA roles can be used. Must be labelled to be recognized as a region by assistive technology.
 </li>
       </ul>
       <p>There are cases when a particular landmark role could be used more than once on a page, such as on primary and secondary navigation menus. In these cases, identical roles should be disambiguated from each other using a valid technique for labelling regions (see examples below).
@@ -41,7 +41,7 @@ <h3>Simple landmarks</h3>
             <pre xml:space="preserve">&lt;div id="header" role="banner"&gt;A banner image and introductory title&lt;/div&gt;
 &lt;div id="sitelookup" role="search"&gt;....&lt;/div&gt;
 &lt;div id="nav" role="navigation"&gt;...a list of links here ... &lt;/div&gt;
-&lt;div id="content" role="main"&gt; ... Ottawa is the capital of Canada ...&lt;/div&gt;
+&lt;div id="content" role="main"&gt;&lt;h1&gt;Capital of Canada&lt;/h1&gt; Ottawa is the capital of Canada ...&lt;/div&gt;
 &lt;div id="rightsideadvert" role="complementary"&gt;....an advertisement here...&lt;/div&gt;
 &lt;div id="footer" role="contentinfo"&gt;(c)The Freedom Company, 123 Freedom Way, Helpville, USA&lt;/div&gt;</pre>
 
@@ -86,39 +86,37 @@ <h3>Search form</h3>
             <li>Examine each element with a <a href="https://www.w3.org/TR/wai-aria/#landmark_roles">landmark role</a>.
 </li>
             <li>Examine whether the landmark role attribute is applied to the section of the page that corresponds with that role. (i.e., the "navigation" role is applied to a navigation section, the "main" role is applied to where the main content begins.)
+</li>
+            <li>Examine that each landmark region that appears multiple times on the page is labelled meaningfully.
 </li>
          </ol>
       </section>
       <section class="results"><h3>Expected Results</h3>
          <ul>
-            <li>#1 and #2 are true.</li>
+            <li>#1, #2 and #3 are true.</li>
          </ul>
       </section>
    </section><section id="related"><h2>Related Techniques</h2><ul>
    	<li><a href="../general/G1">G1</a></li>
    	<li><a href="../general/G124">G124</a></li>
-      <li><a href="../html/H69">H69</a></li>
-      <li><a href="../client-side-script/SCR28">SCR28</a></li>
+    <li><a href="ARIA13">ARIA13</a></li>
+    <li><a href="ARIA20">ARIA20</a></li>
+    <li><a href="../html/H69">H69</a></li>
+    <li><a href="../client-side-script/SCR28">SCR28</a></li>
    </ul></section><section id="resources"><h2>Resources</h2>
 
          <ul>
             <li>
-                  <a href="https://www.w3.org/TR/wai-aria-practices/">WAI-ARIA Authoring Practices 1.1</a> 
+                  <a href="https://www.w3.org/TR/wai-aria-practices-1.1/#aria_landmark">WAI-ARIA Authoring Practices 1.1, Landmark Regions</a> 
                </li>
             <li>
-                  <a href="https://www.w3.org/TR/wai-aria/#usage_intro">Accessible Rich Internet Applications (WAI-ARIA) 1.0, Using WAI-ARIA Roles</a>
+                  <a href="https://www.w3.org/WAI/tutorials/page-structure/regions/">W3C Web Accessibility Tutorials, Page Regions</a>
                </li>
             <li>
-                  <a href="https://www.w3.org/TR/wai-aria/#states_and_properties">Accessible Rich Internet Applications (WAI-ARIA) 1.0, Supported States and Properties</a>
+                  <a href="https://www.w3.org/TR/wai-aria-1.1/#landmark_roles">Accessible Rich Internet Applications (WAI-ARIA) 1.0, Landmark Roles</a>
                </li>
             <li>
-                  <a href="https://www.paciellogroup.com/blog/2013/07/enabling-landmark-based-keyboard-navigation-in-firefox/">Enabling landmark-based keyboard navigation in Firefox</a>
-               </li>
-            <li> 
-                  <a href="http://accessibleculture.org/articles/2011/02/not-all-aria-widgets-deserve-role-application/">Not All ARIA Widgets Deserve role="application"</a>
-               </li>
-            <li> 
-                  <a href="https://developer.yahoo.com/blogs/ydn/aria-role-application-53608.html">When Should You Use ARIA Role="Application"?</a>
+                  <a href="https://developer.paciellogroup.com/blog/2017/05/improving-access-to-landmark-navigation/">Improving access to landmark navigation</a>
                </li>
          </ul>