Even though this is not an accessibility-specific feature, filing under the Accessibility component for now b/c there isn't a better place to implement end-to-end. The "dismiss" request proof-of-concept example will fire a single event for any of the following physical events: - mouse click (OS X) on the UITrigger "close" <button>. - tap (iOS) on the UITrigger "close" <button>. - spacebar key press (OS X) on the UITrigger "close" <button> (when focused). - escape key press (OS X) anytime focus is in the view. - VoiceOver's two-finger "scrub" gesture when VoiceOver is active on iOS. Test case to be added.
<rdar://problem/20655266>
Related to bug 144066
When you say UITrigger, where is that coming from?
Test case: https://rawgit.com/w3c/indie-ui/master/src/examples/dismissrequest_dialog/dismissrequest_dialog.html
(In reply to comment #3) > When you say UITrigger, where is that coming from? A UITrigger is an element whose default action (click, etc) is to trigger a action on an ancestor element. For example, a "cancel" button might trigger a "dismiss" action on a sheet. A "remove item from cart" button might trigger a "delete" action on an item in a web shopping cart. The association between the trigger and the event receiver is defined through use of the @uiactions attribute on the receiver element, and a corresponding @uitrigger attribute on the descendant trigger element.
*** Bug 144551 has been marked as a duplicate of this bug. ***
The goal of this proof-of-concept is to take work previously specified in IndieUI and demonstrate its value to other WGs, especially the general value that is not related to accessibility. The final API is unlikely to end up using the exact IndieUI API, in part due to baggage related to WAI process. The concepts are just complicated enough that few people understand the problem space. A demo is worth a thousand words.
Obsolete.