From 187be37ea11f5392f7472a4a1e8abcf4c6f3150b Mon Sep 17 00:00:00 2001
From: Alastair Campbell <ac@alastc.com>
Date: Thu, 21 Mar 2024 10:52:45 +0000
Subject: [PATCH] Adding a requirement - backwards compatibility (not) (#730)

SHA: eb9e418fd86bfe5014d2d0240aa6f1558432d07a
Reason: push, by alastc

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
---
 requirements/index.html | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/requirements/index.html b/requirements/index.html
index d1768cd0..e2af2362 100644
--- a/requirements/index.html
+++ b/requirements/index.html
@@ -99,7 +99,7 @@
 </style>
         
 	
-<meta name="revision" content="c2f15641d206c6cf845d0edc3dd95e9ab870ad1f">
+<meta name="revision" content="eb9e418fd86bfe5014d2d0240aa6f1558432d07a">
 <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,7 +151,7 @@
   "github": "w3c/silver",
   "maxTocLevel": 4,
   "lint": false,
-  "gitRevision": "c2f15641d206c6cf845d0edc3dd95e9ab870ad1f",
+  "gitRevision": "eb9e418fd86bfe5014d2d0240aa6f1558432d07a",
   "publishISODate": "2024-03-21T00:00:00.000Z",
   "generatedSubtitle": "W3C Editor's Draft 21 March 2024"
 }</script>
@@ -369,6 +369,9 @@ <h1 id="title" class="title">Requirements for WCAG 3.0</h1>
 						<li><strong>Evolving Technology</strong>: WCAG 3.0 needs a flexible design that can be updated as new technologies emerge, assistive technologies improve, and changing technologies produce new barriers for people with disabilities. Accessibility guidance and all supporting documentation should anticipate common scenarios like new technology and the introduction of new modalities like surface reaction and ultrahaptics. As content technology evolves, it must be re-evaluated against assistive technology for compatibility. Likewise, as assistive technology evolves or emerges, it must be evaluated against the backward compatibility of various content technology.</li>
 						<li>
 							<strong>Governance</strong>: Utilize tools that allow interested parties to predict when issues important to them are being discussed. Maintain a backlog that reflects issues along with their status. </li>
+						<li>
+							<strong>Backwards compatibility</strong> The WCAG 3 guidelines will take a cautious approach to backwards compatibility to early versions of WCAG 3.  After the first publication of WCAG 3 guidance and conformance model the guidelines aim to be backwards compatible. However, it will not be bound to backwards compatibility if a substantially more accessible outcome can be achieved. Where there are backwards-incompatible changes, the changes will be highlighted in the supplementary materials so that users of the guidelines know exactly what has changed.
+						</li>
 					</ul>
 				</section>
 				<section id="opportunities_issue-severity"><div class="header-wrapper"><h3 id="x2-4-issue-severity"><bdi class="secno">2.4 </bdi>Issue Severity</h3><a class="self-link" href="#opportunities_issue-severity" aria-label="Permalink for Section 2.4"></a></div>