You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<sectionid="version-control-changes"><divclass="header-wrapper"><h3id="x4-1-suggested-changes"><bdiclass="secno">4.1 </bdi>Suggested changes</h3><aclass="self-link" href="#version-control-changes" aria-label="Permalink for Section 4.1"></a></div>
408
408
409
409
<ul>
410
-
<li><strong>User Need 11:</strong> Assistive technology users need to be able to read the text with information included about <em>suggested changes</em> (i.e., insertions, deletions or formatting modifications proposed by collaborators). Assistive technology users and those with learning or cognitive disabilities also need to be able to read content being edited without the distraction of insertion and deletion annotations.</li>
411
-
<li><strong>REQ 11A:</strong> Provide a mode of operation in which
412
-
details of insertions, deletions and formatting changes are appropriately presented
413
-
as collaborators read the content. These details should include time stamps and identification of who made the change together with any annotations the editor may have provided by way of explanation.</li>
414
-
<li><strong>REQ 11B:</strong> Provide a mode of operation in which users can read the unmodified content, or if they prefer, the revised content with suggested changes applied, without any annotations indicating revisions.</li>
415
-
<li><strong>User Need 12:</strong>All users, and particularly u sers with color blindness need to be able to distinguish insertions, deletions, and unaltered text effectively.</li>
410
+
<li><strong>User Need 11:</strong> Assistive technology users need to be able to read the text with information included about <em>suggested changes</em> (i.e., insertions, deletions, or formatting modifications proposed by collaborators). Assistive technology users and those with learning or cognitive disabilities also need to be able to read content being edited without the distraction of insertion and deletion annotations.</li>
411
+
<li><strong>REQ 11A:</strong> Provide a mode of operation in which details of insertions, deletions, and formatting changes are appropriately presented as collaborators read the content. These details should include time stamps and identification of who made the change together with any annotations the editor may have provided by way of explanation.</li>
412
+
<li><strong>REQ 11B:</strong> Provide a mode of operation in which users can read the unmodified content, or if they prefer, the revised content, with suggested changes applied, without any annotations indicating revisions.</li>
413
+
<li><strong>User Need 12:</strong>All users, and particularly users with color blindness need to be able to distinguish insertions, deletions, and unaltered text effectively.</li>
416
414
<li><strong>REQ 12:</strong> Provide distinctions over and beyond just color to identify inserted and deleted text as required by WCAG 2.2 <ahref="https://www.w3.org/WAI/WCAG22/Understanding/use-of-color">Success Criterion 1.4.1: Use of Color</a>.</li>
<sectionid="summation"><divclass="header-wrapper"><h3id="x4-3-summarizations"><bdiclass="secno">4.3 </bdi>Summarizations</h3><aclass="self-link" href="#summation" aria-label="Permalink for Section 4.3"></a></div>
427
425
428
426
<ul>
429
-
<li><strong>User Need 14:</strong> Users with learning or cognitive disabilities, and users of assistive technologies sometimes need support in identifying revisions and understanding their effects.</li>
430
-
<li><strong>REQ 14A:</strong> Provide, with timestamp and author indication, a mechanism to identify and summarize a series of changes to some portion of content.</li>
431
-
<li><strong>REQ 14B:</strong> Provide, with timestamp and author indication, a mechanism to identify and summarize individual comment threads.</li>
432
-
<li><strong>REQ 14C:</strong> Provide, if technically feasible, a mechanism allowing any user automatically to generate a summary for themselves of content or of a comment thread at any time. Project editors should have the ability to revise and commit a summary to the content in collaborative development as a permanent feature of the collaborative effort.</li>
433
-
<li><strong>REQ 14d:</strong> Whenever <abbrtitle="artificial intelligence">AI</abbr> rather than human authoring is used to generate summaries, indicate that the summary was auto-generated, but also provide the ability for an editor to edit or replace the auto-generated summary. Indicate any special circumstances, e.g. <q>An auto-generated plain language summary.</q></li>
427
+
<li><strong>User Need 14:</strong> Users with learning or cognitive disabilities and users of assistive technologies sometimes need support in identifying revisions and understanding their effects.</li>
428
+
<li><strong>REQ 14A:</strong> Provide, with timestamp and author indication, a mechanism to identify and summarize a series of changes to some portion of content.</li>
429
+
<li><strong>REQ 14B:</strong> Provide, with timestamp and author indication, a mechanism to identify and summarize individual comment threads.</li>
430
+
<li><strong>REQ 14C:</strong> Provide, if technically feasible, a mechanism allowing any user automatically to generate a summary for themselves of content or a comment thread at any time. Project editors should have the ability to revise and commit a summary to the content in collaborative development as a permanent feature of the collaborative effort.</li>
431
+
<li><strong>REQ 14d:</strong> Whenever <abbrtitle="artificial intelligence">AI</abbr> rather than human authoring is used to generate summaries, indicate that the summary was auto-generated, but also provide the ability for an editor to edit or replace the auto-generated summary. Indicate any special circumstances, e.g. <q>an auto-generated plain language summary.</q></li>
0 commit comments