Skip to content

Commit 3ca1383

Browse files
Editorial changes to 7
SHA: a82e2e6 Reason: push, by jasonjgw Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent e520929 commit 3ca1383

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

index.html

+1-1
Original file line numberDiff line numberDiff line change
@@ -465,7 +465,7 @@ <h1 id="title" class="title">Collaboration Tools Accessibility User Requirements
465465
</li>
466466
<li><strong>REQ 19A:</strong> 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>
467467
<li><strong>REQ 19B:</strong> 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 accomplish the same purpose.</li>
468-
<li><strong>REQ 19C:</strong>Make collaborative features available via an <abbr title="application programming interface">API</abbr> to allow interoperability with tools with which the user may already be familiar, and which may better satisfy a person's specific accessibility-related needs. For example, a revision control system could interoperate via an <abbr>API</abbr> with a user's chosen text editor or integrated development environment.</li>
468+
<li><strong>REQ 19C:</strong> Make collaborative features available via an <abbr title="application programming interface">API</abbr> to allow interoperability with tools with which the user may already be familiar, and which may better satisfy a person's specific accessibility-related needs. For example, a revision control system could interoperate via an <abbr>API</abbr> with a user's chosen text editor or integrated development environment.</li>
469469
</ul>
470470
<div class="note" role="note" id="issue-container-generatedID-3"><div role="heading" class="note-title marker" id="h-note-3" aria-level="3"><span>Note</span></div><aside class="">
471471
<p>Provision of an <abbr>API</abbr> does not diminish the importance of ensuring that user interfaces provided by the application satisfy accessibility requirements. Nor is REQ 19C applicable to all collaborative environments. For example, some applications are highly dependent on editing functions specific to the tool itself, and should not be expected to interoperate with external editors.</p>

0 commit comments

Comments
 (0)