Skip to content

Commit

Permalink
respell user-generated content
Browse files Browse the repository at this point in the history
  • Loading branch information
Michael Cooper committed Jul 6, 2023
1 parent 9816958 commit 4d81bc9
Showing 1 changed file with 11 additions and 11 deletions.
22 changes: 11 additions & 11 deletions guidelines/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -612,34 +612,34 @@ <h3>Conforming alternative version</h3>
</section>
</section>
<section data-status="exploratory">
<h3>User generated content</h3>
<h3>User-generated content</h3>
<details class="summary">
<summary>Summary</summary>
<p>User generated content is content written by the public and customers. WCAG 3.0 may use different advice or steps for user generated content to improve accessibility than for content created by the publisher. WCAG 3.0 proposes that organizations identify user generated content and identify the steps taken to encourage accessibility. </p>
<p>User-generated content is content written by the public and customers. WCAG 3.0 may use different advice or steps for user-generated content to improve accessibility than for content created by the publisher. WCAG 3.0 proposes that organizations identify user-generated content and identify the steps taken to encourage accessibility. </p>
</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>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>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>Examples of User Generated Content include:</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>
<li>uploaded photographs, or</li>
<li>uploaded videos or other multimedia.</li>
</ul>
<p>User Generated Content is provided for publication by visitors where the content platform specifically welcomes and encourages it. User-generated content is content that is submitted through a user interface designed specifically for members of the public and customers. Use of the same user interface as an authoring tool for publication of content by agents of the publisher (such as employees, contractors, or authorized volunteers) acting on behalf of the publisher does not make that content User Generated Content. The purpose of the User Generated Content Conformance is to allow WCAG 3 outcomes and methods to require additional or different steps to improve the accessibility of User Generated Content.</p>
<p>An important part of WCAG Conformance is the specific guidance that is associated with individual WCAG 3 guidelines and outcomes. Not all WCAG 3 guidelines will have unique outcomes and testing for User Generated Content. Unless User Generated Content requirements are specified in a particular guideline, that guideline applies as written whether or not the content is User Generated. </p>
<p>User-generated content is provided for publication by visitors where the content platform specifically welcomes and encourages it. User-generated content is content that is submitted through a user interface designed specifically for members of the public and customers. Use of the same user interface as an authoring tool for publication of content by agents of the publisher (such as employees, contractors, or authorized volunteers) acting on behalf of the publisher does not make that content user-generated content. The purpose of the user-generated content Conformance is to allow WCAG 3 outcomes and methods to require additional or different steps to improve the accessibility of user-generated content.</p>
<p>An important part of WCAG Conformance is the specific guidance that is associated with individual WCAG 3 guidelines and outcomes. Not all WCAG 3 guidelines will have unique outcomes and testing for user-generated content. Unless user-generated content requirements are specified in a particular guideline, that guideline applies as written whether or not the content is User Generated. </p>


<p>The web content publisher should identify all locations of User Generated Content (such as commentary on hosted content, product descriptions for consumer to consumer for sale listings, and restaurant reviews) and perform standard accessibility evaluation analysis for each. If there are no accessibility issues, the User Generated Content is fully conforming.</p>
<p>The web content publisher should identify all locations of user-generated content (such as commentary on hosted content, product descriptions for consumer to consumer for sale listings, and restaurant reviews) and perform standard accessibility evaluation analysis for each. If there are no accessibility issues, the user-generated content is fully conforming.</p>
<section>
<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>
<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 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>
<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>
</section>
Expand Down

0 comments on commit 4d81bc9

Please sign in to comment.