rci VS zag

I have created a simple segmented input component, using the not so accessible technique of having multiple input components next to each other. I know it's bad, but doing it the rci is more difficult and limiting, but now I want to make it more accessible. My approach is to make a second input element next to it, hide it with css, and make screen readers think it's the actual input field. However, I don't really know how. So, what aria attributes and what not can I give to to trick screen readers into not seeing the div and only the input and is it even doable? Here's is the general DOM structure of my component

Take a look at https://github.com/leonardodino/rci for inspiration.

Zag.js and Ark are headless component libraries created by the teams behind Chakra UI.

ChakraUI: An emphasis on A11y, meaning it is fully compatible with the WAI-ARIA accessibility standard, has won OSS awards, and has a thriving community. As mentioned, it’s one of the better choices out there as it has a great model for building composable UI, built-in hooks, and great dark-mode support. This is the same team behind Zag.js, which handles UI as state machines. Once again, you’d need to learn the API, and swapping might be hard to do.

I agree with what another poster said about Zag (also part of the Chakra project). It seems to me that eventually, with the explosion of number of frameworks, consolidation is going to happen. Segun is influential enough that Zag has a good chance of being what the consolidation ends up centering around.

it's not perfect yet, but I find zagjs promising

Keep an eye on ZAG and ARK from the Chakra UI team, I feel like together with UnoCSS that could get very powerful.

🔗 Head over to https://zagjs.com/ to learn more about Zag.js and get started with building accessible UI components in your web applications!

The Zag.js documentation can be found here: https://zagjs.com/.