First fixes under Challenge #5; added Silver Findings under Challenge #3

 with hyperlink to Appendix C.

conformance-challenges/index.html

@@ -331,6 +331,13 @@ <h3>Treatment of 3rd party content and Statements of Partial Conformance</h3>
 <p>A statement of partial conformance doesn't address the underlying challenge of improving the usability of 3rd party content.  While it might allow a web page/website visitor to be forewarned in advance that they should 
 anticipate encountering inaccessible content, it does little to practically enable large sites to address such concerns.</p>
 
+	<section class="silver">
+		    <h3>Silver Research Findings</h3>
+
+		    <p>Silver cited <q>Third parties documents, applications and services</q> among its list of conformance related problem statements. See <a href="#3rd">the reference in Appendix C</a> below.
+		    </p>
+
+	</section>
 <div class="mitigation">
 	<h3>Mitigations</h3>
 	<p>There are several approaches to the challenge of 3rd
@@ -429,8 +436,8 @@ <h2>Challenge #5: The <q>Accessibility Supported</q> Requirement</h2>
 	<section class="silver">
 		    <h3>Silver Research Findings</h3>
 
-		    <p>Silver concluded <a>Accessibility Supported</a> is a conformance requirement
-of WCAG 2 that is poortly understood and incompletely implemented, i.e. the role
+		    <p>Silver concluded that <q>Accessibility Supported is a conformance requirement
+of WCAG 2 that is poorly understood and incompletely implemented</q>, i.e. the role
 of AT in assessing conformance. See <a href="#at-supported">additional details in Appendix C</a> below.
 		    </p>
 
@@ -1153,7 +1160,7 @@ <h4>Definition of Conformance</h4>
                         <li>Non-Interference: Technologies that are not accessibility supported can be used, as long as all the information is also available using technologies that are accessibility supported and as long as the non-accessibility-supported material does not interfere.</li>
 		    </ol></blockquote>
                 </section>
-                <section>
+                <section id="3rd">
                     <h4>Themes from Research</h4>
                     <ul>
                         <li>No monitoring process to test the accuracy of WCAG compliance claims (Keith et al., 2012)</li>
@@ -1164,6 +1171,7 @@ <h4>Themes from Research</h4>
                                 <li>Tension between accessibility and design</li>
                             </ul>
                         </li>
+
                         <li>Specific success criteria for failure - 1.1.1 , 2.2., 4.1.2 (Keith et al., 2012)</li>
 			<li><q>Reliably Human Testable,</q> <q>not reliably testable</q> <a href="http://www.researchgate.net/publication/235339930_Is_accessibility_conformance_an_elusive_property_A_study_of_validity_and_reliability_of_WCAG_20">Is Accessibility Conformance an Elusive Property? (Brajnik et al. 2012)</a>, found the average agreement was at the 70-75% mark, while the error rate was around 29%.
                             <ul>