tweaks

Author: mdjastrzebski

docs/api/user-event.md

@@ -312,7 +312,7 @@ await user.accessibilityAction(slider, 'increment');
 
 Simulates an assistive technology (e.g. a screen reader) triggering the named accessibility action on a given element, invoking its `onAccessibilityAction` handler.
 
-The `actionName` autocompletes the [standard React Native actions](https://reactnative.dev/docs/accessibility#accessibility-actions) (`activate`, `increment`, `decrement`, `longpress`, `magicTap`, `escape`), but any custom action name is accepted.
+The `actionName` autocompletes the [standard React Native actions](https://reactnative.dev/docs/accessibility#accessibility-actions) (`activate`, `increment`, `decrement`, `longpress`, `magicTap`, `escape`, `expand`, `collapse`), but any custom action name is accepted.
 
 Just like a real assistive technology, the action must be reachable by the user, otherwise an error is thrown:
 

src/user-event/accessibility-action/accessibility-action.ts

@@ -1,7 +1,4 @@
-import type {
-  AccessibilityActionInfo,
-  AccessibilityActionName as ReactNativeAccessibilityActionName,
-} from 'react-native';
+import type { AccessibilityActionInfo } from 'react-native';
 import type { TestInstance } from 'test-renderer';
 
 import { buildAccessibilityActionEvent } from '../../event-builder';
@@ -14,12 +11,22 @@ import { dispatchEvent } from '../utils';
 
 /**
  * Standard accessibility action names recognized by React Native (`activate`,
- * `increment`, `decrement`, `longpress`, `magicTap`, `escape`). Custom action
- * names are supported as well, hence the `string` fallback.
+ * `increment`, `decrement`, `longpress`, `magicTap`, `escape`, `expand`,
+ * `collapse`). Custom action names are supported as well, hence the `string`
+ * fallback.
  *
  * @see https://reactnative.dev/docs/accessibility#accessibility-actions
  */
-export type AccessibilityActionName = StringWithAutocomplete<ReactNativeAccessibilityActionName>;
+export type AccessibilityActionName = StringWithAutocomplete<
+  | 'activate'
+  | 'increment'
+  | 'decrement'
+  | 'longpress'
+  | 'magicTap'
+  | 'escape'
+  | 'expand'
+  | 'collapse'
+>;
 
 /**
  * Simulate an assistive technology (e.g. screen reader) triggering an

website/docs/14.x/docs/api/events/user-event.mdx

@@ -294,3 +294,32 @@ The sequence of events depends on whether the scroll includes an optional moment
 - `momentumScrollBegin`
 - `scroll` (multiple events)
 - `momentumScrollEnd`
+
+## `accessibilityAction()`
+
+```ts
+accessibilityAction(
+  instance: TestInstance,
+  actionName: string,
+): Promise<void>
+```
+
+Example
+
+```ts
+const user = userEvent.setup();
+await user.accessibilityAction(slider, 'increment');
+```
+
+Simulates an assistive technology (e.g. a screen reader) triggering the named accessibility action on a given element, invoking its `onAccessibilityAction` handler.
+
+The `actionName` autocompletes the [standard React Native actions](https://reactnative.dev/docs/accessibility#accessibility-actions) (`activate`, `increment`, `decrement`, `longpress`, `magicTap`, `escape`, `expand`, `collapse`), but any custom action name is accepted.
+
+Just like a real assistive technology, the action must be reachable by the user, otherwise an error is thrown:
+
+- the action must be declared in the element's `accessibilityActions` prop,
+- the element must not be disabled (via `aria-disabled` or `accessibilityState={{ disabled: true }}`).
+
+### Sequence of events
+
+- `accessibilityAction`