Edit comment LC-2546 for Accessibility Guidelines Working Group

Previous: LC-2545 Next: LC-2552

Comment LC-2546: Comment Shortname:; Commenter: Makoto Ueki <makoto.ueki@gmail.com> on behalf of JIS; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Flash animation is embedded in a HTML web page. The animation has five screens. It starts automatically, lasts more than five seconds, and is presented in parallel with other content. It also has five buttons to stop the animation. When each button receive focus, the movement of the animation will be paused.

Is this considered to be "a mechanism for the user to pause" the animation?

The point is that it might not be obvious for users to understand that the buttons are the mechanism.

Example:
http://www.fujitsu.com/us/

Proposed Change:
Need an answer from WCAG WG to harmonize JIS with WCAG 2.0.; Related issues: (space separated ids); WG Notes: Michael to draft additional info for Intro to Understanding. Action 147. Response: WCAG just says that a mechanism needs to be provided. Whether something is obvious is not testable - although good practice would be to do this of course. In this case you can point to any of the 5 buttons OR point to the image itself to pause it. For the animated text bar, there is actually a pause button shown. @@add a new section in the techniques intro after the "testing techniques" section, with title "Application of techniques", and content as follows. Techniques in this suite often contain code samples to show the technique in practice. These samples exemplify the technique but do not necessarily exemplify all aspects of good code practice or features needed to conform to other success criteria. This is to keep the examples brief and facilitate understanding of the central point of the sample. Accordingly, authors should not copy these examples in production code unless they provide the missing functionality. In addition to inline code samples, many techniques provide "working examples" that are more complete. Such samples are more appropriate as a starting point for production code, although even these may have minimal content. Many techniques describe how to provide alternate mechanisms to access content. It is important to remember that such alternate functionality must itself conform to WCAG 2.0. A given technique may focus on the basic way to provide the alternate mechanism, but authors need to follow additional relevant techniques to ensure the alternate mechanism meets requirements. Some techniques use the word "must". Because this is not a normative document, this word is not used in the sense of RFC 2119, as it is in WCAG 2.0. The colloquial use of the word "must" describes proper application of the specific technique under consideration. It does not imply requirements beyond the scope of the technique. This means it does not impose requirements on interpretation of the Success Criterion to which the technique relates. Reply from commenter: Thank you very much for the response.I appreciate your help. Can I ask you an additional question? When the Flash buttons receive focus, the Flash animation would be paused. However, if the user move the focus to the HTML links and/or controls on the same page, the Flash animation would be restarted. Even if so, does it mean that the Flash animation passed SC 2.2.2?; Resolution: If you cannot move the focus away from the buttons without the animation restarting, then the animation cannot be paused in a manner that allows use of the page -- so it would not be considered a pause in the way it is meant in the SC. We have clarified this in the Understanding Document by adding the following. [DONE] For a mechanism to be considered "a mechanism for the user to pause," it must provide the user with a means to pause that does not tie up the user or the focus so that the page cannot be used. The word "pause" here is meant in the sense of a "pause button" although other mechanisms than a button can be used. Having an animation stop only so long as a user has focus on it (where it restarts as soon as the user moves the focus away) would not be considered a "mechanism for the user to pause" because it makes the page unusable in the process and would not meet this SC. ================================================================== [DONE] add a new section in the techniques intro after the "testing techniques" section, with title "Application of techniques", and content as follows. Techniques in this suite often contain code samples to show the technique in practice. These samples exemplify the technique but do not necessarily exemplify all aspects of good code practice or features needed to conform to other success criteria. This is to keep the examples brief and facilitate understanding of the central point of the sample. Accordingly, authors should not copy these examples in production code unless they provide the missing functionality. In addition to inline code samples, many techniques provide "working examples" that are more complete. Such samples are more appropriate as a starting point for production code, although even these may have minimal content. Many techniques describe how to provide alternate mechanisms to access content. It is important to remember that such alternate functionality must itself conform to WCAG 2.0. A given technique may focus on the basic way to provide the alternate mechanism, but authors need to follow additional relevant techniques to ensure the alternate mechanism meets requirements. Some techniques use the word "must". Because this is not a normative document, this word is not used in the sense of RFC 2119, as it is in WCAG 2.0. The colloquial use of the word "must" describes proper application of the specific technique under consideration. It does not imply requirements beyond the scope of the technique. This means it does not impose requirements on interpretation of the Success Criterion to which the technique relates.; (Please make sure the resolution is adapted for public consumption)