Focusable and accessible native states can get out of sync

[rozele]

Problem Description

If only focusable or accessible props change in a particular batch of updates to a View, we will not apply the mitigation here to ensure focusable and accessible states are kept in sync.

Steps To Reproduce

1. Open the view.tsx example
2. Update the example with the code in this gist.
3. Play around with setting pressable, focusable, and accessible in various combinations.

Setting pressable to false, and then setting either focusable or accessible to false but not both puts the app in a bad state where narrator can get out of sync with keyboard focus.

See following bugs below:

1. IsTabStop not disabled after setting accessible to false
2. Is accessible not disabled after setting focusable to false

Expected Results

Based on #9840 and #10569, we should have the behavior described by the following pseudo-code:

if view is pressable:
  if view is not both focusable or accessible:
    view is not focusable and not accessible
  else:
    view is focusable and accessible
else:
  if view is focusable or accessible:
    view is focusable and accessible
  else:
    view is not focusable and not accessible

CLI version

npx react-native --version

Environment

npx react-native info

Target Platform Version

No response

Target Device(s)

No response

Visual Studio Version

No response

Build Configuration

No response

Snack, code example, screenshot, or link to a repository

React.Native.Playground.Win32.2022-10-06.12-52-32.mp4

[jonthysell]

@chiaramooney can take a look at this?