w3c · alastc · May 25, 2022 · May 24, 2022 · May 24, 2022 · May 25, 2022
diff --git a/guidelines/index.html b/guidelines/index.html
@@ -276,12 +276,10 @@ <h3>Navigable</h3>
 
                 <section data-include="sc/20/section-headings.html" data-include-replace="true"></section>
 
-                <section data-include="sc/22/focus-appearance-minimum.html" data-include-replace="true"></section>
+                <section data-include="sc/22/focus-appearance.html" data-include-replace="true"></section>
 
                 <section data-include="sc/22/focus-not-obscured.html" data-include-replace="true"></section>
 
-                <section data-include="sc/22/focus-appearance-enhanced.html" data-include-replace="true"></section>
-
                 <section data-include="sc/22/page-break-navigation.html" data-include-replace="true"></section>
 
             </section>

diff --git a/guidelines/sc/22/focus-appearance-enhanced.html b/guidelines/sc/22/focus-appearance-enhanced.html
diff --git a/...lines/sc/22/focus-appearance-minimum.html → guidelines/sc/22/focus-appearance.html b/...lines/sc/22/focus-appearance-minimum.html → guidelines/sc/22/focus-appearance.html
@@ -1,6 +1,6 @@
 <section class="sc new">
 
-    <h4>Focus Appearance (Minimum)</h4>
+    <h4>Focus Appearance</h4>
 
     <p class="conformance-level">AA</p>
 	<p class="change">New</p>

diff --git a/guidelines/sc/22/focus-not-obscured-enhanced.html b/guidelines/sc/22/focus-not-obscured-enhanced.html
@@ -0,0 +1,11 @@
+<section class="sc new">
+
+    <h4>Focus Not Obscured (Enhanced)</h4>
+
+    <p class="conformance-level">AA</p>
+	<p class="change">New</p>
+
+    <p>When a <a>user interface component</a> receives keyboard focus, no part of the <a>focus indicator</a> is hidden by author-created content.</p>
+
+
+ </section>
diff --git a/guidelines/sc/22/focus-not-obscured.html b/guidelines/sc/22/focus-not-obscured.html
@@ -1,6 +1,6 @@
 <section class="sc new">
 
-    <h4>Focus Not obscured</h4>
+    <h4>Focus Not Obscured (Minimum)</h4>
 
     <p class="conformance-level">AA</p>
 	<p class="change">New</p>

diff --git a/techniques/css/C41.html b/techniques/css/C41.html
@@ -66,7 +66,7 @@ <h3>Expected Results</h3>
 				<ul>
 					<li>#2 and #3 are true.</li>
 				</ul>
-				<p>The required change of contrast for <a href="../../understanding/22/focus-appearance-minimum.html">Focus Appearance Minimum</a> is 3:1, this technique also applies to <a href="../../understanding/22/focus-appearance-enhanced.html">Focus Appearance Enhanced</a>, which has a higher requirement of 4.5:1.</p>
+				<p>The required change of contrast for <a href="../../understanding/22/focus-appearance-minimum.html">Focus Appearance Minimum</a> is 3:1, this technique goes slightly beyond the minumum requirement.</p>
 			</section>
 		</section>
 		<section id="related">

diff --git a/understanding/21/non-text-contrast.html b/understanding/21/non-text-contrast.html
@@ -121,7 +121,7 @@ <h4 id="related-focus">Relationship with Focus Visible</h4>
 						The external green indicator (#008000) does contrast with the white background (#FFF) which the component is on, <strong>passing</strong> the criterion. It does not need to contrast with both the component background and the component.
 					</figcaption>
 				</figure>
-				<p>Although the figure above with a dark outline passes non-text contrast, it is not a good indicator unless it is very thick. <span class="wcag22">There is a criterion in WCAG 2.2 that addresses this aspect, <a href="../22/focus-appearance-minimum.html">Focus Appearance (minimum)</a>.</span></p>
+				<p>Although the figure above with a dark outline passes non-text contrast, it is not a good indicator unless it is very thick. <span class="wcag22">There is a criterion in WCAG 2.2 that addresses this aspect, <a href="../22/focus-appearance-minimum.html">Focus Appearance</a>.</span></p>
 
 				<p>If an indicator is partly inside and partly outside the component, either part of the indicator could provide contrast.</p>
 

diff --git a/understanding/22/focus-appearance-enhanced.html b/understanding/22/focus-appearance-enhanced.html
diff --git a/...standing/22/focus-appearance-minimum.html → understanding/22/focus-appearance.html b/...standing/22/focus-appearance-minimum.html → understanding/22/focus-appearance.html
@@ -6,7 +6,7 @@
    <link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link>
 </head>
 <body>
-   <h1>Understanding Focus Appearance (Minimum)</h1>
+   <h1>Understanding Focus Appearance</h1>
 
     <section id="status" class="advisement">
         <h2>Status</h2>
@@ -16,7 +16,7 @@ <h2>Status</h2>
 
    <section class="remove">
 
-        <h2>Focus Appearance (Minimum) Success Criterion text</h2>
+        <h2>Focus Appearance Success Criterion text</h2>
         <blockquote>
             <p class="conformance-level">AA</p>
 
@@ -68,10 +68,10 @@ <h2>Focus Appearance (Minimum) Success Criterion text</h2>
 
     <section id="intent">
 
-        <h2>Intent of Focus Appearance (Minimum)</h2>
+        <h2>Intent of Focus Appearance</h2>
 
 
-        <p>The purpose of this Success Criterion (SC) is to ensure a keyboard focus indicator is clearly visible and discernible. Focus Appearance (Minimum) is closely related to <a href="https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html">2.4.7 Focus Visible</a> and <a href="https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html">1.4.11 Non-text Contrast</a>. Where Focus Visible merely requires a visible focus indicator, this SC defines a minimum level of visibility. Where Non-text Contrast requires a component to have adequate contrast against the background in each of its states, this SC requires sufficient contrast for the focus indicator itself.</p>
+        <p>The purpose of this Success Criterion (SC) is to ensure a keyboard focus indicator is clearly visible and discernible. Focus Appearance is closely related to <a href="https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html">2.4.7 Focus Visible</a> and <a href="https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html">1.4.11 Non-text Contrast</a>. Where Focus Visible merely requires a visible focus indicator, this SC defines a minimum level of visibility. Where Non-text Contrast requires a component to have adequate contrast against the background in each of its states, this SC requires sufficient contrast for the focus indicator itself.</p>
 
         <p>For sighted people with mobility impairments who use a keyboard or keyboard-like device (such as a switch or voice input), knowing the current point of focus is very important. Visible focus must also meet the needs of users with low vision, who may also be keyboard-only users.</p>
 
@@ -469,7 +469,7 @@ <h2>Resources</h2>
     </section>
 
     <section id="techniques">
-        <h2>Techniques for Focus Appearance (Minimum)</h2>
+        <h2>Techniques for Focus Appearance</h2>
 
 
         <section id="sufficient">

diff --git a/understanding/22/focus-not-obscured-enhanced.html b/understanding/22/focus-not-obscured-enhanced.html
@@ -0,0 +1,91 @@
+<!DOCTYPE html>
+<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
+<head>
+   <meta charset="UTF-8"></meta>
+   <title>Understanding Focus Not Obscured (Enhanced)</title>
+   <link rel="stylesheet" type="text/css" href="../../css/editors.css" class="remove"></link>
+</head>
+<body>
+   <h1>Understanding Focus Not Obscured (Enhanced)</h1>
+
+    <section id="status" class="advisement">
+        <h2>Status</h2>
+        <p>This understanding document is part of the <a href="https://w3c.github.io/wcag/guidelines/22/"><strong>draft</strong> WCAG 2.2 content</a>. It may change or be removed before the final WCAG 2.2 is published.</p>
+    </section>
+
+
+   <section class="remove">
+
+        <h2>Focus Not Obscured Success Criterion text</h2>
+        <blockquote>
+         <p>When a <a>user interface component</a> receives keyboard focus, no part of the <a>focus indicator</a> is hidden by author-created content.</p>
+        </blockquote>
+     </section>
+
+    <section id="intent">
+
+        <h2>Intent of Focus Not Obscured (Enhanced)</h2>
+
+        <p>The purpose of this Success Criterion is to ensure that a component with keyboard focus is visible. This criterion is closely related to <a href="./focus-not-obscured.html">Focus Not Obscured (Minimum)</a> but requires that the whole of the component is visible.</p>
+
+    </section>
+
+    <section id="benefits">
+      <h2>Benefits of Focus  Not Obscured (Enhanced)</h2>
+
+      <ul>
+         <li>This Success Criterion helps anyone who relies on the keyboard to operate the page by letting them visually determine the component on which keyboard operations will interact at any point in time.</li>
+         <li>People with attention limitations, short term memory limitations, or limitations in executive processes benefit by being able to discover where the focus is located.</li>
+      </ul>
+
+   </section>
+
+   <section id="examples">
+      <h2>Examples of Focus  Not Obscured (Enhanced)</h2>
+
+      <ul>
+         <li>A page has a sticky footer (attached to the bottom of the vieport). When tabbing down the page the focused item is not overlapped by the footer at all.</li>    
+      </ul>
+
+   </section>
+
+   <section id="resources">
+       <h2>Resources</h2>
+
+   </section>
+
+
+   <section id="techniques">
+      <h2>Techniques for Focus Not Obscured (Enhanced)</h2>
+
+
+      <section id="sufficient">
+         <h3>Sufficient Techniques</h3>
+
+
+         <ol>
+            <li>
+                CSS: Using scroll-padding to ensure a sticky header does not obscure the focused item (Potential future technique).
+            </li>
+         </ol>
+
+      </section>
+
+      <section id="advisory">
+         <h3>Additional Techniques (Advisory)</h3>
+
+      </section>
+
+      <section id="failure">
+         <h3>Failures</h3>
+         <ol>
+            <li>
+
+            </li>
+         </ol>
+      </section>
+
+   </section>
+
+</body>
+</html>