Updates from issue 291

techniques/aria/ARIA11.html

@@ -5,7 +5,7 @@
 </p>
       <p>They also provide an easy way for users of assistive technology to skip over blocks of content that are repeated on multiple pages and notify them of programmatic structure of a page. For instance, if there is a common navigation menu found on every page, landmark roles (or "landmarks") can be used to skip over it and navigate from section to section. This will save assistive technology users and keyboard users the trouble and time of tabbing through a large amount of content to find what they are really after, much like a traditional "skip links" mechanism. (Refer to User Agent Notes above for specifics of AT support). A blind user who may be familiar with a news site's menu, and is only interested in getting to the top story could easily navigate to the "main" landmark, and bypass dozens of menu links. In another circumstance, a user who is blind may want to quickly find a navigation menu, and can do so by jumping to the navigation landmark. 
 </p>
-      <p>Landmarks also can help sighted keyboard-only users navigate to sections of a page using a <a href="https://www.paciellogroup.com/blog/2013/07/enabling-landmark-based-keyboard-navigation-in-firefox/">browser plugin</a>. 
+      <p>Landmarks also can help sighted keyboard-only users navigate to sections of a page using a <a href="http://matatk.agrip.org.uk/landmarks/">browser plugin</a>. 
 </p>
       <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>
@@ -22,6 +22,9 @@
 </li>
          <li>navigation: A collection of links suitable for use when navigating the document or related documents.
 </li>
+         <li>region: A generic region of content to which, for an author-specific purpose, it is important for users to be able to navigate. In HTML, `section` with an accessible label maps to the region role. The region role needs an accessible label to be included as a landmark for assistive technology.
+</li>
+
          <li>search: The search tool of a Web document.
 </li>
       </ul>
@@ -71,7 +74,8 @@ <h3>Multiple landmarks of the same type and aria-label</h3>
       <section class="example">
          <h3>Search form</h3>
 
-            <p>The following example shows a search form with a "search" landmark. The search role typically goes on the form element or a div surrounding the form.</p>
+            <p>The following example shows a search form with a "search" landmark. The search role typically goes on the form element or a div surrounding the search form.</p>
+
             <pre xml:space="preserve">&lt;form role="search"&gt;
 &lt;label for="s6"&gt;search&lt;/label&gt;&lt;input id="s6" type="text" size="20"&gt;
 ...
@@ -110,7 +114,7 @@ <h3>Search form</h3>
                   <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>
                </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>
+                  <a href="https://www.tpgi.com/improving-access-to-landmark-navigation/">Enabling landmark-based keyboard navigation in Firefox</a>
                </li>
             <li>
                <a href="http://matatk.agrip.org.uk/landmarks/">Landmarks browser extension</a>