Suggested additional note for focus-not-obscured (AAA), tweak AA note (#4403)

AAA version of the note that was added for AA in
#4104

Includes a small tweak to the AA note as well regarding focus indicator
not being *fully* obscured

---------

Co-authored-by: Mike Gower <[email protected]>

Author: patrickhlauke

understanding/22/focus-not-obscured-enhanced.html

@@ -23,6 +23,7 @@ <h2>Intent of Focus Not Obscured (Enhanced)</h2>
   <p>Typical types of content that can overlap focused items are sticky footers, sticky headers, and non-modal dialogs. As a user tabs through the page, these layers of content can hide the item receiving focus, along with its focus indicator.</p>
   <p>A notification implemented as sticky content, such as a cookie banner, will fail this success criterion if it partially covers a component receiving focus. Ways of passing include making the banner modal so the user has to dismiss the banner before navigating through the page, or using <a href="https://www.w3.org/TR/css-scroll-snap/#propdef-scroll-padding">scroll padding</a> so the banner does not overlap other content. Notifications that do not require user action could also meet this criterion by closing on loss of focus.</p>
   <p>Another form of obscuring can occur where light boxes or other semi-opaque effects overlap the item with focus. This form of obscuring is <em>not</em> in scope for this success criterion. While less than 100 percent opacity is not causing the component to be <q>visually hidden</q>, such semi-opaque overlaps may cause a failure of <a href="non-text-contrast">1.4.11 Non-text Contrast</a> and/or <a href="focus-appearance">2.4.13 Focus Appearance</a>. When a focus indicator can be covered by a semi-opaque component, the focus indicator should be assessed against 1.4.11 and 2.4.13. The intention in both situations is that the component receiving focus should never be obscured to the point a user cannot tell which item has focus.</p>
+  <p class="note">This criterion evaluates the focused <em>component</em>, rather than the focus <em>indicator</em>. The component itself does not include the focus indicator when checking that "no part of the component is hidden" - unless the focus indicator is inside the component, or focus is indicated by a change to the component itself. Although users benefit from both the component and the focus indicator (if external to the component) not being obscured when tracking the focus, for the purposes of this criterion only checking the component provides a clearer metric. However, if the focus indicator is fully obscured, it would likely fail <a href="focus-visible">2.4.7 Focus Visible</a>.</p>
 </section>
 <section id="benefits">
   <h2>Benefits of Focus Not Obscured (Enhanced)</h2>

understanding/22/focus-not-obscured-minimum.html

@@ -31,7 +31,7 @@ <h2>Intent of Focus Not Obscured (Minimum)</h2>
 
       <p>Another form of obscuring can occur where light boxes or other semi-opaque effects overlap the item with focus. While less than 100 percent opacity is not causing the component to be <q>entirely obscured</q>, such semi-opaque overlaps may cause a failure of <a href="../understanding/non-text-contrast.html">1.4.11 Non-text Contrast</a>. When a focus indicator can be covered by a semi-opaque component, the ability of the focus indicator to pass 1.4.11 should be evaluated (and pass) while the focus indicator is under the semi-opaque component. The intention in both situations is that the component receiving focus should never be obscured to the point a user cannot tell which item has focus.</p>
 
-      <p class="note">This criterion evaluates the focused <em>component</em>, rather than the focus <em>indicator</em>. The component itself does not include the focus indicator when checking that "the component is not entirely hidden" - unless the focus indicator is inside the component, or focus is indicated by a change to the component itself. Although users benefit from both the component and the focus indicator (if external to the component) not being obscured when tracking the focus, for the purposes of this criterion only checking the component provides a clearer metric. However, if the focus indicator is obscured, it would likely fail <a href="focus-visible">2.4.7 Focus Visible</a>.</p>
+      <p class="note">This criterion evaluates the focused <em>component</em>, rather than the focus <em>indicator</em>. The component itself does not include the focus indicator when checking that "the component is not entirely hidden" - unless the focus indicator is inside the component, or focus is indicated by a change to the component itself. Although users benefit from both the component and the focus indicator (if external to the component) not being obscured when tracking the focus, for the purposes of this criterion only checking the component provides a clearer metric. However, if the focus indicator is fully obscured, it would likely fail <a href="focus-visible">2.4.7 Focus Visible</a>.</p>
 
       <section id="Movable">
          <h3>User-movable content</h3>