Merge pull request #274 from w3c/matf-JoeH

2.4.11 commit from branch

Author: JJdeGroot

comments/2.4.11.md

@@ -5,6 +5,10 @@
 [wcag:focus-not-obscured-minimum]
 [wcag2ict:applying-sc-2-4-11-focus-not-obscured-to-non-web-documents-and-software]
 
-Placeholder
+This applies directly as written, and as described in Intent from [Understanding Success Criterion 2.4.11](https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum.html#intent).
 
-[issue:52]
+**2.4.11 Focus Not Obscured (Minimum):** When a [user interface component](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components) receives keyboard focus, the component is not entirely hidden due to author-created content.
+
+[note:Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this success criterion.]
+
+[note:Content opened by the *user* may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered visually hidden due to author-created content.]

index.html

@@ -2935,17 +2935,18 @@ <h2>Success Criterion 2.4.11 Focus Not Obscured (Minimum)</h2>
         </footer>
       </details>
     </p>
-<p>Placeholder</p>
+<p>This applies directly as written, and as described in Intent from <a href="https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum#intent">Understanding Success Criterion 2.4.11</a>.</p>
+<p><strong>2.4.11 Focus Not Obscured (Minimum):</strong> When a <a href="https://www.w3.org/TR/wcag22/#dfn-user-interface-components">user interface component</a> receives keyboard focus, the component is not entirely hidden due to author-created content.</p>
 <p>
-      <div class="note" title="Work In Progress">
-        <p>
-          <a href="https://github.com/w3c/matf/issues/52" target="_blank">
-            Read issue #52 on GitHub
-          </a>
-        </p>
+	  <div class="note">
+        <p>Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this Success Criterion.</p>
       </div>
-    </p>
-
+</p>
+<p>
+      <div class="note">
+        <p>Content opened by the <em>user</em> may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered hidden due to author-created content.</p>
+      </div>
+</p>
       </section>
 
       <section>