blavalla

While I like the general idea of having a more unified API between native and web, there are some pretty big differences that would need to be taken into account...

While this is a good idea, there are some caveats as to how it could be implemented on iOS and Android. I think it would be useful to know if...

@kacieb, @lunaleaps, @nadiia, this mostly impacts in that it has a required "title" prop that does this automatically, but it could also impact the various components as well, if you...

@kacieb Having the contentDescription override the text isn't really a bug, as that is the expected behavior of that property on Android, and accessibilityLabel on iOS works the same way....

Links should now be working in the new Fabric renderer. ``` {'This is a test of '} { alert('clicked')}}>inline links {' in Fabric. Here is '} { alert('clicked')}}>another link {'.'}...

@akkadaya, this should be fixed in 0.69 via this commit (https://github.com/facebook/react-native/commit/7b5b114d578142d18bf4a7a5279b179a9ac8d958)

@kacieb , @nadiia , @lunaleaps , what are your thoughts on the missing iOS traits here? All iOS traits that are "element types" and fit into the model of "accessibilityRole"...

> Just wanted to confirm that `accessibilityRole='text'` is not being read in TalkBack. Currently using react-native 0.63.4 Talkback doesn't have an equivalent of iOS's "StaticText" trait, which is what this...

> > > Just wanted to confirm that `accessibilityRole='text'` is not being read in TalkBack. Currently using react-native 0.63.4 > > > > > > Talkback doesn't have an equivalent...

This one likely needs investigation from the React Native team, as the "collapsible" prop has some complex behavior trying to automatically reduce the view hierarchy, which can cause accessibility problems...