Skip to content

Commit

Permalink
harmonize quote style
Browse files Browse the repository at this point in the history
  • Loading branch information
Michael Cooper committed Jul 6, 2023
1 parent 7370199 commit 55c8020
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions guidelines/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@
<p>See <a href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">WCAG 3 Introduction</a> for an introduction and links to WCAG technical and educational material.</p>
</section>
<section id="sotd">
<p>To comment, <a href="https://github.com/w3c/silver/issues/new">file an issue in the W3C silver GitHub repository</a>. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to <a href="mailto:public-agwg-comments@w3.org?subject=WCAG%203.0%20public%20comment">public-agwg-comments@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). In-progress updates to the guidelines can be viewed in the <a href="https://w3c.github.io/silver/guidelines/">public editors' draft</a>.</p>
<p>To comment, <a href="https://github.com/w3c/silver/issues/new">file an issue in the W3C silver GitHub repository</a>. The Working Group requests that public comments be filed as new issues, one issue per discrete comment. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to <a href="mailto:public-agwg-comments@w3.org?subject=WCAG%203.0%20public%20comment">public-agwg-comments@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-agwg-comments/">comment archive</a>). In-progress updates to the guidelines can be viewed in the <a href="https://w3c.github.io/silver/guidelines/">public editors’ draft</a>.</p>
</section>
<section class="informative">
<h2>Introduction</h2>
Expand Down Expand Up @@ -364,7 +364,7 @@ <h5>Test scopes</h5>

<p><dfn data-lt="item|unit" title="Smallest testable unit">Items</dfn> are the smallest testable unit. They may be interactive components such as a drop down menu, a link, or a media player. They may also be units of content such as a word, a phrase, a label or error message, an icon, or an image.</p>

<p><dfn data-lt="views" title="All content visually and programmatically available without a substantive change.">Views</dfn> include all content visually and programmatically available without a substantive change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a "screen" in a mobile app or a layer of web content – such as a modal. </p>
<p><dfn data-lt="views" title="All content visually and programmatically available without a substantive change.">Views</dfn> include all content visually and programmatically available without a substantive change. Conceptually, views correspond to the definition of a web page as used in WCAG 2, but are not restricted to content meeting that definition. For example, a view could be considered a “screen” in a mobile app or a layer of web content – such as a modal. </p>

<p><dfn data-lt="user process" title="Series of user actions required to complete an activity">User processes</dfn> are a series of user actions, and the distinct interactive <a>views</a> and <a>items</a> that support the actions, where each action is required to complete an activity. A user process may include a subset of items in a view or a group of views.</p>
<p>Examples of a process include:</p>
Expand Down Expand Up @@ -505,8 +505,8 @@ <h3>Issue severity</h3>
<li>If included, how will situations where severity depends on context be handled?</li>
<li>Can the matrix inform designation of functional categories? For example, the <a href="https://www.w3.org/WAI/GL/WCAG3/2021/outcomes/text-alternative-available">Text Alternative Available outcome</a>.</li>
<li>How will issue severity fit into levels? For example:<ul>
<li>"Bronze" could be an absence of any critical or high issues;</li>
<li>"Silver" could be an absence of any critical, high, or medium issues.</li>
<li>“Bronze” could be an absence of any critical or high issues;</li>
<li>“Silver” could be an absence of any critical, high, or medium issues.</li>
</ul>
</li>
<li>How to account for cumulative issues becoming critical?</li>
Expand Down Expand Up @@ -568,7 +568,7 @@ <h3>Defining conformance scope</h3>
<li>Large amounts of content are impractical to evaluate comprehensively using anything beyond <a>automated evaluation</a> of items;</li>
<li>In many cases, content changes frequently, causing evaluation to be accurate only for a specific moment in time;</li>
<li>Some content is more important to the majority of users than other content; and</li>
<li>Content that mostly meets the requirements but has problems can interfere with the user's ability to complete a process.</li>
<li>Content that mostly meets the requirements but has problems can interfere with the user’s ability to complete a process.</li>
</ul>
<p>WCAG 3 therefore defines two ways to scope content: <a>views</a> and <a>processes</a>. Evaluation is done on one or more complete views or processes, and conformance is determined on the basis of one or more complete views or processes. </p>

Expand Down Expand Up @@ -623,10 +623,10 @@ <h3>User generated content</h3>
</details>
<div class="ednote">
<p>It remains to be determined how to address User Generated Content that has accessibility issues; and to define what minimum thresholds might be acceptable. We expect WCAG 3 to provide this guidance within individual guidelines and outcomes and to support testing for conformance. The working group is looking at alternative requirements to apply to User Generated Content guideline by guideline, and is seeking feedback on what would serve as reasonable requirements on how to best support accessibility in User Generated Content with known (or anticipated) accessibility issues. </p>
<p>One example would be 'alternative text'. The Authoring Tool Accessibility Guidelines (ATAG) has specific guidance for providing a mechanism for alternative text. The <a href="https://www.w3.org/TR/ATAG20/#gl_b23">ATAG 2.0 Guideline B.2.3</a> - "Assist authors with managing alternative content for non-text content" could be adapted to provide specific, guideline-related guidance for user generated alternative text. </p>
<p>One example would be “alternative text”. The Authoring Tool Accessibility Guidelines (ATAG) has specific guidance for providing a mechanism for alternative text. The <a href="https://www.w3.org/TR/ATAG20/#gl_b23">ATAG 2.0 Guideline B.2.3</a> - “Assist authors with managing alternative content for non-text content” could be adapted to provide specific, guideline-related guidance for user generated alternative text. </p>
<p>The working group intends to more thoroughly address the contents and the location of an accessibility statement in a future draft.</p>
</div>
<p>Web content publishers may include content provided by the users of their digital products. We refer to such content as "<a href="#user-generated-content">User Generated Content</a>".</p>
<p>Web content publishers may include content provided by the users of their digital products. We refer to such content as “<a href="#user-generated-content">User Generated Content</a>”.</p>
<p>Examples of User Generated Content include:</p>
<ul>
<li>social media postings and comments,</li>
Expand All @@ -642,7 +642,7 @@ <h3>User generated content</h3>
<h4>Steps to conform</h4>
<p>If accessibility issues are identified, or if the web site author wants to proactively address potential accessibility issues that might arise from User Generated Content, then all of the following must be indicated alongside the User Generated Content or in an Accessibility Statement published on the web site or product that is linked from the view or page in a consistent location:</p>
<ol>
<li>Clearly identify where User Generated Content can be found on the publisher's digital product (perhaps by id href);</li>
<li>Clearly identify where User Generated Content can be found on the publisher’s digital product (perhaps by id href);</li>
<li>Clearly identify the steps taken to encourage accessibility in User Generated Content such as prompting the user for ALT text for their uploaded images before they are accepted and prohibiting text attributes except as they are part of semantic markup such as strong, headings, etc., as enumerated in Guideline Outcomes;</li>
</ol>
</section>
Expand Down

0 comments on commit 55c8020

Please sign in to comment.