Last updated April 17, 2019 (originally created late 2017 or early 2018?): There was some recent confusion about AOM events recently explained in a support document from Apple. Please read that first. Also read the Events section of the AOM explainer for use cases.
To enable the experimental feature, use one of these methods.
--enable-blink-features=AccessibilityObjectModelFocus the form field, select some text and "cut" it. It should trigger two alerts.
Note: This is just a baseline test for input events. Not a part of AOM.
Interact with the slider and perform increment/decrement actions on it. It should trigger alerts for each type. Depending on how the standard develops, it may triggered by Arrow key presses when using a keyboard.
Note: This is not a fully functional slider example. It's just an event test case.
Navigate inside the dialog, then perform a "scrub" gesture in VoiceOver on iOS, or trigger with Switch Control. This should not trigger "back" behavior on either the button or the heading. The input event will also likely be triggered by Escape key presses when using a keyboard.
Note: This is not a fully functional dialog example. It's just an event test case.
Deprecation note: These are kept around for legacy test purposes until the increment/decrement/dismiss functionality is either unshipped in its current form, or updated to the new proposal, probably in the form of input events.
Interact with the slider and perform increment/decrement actions on it. It should trigger alerts for each type. The updated replacement input event for this will also likely be triggered by Arrow key presses when using a keyboard.
Note: This is not a fully functional slider example. It's just an event test case.
Interact with the slider and perform increment/decrement actions on it. It should trigger alerts for each type. The updated replacement input event for this will also likely be triggered by Arrow key presses when using a keyboard.
Note: This is not a fully functional slider example. It's just an event test case.
Navigate inside the dialog, then perform a "scrub" gesture in VoiceOver on iOS, or trigger with Switch Control. This should not trigger "back" behavior on either the button or the heading. The updated replacement input event for this will also likely be triggered by Escape key presses when using a keyboard.
Note: This is not a fully functional dialog example. It's just an event test case.
Content past the examples.