Divide the existing requirement in section 9 into two separate requir…

…ements, and clarify them as discussed at the 3 April RQTF meeting. SHA: 42001a7 Reason: push, by jasonjgw Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
w3c · Apr 3, 2024 · bbe8009 · bbe8009
1 parent 088c4f1
commit bbe8009
Showing 1 changed file with 5 additions and 4 deletions.
diff --git a/index.html b/index.html
@@ -149,15 +149,15 @@
   "group": "apa",
   "github": "w3c/ctaur",
   "maxTocLevel": 4,
-  "publishISODate": "2024-04-01T00:00:00.000Z",
-  "generatedSubtitle": "W3C Editor's Draft 01 April 2024"
+  "publishISODate": "2024-04-03T00:00:00.000Z",
+  "generatedSubtitle": "W3C Editor's Draft 03 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">Collaboration Tools Accessibility User Requirements</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-04-01">01 April 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-03">03 April 2024</time></p>
     <details open="">
       <summary>More details about this document</summary>
       <dl>
@@ -459,7 +459,8 @@ <h1 id="title" class="title">Collaboration Tools Accessibility User Requirements
       <p>To facilitate effective collaboration, applications should be designed to respect conventions of user interface design that are likely to be expected by users, including those who have disabilities.</p>
       <ul>
         <li><em>User Need 19:</em> Users with learning or cognitive disabilities or who use assistive technologies need to be able to learn collaboration tools efficiently, including software with which they are unfamiliar and which is necessary to the task at hand.</li>
-        <li><em>REQ 19:</em> Support the user interface conventions and accessibility features of the user's operating system, desktop environment, user agent and assistive technology. For example, some assistive technologies, notably screen readers, provide commands and features for interacting with comments and revisions, which should be supported by collaboration tools to which these functions are applicable.</li>
+        <li><em>REQ 19A:</em> In implementing collaboration features, follow established user interface conventions and design patterns. For example, use conventional terminology, labels, or icons for functionality that may be familiar to users.</li>
+        <li><em>REQ 19B:</em> Support the accessibility-related features of the user's operating system, user agent, and assistive technology. For example, some assistive technologies, such as screen readers, have features designed specifically for reading comments and suggested changes in textual content, which should be supported instead of defining application-specific functionality or keyboard commands that achieve the same purpose.</li>
       </ul>
     </section>