- From: <akirkpat@adobe.com>
- Date: Thu, 16 Jan 2014 20:57:37 +0000
- To: detlev.fischer@testkreis.de
- Cc: public-comments-wcag20@w3.org
Dear detlev.fischer@testkreis.de, The Web Content Accessibility Guidelines Working Group has reviewed the comments you sent [1] on the Last Call Working Draft [2] of the Techniques for WCAG 2.0 published on 5 Sep 2013. Thank you for having taken the time to review the document and to send us comments! The Working Group's response to your comment is included below. Please review it carefully and let us know by email at public-comments-wcag20@w3.org if you agree with it or not before 21 January 2014. In case of disagreement, you are requested to provide a specific solution for or a path to a consensus with the Working Group. If such a consensus cannot be achieved, you will be given the opportunity to raise a formal objection which will then be reviewed by the Director during the transition of this document to the next stage in the W3C Recommendation Track. Thanks, For the Web Content Accessibility Guidelines Working Group, Michael Cooper W3C Staff Contact 1. http://www.w3.org/mid/E1Vjnoq-0005UQ-BF@shauna.w3.org 2. http://www.w3.org/TR/2013/NOTE-WCAG20-TECHS-20130905/ ===== Your comment on F16: Failure of Success Criterion 2.2.2 due to including scrolling content...: > Summary of Issue: Pause/resume controls required also when moving > content initially paused? > Comment (Including rationale for any proposed change): > According to SC 2.2.2 Pause, Stop, Hide, controls or documented means to > stop/pause and resume moving content is required for content that starts > automatically. Does that mean that moving content that is initially > paused but can be activated by the user, there is no requirement to > pause it once it is running? We just have this case in a web site test). Working Group Resolution (LC-2866): Thank you for your question. Your conclusion is on the mark. If content is not moving initially, there's no interference as envisaged by the SC and documented in Understanding WCAG 2.0. If the page does not permit the user to pause the movement after it has been initiated by user-action, it is perhaps a matter that might need to be reviewed from a functionality or usability viewpoint, but it does not fail SC 2.2.2 or conformance requirement #5. ----
Received on Thursday, 16 January 2014 20:57:39 UTC