- From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
- Date: Thu, 3 May 2018 02:16:22 +0000
- To: Jan Hellbusch <jan@hellbusch.de>, "'w3c-wai-ig'" <w3c-wai-ig@w3.org>
Why would you need a fall back role? As this completely changes the users expectation of the control. If something is a button it is a button. Regards Sean Murphy Accessibility Software ENGINEER seanmmur@cisco.com Tel: +61 2 8446 7751 Cisco Systems, Inc. The Forum 201 Pacific Highway ST LEONARDS 2065 Australia cisco.com http://www.cisco.com/go/accessibility Think before you print. This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html -----Original Message----- From: Jan Hellbusch <jan@hellbusch.de> Sent: Wednesday, 2 May 2018 6:18 PM To: Sean Murphy (seanmmur) <seanmmur@cisco.com>; 'w3c-wai-ig' <w3c-wai-ig@w3.org> Subject: RE: ARIA presentation and role Hi, > Is it valid code to have role=”button presentation” as this doesn’t > look correct to me. The technique is valid to provide a fallback role, but the second role is not a suitable fallback for the first in this example. I don't think that will affect accessibility, though, because buttons are supported everywhere AFAIK. Jan -- Hellbusch Accessibility Consulting Chemnitzer Str. 50, 44139 Dortmund Tel.: +49 (231) 58054815 Mobil: +49 (163) 3369925 -- Accessibility-Consulting seit 15 Jahren Leistungen, Bücher, Artikel: https://www.barrierefreies-webdesign.de Blog: https://www.hellbusch.de
Received on Thursday, 3 May 2018 02:17:03 UTC