WCAG 2.2: Understanding 2.4.12 Focus Not Obscured (Enhanced) - Wrong …

…reference to Focus Appearance (#3753)

Closes #3722

Fixes:
- Added reference to 1.4.11 Focus Appearance, since it is also involved;
- Fixed wrong SC reference (2.4.11 Focus Appearance with 2.4.13 Focus
Appearance);
- Updated herf attribute to reflect new link guideline structure;
- Fixed typo "the the".

---------

Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk>

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

@@ -22,7 +22,7 @@ <h2>Intent of Focus Not Obscured (Enhanced)</h2>
   <p>The intent of this Success Criterion is to ensure that the item receiving keyboard focus is always visible in the user's viewport. For sighted people who rely on a keyboard (or on a device that operates through the keyboard interface, such as a switch or voice input), knowing the current point of focus is critical. The component with focus signals the interaction point on the page. Where users cannot see the item with focus, they may not know how to proceed, or may even think the system has become unresponsive.</p>
   <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="../understanding/focus-appearance.html">2.4.11 Focus Appearance</a>. When a focus indicator can be covered by a semi-opaque component, the the focus indicator should be assessed against 2.4.11. 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>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>
 </section>
 <section id="benefits">
   <h2>Benefits of Focus Not Obscured (Enhanced)</h2>