Skip to content

Commit

Permalink
Correct markup validity error detected by the validator.
Browse files Browse the repository at this point in the history
SHA: a9b68a9
Reason: push, by jasonjgw

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
jasonjgw and github-actions[bot] committed Mar 2, 2024
1 parent c4b8993 commit 69fe9f8
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,7 @@
"generatedSubtitle": "W3C Editor's Draft 02 March 2024"
}</script>
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED"></head>
<body class="h-entry informative toc-inline"><div class="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>
Expand Down Expand Up @@ -301,13 +301,13 @@ <h1 id="title" class="title">Collaboration Tools Accessibility User Requirements
<dd>Some collaborative environments support <em>access controls</em>, allowing restrictions to be imposed on modification of part or all of the content. Permission to modify content may be granted on a granular basis to specific individuals or to groups of users. For example, in a collaborative tool for creating fillable forms, some users may only be allowed to change the values of input fields (i.e., to complete a form), whereas others may be free to edit any aspect of the document, including the addition, deletion and rearrangement of form fields.</dd>
</dl>

<p>Collaboration tools differ widely in the nature of content that may be edited. They also differ widely in the user interfaces presented to users. For example:cl
</p><ul>
<p>Collaboration tools differ widely in the nature of content that may be edited. They also differ widely in the user interfaces presented to users. For example:</p>
<ul>
<li>Word processors typically provide a <q>what you see is what you get</q> (<abbr title="what you see is what you get">wysiwyg</abbr>) interface based on a rendered view of the content.</li>
<li>Editors designed for source code or markup language text development do not. In the latter case, indentation and syntax highlighting may be the only visual cues provided to the structure of the code or markup available in the editing environment.</li>
<li>Candidate video renditions may be played in side by side windows for purposes of comparison and editing decisioning.</li>
<li>By its very nature audio alternatives must be played serially, and their distinctions remembered in the comparison and decisioning process.</li>
</ul><p></p>
</ul>
<p>Collaboration tools that support editing of graphics, mathematical notation, or other content types are also within the scope of this document. However, only the collaboration-related aspects of such systems are addressed here. The accessibility issues arising from creating and editing these types of content are not considered, as they are separate problems from the user needs associated with the collaborative features of the tools.</p>
<p>Nevertheless it is important that collaborative tools support the full range of editing functions associated with making web content accessible. Among others this would include the ability to add
headings, provide alternative text for images and add captions to videos.</p>
Expand Down

0 comments on commit 69fe9f8

Please sign in to comment.