Should accessible be supported in React Strict DOM?

[christianbach]

Describe the feature request

React Native uses the accessible prop to group child elements into a single selectable component (docs). Since React Strict DOM is meant to work across React and React Native, should this prop be supported?

I looked through the source code and saw that accessible is defined in renderer.native.js , but it’s never actually set. Was this an intentional omission, or something that could be added?

Curious to hear your thoughts.

[nmn]

React Strict DOM has the explicit goal of matching the web/DOM APIs where possible and bringing those to React Native. This is also the direction that React Native itself is taking in the long run.

So, accessible is not an API that should be exposed through React Strict DOM because it's a React Native only API that doesn't exist on the web.

Instead, it should be an implementation detail. The web way to do something similar is to use the aria-label attribute. Setting this attribute makes a screenreader announce the entire element and its children as a single label for screen readers. Using aria-label in RSD should automatically be using accessible behind the scenes.

The question here is to understand when else it should be applied. What other aria- attributes or other HTML props and attrs should result in accessible as an implementation detail?

Some things that come to mind:

• inert
• aria-hidden

[hentry-paul]

@nmn Is there a way to assign a hint via RSD? afaik, there is no specific property in aria-* to assign hint.