Various updates to requirements doc (#732)

WilcoFiers · github-actions[bot] · WilcoFiers · commit adbf91b361da · 2024-04-02T10:33:30.000Z
SHA: 570db02 Reason: push, by alastc Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
diff --git a/requirements/index.html b/requirements/index.html
@@ -99,7 +99,7 @@
 </style>
         
 	
-<meta name="revision" content="6dbf658ac3e4516f244e81234078b58c37c53812">
+<meta name="revision" content="570db026d5f5f01befb7fc9089bce9dfa86b9515">
 <meta name="description" content="The Requirements for W3C Accessibility Guidelines (WCAG) 3.0 documentation is the next phase of development of the next major upgrade to accessibility guidelines. WCAG 3.0 will be the successor to the Web Content Accessibility Guidelines (WCAG) 2 series. The Silver Task Force of the Accessibility Guidelines Working Group and the W3C Silver Community group have partnered to incubate the needs, requirements, and structure for the new accessibility guidance. To date, the group  has:">
 <style>
 var{position:relative;cursor:pointer}
@@ -151,16 +151,16 @@
   "github": "w3c/silver",
   "maxTocLevel": 4,
   "lint": false,
-  "gitRevision": "6dbf658ac3e4516f244e81234078b58c37c53812",
-  "publishISODate": "2024-03-21T00:00:00.000Z",
-  "generatedSubtitle": "W3C Editor's Draft 21 March 2024"
+  "gitRevision": "570db026d5f5f01befb7fc9089bce9dfa86b9515",
+  "publishISODate": "2024-04-02T00:00:00.000Z",
+  "generatedSubtitle": "W3C Editor's Draft 02 April 2024"
 }</script>
 <link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED"></head>
 	<body class="h-entry informative"><div class="head">
     <p class="logos"><a class="logo" href="https://www.w3.org/"><img crossorigin="" alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72">
   </a></p>
     <h1 id="title" class="title">Requirements for WCAG 3.0</h1> 
-    <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2024-03-21">21 March 2024</time></p>
+    <p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2024-04-02">02 April 2024</time></p>
     <details open="">
       <summary>More details about this document</summary>
       <dl>
@@ -354,9 +354,9 @@ <h1 id="title" class="title">Requirements for WCAG 3.0</h1>
 					
 					<p>There are several areas for exploration in how conformance can work. These opportunities may or may not be incorporated. They need to work together, and that interplay will be governed by the design principles</p>
 					<ul>
-						<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is quite clear and measurable. Others, far less so. Some needs of people with disabilities, especially cognitive and low vision disabilities, are not well served by guidance that can only be measured by a true/false statement. If we allow multiple means of measurement, in addition to true/false statements, then we may include new accessibility guidance that benefits groups that may have been underserved in the past.</li>
-						<li><strong>Task-Based Assessment</strong>: Moving away from strictly web pages and web sites as a collection of web pages, WCAG 3.0 could set the scope of conformance as a comprehensive set of tasks defined by the author of the site or application. A properly marked up button doesn't help anybody if the user can't complete the task at hand. Task-based assessment allows flexibility for the conformance of complex applications that are not conducive to component/tag assessment or full-page assessment.</li>
-						<li><strong>Accessibility Supported</strong>: As technologies evolve, the interoperability of content, user agents, and assistive technology will continue to blur. Interoperability may be affected by any number of factors outside of the control of the author and publisher of digital content. WCAG 3.0 can include advice to user agents and assistive technology developers. Authors are not responsible for interoperability problems beyond a reasonable effort.</li>
+						<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is best expressed as a true/false statement. Others far less so. There are needs of people with disabilities, especially cognitive and low vision disabilities, that are better captured by a different type of measurement. WCAG 3.0 can include multiple means of measurement, in addition to true/false statements, allowing inclusion of more accessibility guidance.</li>
+						<li><strong>Scope Options</strong>: WCAG 3.0 conformance could include web pages, web sites, page sections, individual components, and conformance based on a set of tasks as defined by the author of the site or application. A task-based assessment would allow flexibility for conformance of complex applications that go beyond component/tag assessment or full-page assessment.</li>
+						<li><strong>Accessibility Supported</strong>: As the technologies advance, the lines between content, user agents, and assistive technology will continue to shift and blur. Interoperability may be affected by any number of factors outside of the control of the author and publisher of digital content. WCAG 3.0 can include advice to user agents and assistive technology developers. WCAG 3 does not intend to make authors responsible for interoperability problems beyond a reasonable effort.</li>
 					</ul>
 				</section>
 				<section id="opportunities_maintenance"><div class="header-wrapper"><h3 id="x2-3-maintenance"><bdi class="secno">2.3 </bdi>Maintenance</h3><a class="self-link" href="#opportunities_maintenance" aria-label="Permalink for Section 2.3"></a></div>
@@ -461,9 +461,8 @@ <h1 id="title" class="title">Requirements for WCAG 3.0</h1>
 	 </section>
           <section id="readability"><div class="header-wrapper"><h3 id="x4-5-readability"><bdi class="secno">4.5 </bdi>Readability</h3><a class="self-link" href="#readability" aria-label="Permalink for Section 4.5"></a></div>
             
-	    <p>The core guidelines are understandable by a non-technical audience. Text and presentation are usable and understandable through the use of plain language, structure, and design. They link to instruction videos, illustrations, and how-to where available.  Creation of new videos and illustrations are outside the scope of this project at this time. 
-</p>
-	 </section>
+            <p>The core guidelines are understandable by a non-technical audience. Where technical guidance is necessary, a plain language alternative or summary will be provided. Text and presentation are usable and understandable through the use of plain language, structure, and design. They link to instruction videos, illustrations, and how-to where available.  Creation of new videos and illustrations are outside the scope of this project at this time.</p>
+          </section>
           <section id="regulatory-environment"><div class="header-wrapper"><h3 id="x4-6-regulatory-environment"><bdi class="secno">4.6 </bdi>Regulatory Environment</h3><a class="self-link" href="#regulatory-environment" aria-label="Permalink for Section 4.6"></a></div>
             
 	    <p>The Guidelines provide broad support, including</p>
