🤖 Deploy to GitHub Pages: 27bc149 from branch refs/heads/main

w3cgruntbot · w3cgruntbot · commit 42d47c3640a7 · 2025-05-20T16:55:31.000Z
diff --git a/conformance-challenges/index.html b/conformance-challenges/index.html
@@ -125,7 +125,7 @@
   "publishISODate": "2025-05-20T00:00:00.000Z",
   "generatedSubtitle": "Editor's Draft 20 May 2025"
 }</script><link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2016/W3C-ED"></head>
-    <body class="h-entry informative"><div class="head">
+    <body class="h-entry informative toc-inline"><div class="head">
     <a class="logo" href="https://www.w3.org/"><img alt="W3C" width="72" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C"></a> <h1 id="title" class="title">Challenges with Accessibility Guidelines Conformance and Testing, and Approaches for Mitigating Them</h1>
     
     <h2>
diff --git a/understanding/error-identification.html b/understanding/error-identification.html
@@ -182,8 +182,8 @@ <h2>Intent</h2>
          that user agents or assistive technologies can use to identify an error and provide
          error information to the user. For example, certain technologies can specify that
          the user's input must not fall outside a specific range, or that a form field is required.
-         Currently, few technologies support this kind of programmatic information, but this
-         success criterion does not require, nor prevent it.</p>
+         This type of programmatic information is not required for this success criterion, but may be covered
+         by other criteria such as <a href="name-role-value">4.1.2 Name, Role, Value</a>.</p>
 
       <p>It is perfectly acceptable to indicate the error in other ways such as through the use of an image,
          color, or other visual indicator, in addition to the text description.</p>
