further alignment with accName description updates

index.html

@@ -6100,30 +6100,42 @@ Text-level Element Accessible Name Computation
     
     
       Accessible Description Computation
-      An accessible description MAY be provided to any HTML element that is a valid child of the `body` element.
+      
+        An accessible description MAY be provided to any HTML element that is a valid child of 
+        the `body` element. The following list represents the order of precedence for user agents to compute the 
+        accessible description of an element. As defined by 
+        Accessible Name and Description Computation: Description Computation , 
+        user agents MUST use the first applicable description source, even if its use results in an empty description.
+      
       
         
-          If the element has an `aria-describedby` or `aria-description` attribute the accessible description is to be calculated using the algorithm defined in Accessible Name and Description: Computation and API Mappings.
+          If the element has an `aria-describedby` or 
+          `aria-description` attribute refer to the computation conditions defined in 
+          Accessible Name and Description: Computation and API Mappings.
         
         
           Otherwise, if the accessible description is still empty, and the element is:
           
             
-              a `table` element which has a child `caption` element, use the subtree of the first `caption` element if it was not used as the accessible name.
+              a `table` element which has a child `caption` element, use the 
+              text equivalent computation of the subtree of the first `caption` element if it 
+              was not used as the accessible name. 
             
             
-              a `summary` element, use the element's subtree if it was not used as the accessible name.
+              a `summary` element, use the text equivalent computation of its subtree if it was not 
+              used as the accessible name.
             
             
-              an `input` element whose `type` attribute is the `button`, `submit` or `reset` state, and it has a `value` attribute, then use the content of the attribute if it was not used as the accessible name.
+              an `input` element whose `type` attribute is the `button`, `submit` or `reset` state, and it has a `value` attribute, then use the flat string 
+              of the attribute if it was not used as the accessible name.
             
           
          
         
-          Otherwise, use the content of the `title` attribute if it was not used as the accessible name for the element.
+          Otherwise, use the flat string of the `title` attribute if it was not used as the accessible name for the element.
         
         
-          If none of the above yield a usable text string there is no accessible description.
+          If none of the above are applicable, there is no accessible description.
         
       
     
@@ -6136,7 +6148,8 @@ Change Log
       
         Substantive changes since moving to the Accessible Rich Internet Applications Working Group (03-Nov-2019)
         
-          19-Jul-2022: Update `address` element to be mapped to `role=group`. See GitHub PR 420
+          28-Nov-2022: Simplify accessible description computation section. See GitHub PR 444.
+          19-Jul-2022: Update `address` element to be mapped to `role=group`. See GitHub PR 420.
           03-Apr-2022: Update `aside` mappings based on its nesting context. See GitHub PR 350.
           06-Mar-2022: Update the following elements to map to the `generic` role: `a no href`, `footer` not scoped to `body`, `header` not scoped to `body`, `samp`, `span`. See GitHub PR 364.
           06-Feb-2022: Update `mark` to point to Core AAM mapping for the role. See GitHub Issue 316.