Removed one WCAG version reference; made cfhanges to UN 7 and 8.

index.html

@@ -82,7 +82,7 @@ <h3>Collaboration tools and accessibility</h3>
 	<p>Thus when we talk about collaborative tools we must consider accessibility burdens imposed by their
 	concomitant complexity. In truth, collaborative tools are necessarily complex interfaces for all users, and not only persons with various disabilities. The salient point here is that a failure to design to accomodate persons with disabilities appropriately will inevitably prevent their participation in collaborative work. What constitutes challenging complexity for most users will inevitably become an insurmountable barrier for some persons with disabilities.</p>
 
-	<p>A fairly common accessibility failure is the use of arbitrary color to flag edits put forth by different collaborators. However, identifying collaborators only by colorization  violates WCAG 2.2 Success Criterion 1.4.1 as described below in <a href="#version-control-changes">User Need 11</a>.</p>
+	<p>A fairly common accessibility failure is the use of arbitrary color to flag edits put forth by different collaborators. However, identifying collaborators only by colorization  violates WCAG Success Criterion 1.4.1 as described below in <a href="#version-control-changes">User Need 11</a>.</p>
       </section>
       <section id="social">
 	      <h2>Social Considerations</h2>
@@ -107,7 +107,7 @@ <h2>Real-Time co-editing</h2>
       <ul>
         <li><strong>User Need 2:</strong> An assistive technology user needs to be informed in real time of changes to the content being made by collaborators.</li>
         <li><strong>REQ 2:</strong> Provide a mode of operation in which status messages inform the assistive technology user of insertions, deletions or formatting-related changes made by collaborators as they occur. Limiting these notifications to a content span currently focused by the user is also an advisable option.</li>
-        <li><strong>User Need 3:</strong> Users with learning or cognitive disabilities  and assistive technology users need the ability to read or edit without being distracted by status messages.</li>
+        <li><strong>User Need 3:</strong> Users with learning or cognitive disabilities  and assistive technology users need the ability to read or edit without being distracted or overwhelmed by status messages.</li>
         <li><strong>REQ 3:</strong> Provide a mode of operation in which status messages informing the user of the presence or activities of collaborators are suppressed. This may be achieved by allowing the user selectively to enable and disable specific types of status message, to messages relating to a specific span of content, or all such messages.</li>
         <li><strong>User Need 4:</strong> An assistive technology user needs the ability to track changes introduced by a specific collaborator as they are made.</li>
         <li><strong>REQ 4:</strong> Provide a function that moves and tracks user&apos;s
@@ -129,10 +129,10 @@ <h2>Annotations</h2>
       </ul>
       <p class="note">See <cite>Web Content Accessibility Guidelines (WCAG) 2.2</cite> [[wcag22]], success criterion 1.3.1.</p>
       <ul>
-        <li><strong>User Need 7:</strong> Assistive technology users need to be able to read text without being distracted by information about annotations.</li>
+        <li><strong>User Need 7:</strong> Assistive technology users need to be able to review content without being overwhelmed or distracted by information about annotations.</li>
         <li><strong>REQ 7:</strong> Provide a mode of operation in which information about annotations is suppressed. This mode might be activated by an application setting, such as a toggle switch controlling the presence or absence of annotations.</li>
         <li><strong>User Need 8:</strong> An assistive technology user needs to be able to navigate between annotations (from previous to next) and to obtain a navigable list of annotations (e.g., a list of comments in a word processor document or on a Web page), in order to read and respond to annotations efficiently.</li>
-        <li><strong>REQ 8:</strong> Provide navigation functions and a means of obtaining a list of all the annotations associated with the content.</li>
+        <li><strong>REQ 8:</strong> Provide navigation and content viewing functions and a means of obtaining a navigable list of all the annotations associated with the content.</li>
         <li><strong>User Need 9:</strong> Assistive technology users need to be able to control the amount of information presented about annotations to prevent becoming overwhelmed while they are reading, navigating and editing content.</li>
         <li><strong>REQ 9:</strong> Provide options for the user to limit the amount of detail presented as each annotation is encountered. For example, it should be possible to suppress presentation of metadata, or replies to comments, or to alert the user only to the presence of the annotation without presenting the metadata or comment text.</li>
         <li><strong>User Need 10:</strong> Assistive technology users and users with learning or cognitive disabilities sometimes need support in understanding and navigating annotations that represent comments organized as <em>threads</em> of conversation.</li>