Adding PK's wirte-up of Challenge #5 to Abstract.

conformance-challenges/index.html

@@ -39,12 +39,19 @@
 			This document focuses primarily on challenges to large, highly complex, dynamic sites.  
 			Other efforts in WAI are looking at different aspects of conformance for other types of sites.</p>
 
-		<p>The challenges covered broadly fall into four main areas:</p>
+		<p>The challenges covered broadly fall into five main areas:</p>
             <ol>
 		    <li>Numerous provisions need human involvement to test and verify conformance, which is especially challenging to scale for <a>large websites</a> and for <a>dynamic websites</a>;</li>
 			    <li>Large and dynamic sites with their changing permutations may be difficult to validate;</li>
 			<li>Third parties frequently add and change content on large and dynamic sites;</li>
                 <li>Applying a web-based, and page-based conformance model can be challenging to do for non-web Information and Communications Technologies (ICT).</li>
+<li>The centrality of <q>Accessibility Supported</q> in the many provisions
+tied to use with assistive technologies and platform accessibility
+features, combined with the lack of definition of what constitutes
+Accessibility Supported, further exacerbates the need for expert
+human judgement (\#1 above), as well as potential different and
+non-overlapping sets of these features used when including 3rd
+party content (\#3 above).</li>
             </ol>
 	    <p>The purpose of this document is to help understand those challenges more holistically, and explore approaches for mitigating them so that we can address such
 	    challenges more fully in future accessibility guidelines including the forthcoming <a href="https://www.w3.org/WAI/wcag3">W3C Accessibility Guidelines (WCAG 3.0)</a> (now in early development) where the <a href="https://www.w3.org/2019/12/ag-charter.html#scope">W3C Working Group Charter</a> expressly anticipates a new conformance model.</p>
@@ -257,11 +264,11 @@ <h3>Silver Research Findings</h3>
 		yield consistent conclusions: <q>Regardless of proficiency,
 			there is a significant gap in how any two human
 			auditors will identify a success or fail of criteria.
-			... Ultimately, there is variance between: any two
-			auditors; ... Because there&apos;s so much room for human
+			&#x2026; Ultimately, there is variance between: any two
+			auditors; &#x2026; Because there&apos;s so much room for human
 			error, an individual may believe they&apos;ve met a specific
 			conformance model when, in reality, that■s not the
-			case. ... There isn&apos;t a standardized approach to how
+			case. &#x2026; There isn&apos;t a standardized approach to how
 			the conformance model applies to success criteria at
 			the organizational level and in specific test case
 			scenarios.</q></li>
@@ -473,7 +480,7 @@ <h2>Challenge #5: Accessibility Supported</h2>
 		    <h3>Silver Research Findings</h3>
 
 		    <p>Silver concluded that <q>Accessibility Supported is a conformance requirement
-of WCAG 2 that is poorly understood and incompletely implemented, ... i.e. the role
+of WCAG 2 that is poorly understood and incompletely implemented, &#x2026; i.e. the role
 of AT in assessing conformance.</q> See <a href="#at-supported">additional details in Appendix C</a> below.
 		    </p>
 
@@ -484,7 +491,7 @@ <h3>Mitigations</h3>
 
 		<p>We know of no useable mitigations to achieve the <q>Accessibility Supported</q> conformance requirement for public facing web sites. <a href="https://www.w3.org/TR/WCAG-EM/#step1c">WCAG-EM's Second Note</a> suggests that: <q>For some websites in closed networks, such as an intranet website, where both the users and the computers used to access the website are known, this baseline may be limited to the operating systems, web browsers and assistive
 technologies used within this closed network.</q> It continues saying: <q>However, in most cases this baseline is ideally broader to cover the majority of current user agents used by people with disabilities in any applicable particular geographic region and
-language community.</q> Beyond placing the responsibility on the evaluator to establish this baseline, <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head">Note 5 in Understanding Conformance 2.0</a> suggests that: <q>One way for authors to locate uses of a technology that are accessibility supported would be to consult compilations of uses that are documented to be accessibility supported. ... Authors, companies, technology vendors, or others may document accessibility-supported ways of using Web content technologies.</q> Unfortunately, we know of no such public repository.
+language community.</q> Beyond placing the responsibility on the evaluator to establish this baseline, <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-accessibility-support-head">Note 5 in Understanding Conformance 2.0</a> suggests that: <q>One way for authors to locate uses of a technology that are accessibility supported would be to consult compilations of uses that are documented to be accessibility supported. &#x2026; Authors, companies, technology vendors, or others may document accessibility-supported ways of using Web content technologies.</q> Unfortunately, we know of no such public repository.
 	</p>
 	</section>
 	</section>
@@ -976,7 +983,7 @@ <h4>Audio Control
 
 <p>Where non-web software contains audio, especially audio that automatically
 plays in certain circumstances (e.g. making a ringing sound to indicate an
-incoming call) ... </p>
+incoming call) &#x2026; </p>
 <p><strong>EDITOR&apos;S NOTE</strong><br /> Section content yet to be written.</p>
 
 </section>