Agne Lukoseviciute

@JerryMacedoCastro could you confirm what versions of RNW and react-navigation you are on?

> > @JerryMacedoCastro could you confirm what versions of RNW and react-navigation you are on? > > "react-native-windows": "0.64.14" "@react-navigation/native": "5.9.3" Hmm... 64.14 includes the display:none fix referenced above so...

@laimasingla There are equivalents of focusable for other components (like `disabled` for Pressable, Button, Switch) that you could use with that same hook. For a cleaner approach it might be...

I think this is the same root issue for what we're seeing in gallery - https://github.com/microsoft/react-native-gallery/issues/231. Seems like fixing display:none hasn't fixed this. The [app-side workaround](https://github.com/react-navigation/react-navigation/issues/9109#issuecomment-981829848) should still work, but...

@paperbackdragon if you use a different screen reader like JAWS or NVDA do you get the same issue? That would help narrow down whether this might be a problem with...

@paperbackdragon got it! Yeah definitely seems like it's an issue with XAML islands then, I'm guessing the testing you've done is on a RNW xaml islands app? We'll want to...

related: https://github.com/microsoft/react-native-windows/issues/8875. Next step is to confirm that the root cause is the same for both, in which case this will be a matter of checking the disabled/enabled state when...

update: since we're moving in the direction of using NuGets instead of source, we'll want to create and publish a cpp WinAppSDK nuget -- aka Microsoft.ReactNative build with USE_WINUI3 defined....

Was able to repro on gallery. Works when activating through mouse, but not with keyboard. Looks as though hitting enter/space isn't being registered at all.

Hey @axelfratoniMS, could you try adding accessibilityRole="button" and try again? I'm able to get onPress working that way. For example, this works as expected in scan mode (although onPressIn/onPressOut are...