Merge pull request #143 from w3c/How-to-updates-2024-11

Clear meaning goal update

how-to/outcomes/clear-meaning/index.md

@@ -5,12 +5,12 @@ layout: outcome.html
 ## Goal
 
 To help people understand text:
-* Use literal language, or 
-* Explain the implied meaning of non-literal language.
+* Use clear, unambiguous language, or 
+* Explain the implied meaning of ambiguous language.
 
-Making non-literal or figurative language easier to understand helps people with cognitive disabilities as well as neurodivergent people, such as those who are autistic and may be so focused on the literal meaning that they may not notice the implied meaning.
+Making ambiguous content (including non-literal or figurative language) easier to understand helps people with cognitive disabilities as well as neurodivergent people, such as those who are autistic and may be so focused on the literal meaning that they may not notice the implied meaning.
 
-Explaining or avoiding non-literal language can also help:
+Explaining or avoiding ambiguous language can also help:
 * Non-native language speakers
 * People of different ages or generations
 * People from different cultural backgrounds

how-to/outcomes/focus-appearance/index.md

@@ -21,12 +21,7 @@ The keyboard focus must have a sufficient visual indicator.
 For each focusable item:
 
 1. Is the user-agent default focus indicator used? (Prerequisite)
-    1. Yes, the [user-agent default indicator](methods/default-focus-indicator) is used AND the *accessibility support set* incorporates [Using the default focus indicator and checking contrast](methods/default-focus-indicator-check-contrast) and checking contrast. Stop.
-    2. No, continue.
-
-
-2. Is the user-agent default focus indicator used, and meets contrast across backgrounds? (Baseline)
-    1. Yes, indicator must meet [Using the default focus indicator and checking contrast](methods/default-focus-indicator-check-contrast). Stop. 
+    1. Yes, the [user-agent default indicator](methods/default-focus-indicator) is used AND the *accessibility support set* meets [Custom focus indicators](methods/custom-focus-indicator). Stop.
     2. No, continue.
 
 

how-to/outcomes/text-alternatives/index.md

@@ -24,7 +24,7 @@ If there is no information conveyed by the image, the user's assistive technolog
    2. Yes, continue.
 
 2. Is the image presented in a way that is available to user agents and assistive technology? (Prerequisite)
-   1. Yes, image must meet [@@@ programatic availability] image AND the [accessibility support set] incorporates [Equivalent text alternatives are available for images that convey content](methods/equivalent-alternative-text). Stop.
+   1. Yes, image must meet _Image is programmatically determinable_ AND the _accessibility support set_ incorporates [Equivalent text alternatives are available for images that convey content](methods/equivalent-alternative-text). Stop.
    2. No, continue.
 
 3. Is an equivalent text alternative available for the image? (Baseline)