Edit comment LC-2569 for Accessibility Guidelines Working Group

Next: LC-2511

Comment LC-2569: Comment Shortname:; Commenter: Makoto Ueki <makoto.ueki@gmail.com>; 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:
The note reads "Even though this is currently invalid, it is provided as a transitional technique to make this function work."
Was this technique used before? This example looks very strange because none of WAIC working group members have used this technique before. We would simply use <a> element for this. This example is not useful.

Proposed Change:
Could you tell us the reason why this example is needed?
In our opinion, this example should be deleted.; Related issues: (space separated ids); WG Notes: Using and manipulating non-semantic elements does happen increasingly in self-styled widgets, mostly because designers don't want the default look of semantic elements (think of checkboxes) and sometimes because they want extended functionality (for example, to express 'partly checked' above a group of checkboxes). While I agree that example 2 is odd and should be replaced, there is a trade-off regarding such examples: they may encourage bad practice, but on the other hand, to the extent that self-styled widgets are becoming more common anyway, examples should show responsible use. So maybe one could identify another example for device independent event handlers where the use of images to implement a custom look and behaviour seems better motivated. A note should refer to the need to use WAI-ARIA appropriately to announce role and states so such elements become semantic for screen reader users (and point out still partial support by oder UA and AT). Adam: I checked this example in ie9 firefox and chrome and I couldn't click it with the return key - unless someone can prove that I didn't test it right, this example is not just invalid but is also not relevant to the technique which is about keyboard handlers http://websiteaccessibility.donaldevans.com/2011/06/30/when-does-onclick-work-with-the-keyboard-enter-key/ I know that it was popular to use img with click but right now it is completely unsupported and should be dropped Response from 9/29/11: Thank you for your comment. We have concluded that the example in question does not work correctly in modern browsers. The image is not clickable with a keyboard key. We will delete this example. We are also considering replacing it with a different example. @@Proposed resolution: delete example 2. Add similar example with input of type image instead of img element. Action: James to contact Adam to find out why there is a disconnect, since these examples work for him.; Resolution: [DONE] Change first sentence of example to "This example shows a custom image control for which both the mouse and the keyboard can be used to activate the function." [DONE] Add to end of note: "Custom controls like this should also use WAI-ARIA to expose the role and state of the control." Proposed response: Using and manipulating non-semantic elements does happen increasingly in self-styled widgets, mostly because designers don't want the default appearance of semantic elements (think of checkboxes) and sometimes because they want extended functionality (for example, to express 'partly checked' above a group of checkboxes). To the extent that self-styled widgets have become more popular, we provide this example to demonstrate how to add keyboard access. As we add WAI-ARIA techniques, we hope to provide better examples of custom controls.; (Please make sure the resolution is adapted for public consumption)