Kacie Fijalkovich

It sounds like we could fix this on specific components by setting an `accessibilityLabel` in JS on the outermost View/Touchable/thing that Android deems focusable (like you mentioned with Button). I...

> @kacieb equivalent functionality in terms of web aria api https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-errormessage This is awesome @fabriziobertoglio1987! Would it be possible to follow the aria names and pattern for the JavaScript API?...

> something to note is that the value of aria-errormessage is meant to be the id of an element that contains the error message. Good note. I think this is...

This looks good to me on the JS side! I'll work with blavalla to make sure we can land safely. cc @lunaleaps for awareness.

> I think there may be room for a new accessibility property that contains these traits and possibly others There's previously been some conversation about adding new accessibility properties in...

Hey @blavalla! Thanks for reporting this. I think several of the issues you noticed are actually from the Views being completely removed because they have no "height" property. This is...

Just wanted to check - it sounds like "title" is different from "accessibilityLabel" (or contentDescription on Android)? It seems reasonable to me to add a new prop to Modal to...

Potentially a prop like this could be exposed as a native prop on ScrollView.js. Maybe an automatic count could be accomplished in the native Android React Native ScrollView component. What...

This is an issue I think would be great to see a proposal for before anyone begins working on it, since there are likely multiple ways to solve this.

> Count should be the number of child elements That's great, I think that means this can be done automatically in the native ScrollView (I have to double check, but...