- From: White, Jason J <jjwhite@ets.org>
- Date: Mon, 15 Dec 2014 19:08:49 +0000
- To: "lwatson@paciellogroup.com" <lwatson@paciellogroup.com>, "WAI Protocols & Formats" <public-pfwg@w3.org>
>-----Original Message----- >When a custom control is created, would it be possible for a browser to >provide the expected keyboard support based on the presence of an explicit >role? For example a custom control with role="button" would automatically >be given the same interaction support as a native <button>. This could be awkward if the author wants to support a different keyboard interface from that of the native control. The user agent would need reliably to detect the presence of keyboard event handlers applicable to the custom control. More broadly, this proposal has been raised previously, and there's an ongoing disagreement as to whether or not the function of ARIA should be confined, as it presently is, strictly to reporting the role, states and properties of each supporting element to assistive technologies such as screen readers that require it. It's possible that we're about to witness another episode in that discussion. ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Monday, 15 December 2014 19:09:17 UTC