w3c/wbs-design
or
by mail to sysreq
.
The results of this questionnaire are available to anybody.
This questionnaire was open from 2021-08-05 to 2021-08-10.
7 answers have been received.
Jump to results for question:
Link to new User Generated Outcome
This is an example of a way that an outcome can be used for additional requirements for User Generated Content. Since the Outcome template is being revised, the organization of the outcome will change as we update the template for Outcomes. This example is taken from Authoring Tool Accessibility Guidelines (ATAG) 2.0. The Text Alternatives subgroup continues to develop outcomes, methods and how-to material for Text Alternatives.
Can we move the example of a text alternative outcome for user generated content to CFC for addition to the next update of WCAG 3?
Choice | All responders |
---|---|
Results | |
Agree | 2 |
Agree with the following changes | 1 |
Disagree for the following reason | 3 |
(1 response didn't contain an answer to this question)
Responder | New example of an outcome: Text alternative for user generated content | Comments |
---|---|---|
Oliver Keim | Agree with the following changes | The unordered list items may be named in a manner its easier to understand. * for non-text content a text can be added, maintained or removed. * the editing process is supported by validation checks (list samples, liek "image", filename, etc) * Authoring tools allow identifying and correcting texts that do not validate. |
Gundula Niemann | Disagree for the following reason | Third bullet: The outcome now requests a flagging functionality instead of an automatic repair. Fifth bullet: The sentence is still clumsy (I don't understand it). I fee the outcome should be closer to the ATAG. Like . If the authoring tool provides functionality for adding non-text content, then authors are able to edit text alternatives for their non-text content. - The authoring tool repairs text alternatives for non-text content by refusing generic and irrelevant strings as text alternative. - In the case when the same image is re-used, offers the user the previously provided text alternative for that image. |
Rain Breaw Michaels | Agree | |
Sarah Horton | Disagree for the following reason | It’s unclear how this content fits into the WCAG 3 structure. Is it an outcome for the Text Alternatives guideline? Or a method for the Text Alternative Available outcome? The only method on the “Supports the addition of text alternatives for user-generated content” page that seems to relate to this as its own outcome is Author control of text alternatives (ATAG) (https://www.w3.org/WAI/GL/WCAG3/2020/methods/text-alternative-editable/). Is that content part of this survey? If the structure can be clarified and makes sense I would change my response to agree with the following changes: On the outcome page, remove mention of scoring: “The scoring system is being revised, but we envision that the conformance score for the publisher of the user generated content will recognize the publishing doing increasing amounts of the previous list.” The previous sentence better explains the status, which is that specifics such as scoring and conformance need further discussion: “How the specific details of this outcome will be managed and what is required vs what is recommended still needs discussion.” Clarify what is meant by the last bullet, “Provides the functionality for adding non-text content, when users enter programmatically associated text alternatives for non-text content AND the author has the option to edit or delete the saved text alternatives.” Add something to the Author control of text alternatives (ATAG) method to make clear that the content is from ATAG and is out of date, but is provided for the purpose of illustrating what it might look like if ATAG were included in WCAG 3. |
Jeanne F Spellman | Agree | |
Laura Carlson | Disagree for the following reason | Agree with Sarah Horton. |
Michael Gower | Still digesting. I think the test makes sense, and I'm struggling to think why we wouldn't include Authoring tool requirements like this as part of 3. |
Link to new User Generated Content section in Conformance
Can we move the User Generated Content section to CFC for addition to the next update of WCAG 3?
Choice | All responders |
---|---|
Results | |
Agree | 2 |
Agree with the following changes | 3 |
Disagree for the following reason |
(2 responses didn't contain an answer to this question)
Responder | User Generated Content (a new subsection of conformance) | Comments |
---|---|---|
Oliver Keim | Agree with the following changes | duplicate string: "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." |
Gundula Niemann | Agree with the following changes | The last paragraph is duplicated. It should appear only once. |
Rain Breaw Michaels | Agree | |
Sarah Horton | ||
Jeanne F Spellman | Agree | |
Laura Carlson | Agree with the following changes | Agree if, for the text "all of the following should be indicated alongside the User Generated Content or in an Accessibility Statement published on the site or product": The word "should" is changed to "MUST" and text is added o make sure that if it is in an Accessibility Statement that it must be also be linked to alongside the User Generated Content so the user doesn't need to hunt for the an Accessibility Statement hidden somewhere on a website. |
Michael Gower |
Link to the User Generated Content in the Glossary
Can we move the User Generated Content definition in the Glossary to CFC for addition to the next update of WCAG 3?
Choice | All responders |
---|---|
Results | |
Agree | 1 |
Agree with the following changes | 3 |
Disagree for the following reason |
(3 responses didn't contain an answer to this question)
Responder | Glossary Definition of User Generated Content | |
---|---|---|
Oliver Keim | Agree with the following changes | The last sentence is not necessary, if the UI for the members/end users supports accessibility features, why should the authoring UI not support the same? |
Gundula Niemann | Agree with the following changes | Drop the last sentence. Why is the distinction needed? The resulting page with content shall be accessible anyway. |
Rain Breaw Michaels | Agree with the following changes | I can live without this change. Do we feel confident that this definition also excludes website owners who are customers of SAAS (software as a service) platforms such as Wix, Squarespace, etc.? I'm concerned that the way it reads, with the use of the word "customers," could lead some to interpret that site owners using such tools to create their site are "users" and therefore their entire site falls under UGC. An addition might address this, such as "The publisher in this definition is the owner of the website providing content, not the owner of a paid platform used for website creation and hosting." |
Sarah Horton | ||
Jeanne F Spellman | Agree | |
Laura Carlson | I think that the last sentence is needed to clarify that employees are not exempt from following the rules. Example: https://www.youtube.com/user/UMNDuluth These use cases should not be exempt. | |
Michael Gower |
The following persons have not answered the questionnaire:
Send an email to all the non-responders.
Compact view of the results / list of email addresses of the responders
WBS home / Questionnaires / WG questionnaires / Answer this questionnaire
w3c/wbs-design
or
by mail to sysreq
.