Best Practices – Digital Asset Guidelines – Rev 4 www.autocare.org | www.autocarevip.com | technology@autocare.org 46 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. Steps to Conform If accessibility issues are identified or if the website 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 site or product that is linked from the view or page in a consistent location: 1. Clearly identify where User Generated Content can be found on the publisher's digital product (perhaps by id href) 2. 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 the disallowance of text attributes except as they are part of semantic markup such as strong, headings, etc., as enumerated in Guideline Outcomes Defining conformance scope When evaluating the accessibility of content, WCAG 3.0 requires the outcomes apply to a specific scope. While the scope can be an all content within a digital product, it is usually one or more sub-sets of the whole. Reasons for this include: • Large amounts of content are impractical to evaluate comprehensively using anything beyond automated evaluation of atomic tests • In many cases, content changes frequently, causing evaluation to be accurate only for a specific moment in time • Some content is more important to the majority of users than other content and • Content that mostly meets the requirements but has problems can interfere with the user's ability to complete a process begun elsewhere. WCAG 3.0 therefore defines two inter-related ways to scope content: views and processes. 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.