react-three-a11y VS three-stdlib

Thanks! Threlte is "just" offering a declarative way to express Three.js. If you know how the `` component and its props and event handlers work, you can use the Three.js documentation for everything else.

Apart from that with Threlte I personally practice documentation-driven-development, so ecosystem packages are exhaustively documented. If you're missing something, let us know via an issue[1] or on Discord[2].

Accessibility is a topic we didn't care enough yet to be perfectly honest. Accessibility doesn't stop at screen readers though, it's about contrast, size, colors, motion, reachability, and so much more that we cannot provide and are a consumer topic. Naturally WebGL apps suffer from being practically invisible to screenreaders. There are workarounds[3] but essentially this has to be solved by consumers of Threlte (devs) and hopefully by browser vendors at some point in the future.

[1] https://github.com/threlte/threlte/issues

[2] http://chat.threlte.xyz

[3] https://github.com/pmndrs/react-three-a11y

There is an accessibility library from drei: https://github.com/pmndrs/react-three-a11y

Caveat: Not the most accessible thing ever. The pmndrs crew made a tool that does this way more accessibly, this would be my production-grade recommendation: https://github.com/pmndrs/react-three-a11y

like /u/thesonglessbird said, it exists: https://github.com/pmndrs/react-three-a11y it covers screen readers, tabbing , focus indication, roles, and so on.

That’s a bit of a cop out - React Three Fiber renders to a canvas too (obviously) and there’s a bunch of accessibility stuff in its semi-official ecosystem https://github.com/pmndrs/react-three-a11y

♿ R3F A11y

To simulate the selected state you can try to use react-three-a11y. By wrapping our model with the component we will have access to hover, focus, and pressed state through useA11y() hook. We can try to display a SelectedMaterial based on the hover state for example.

We have forked parts of the three core stuff to minimise breaks. drei for instance uses https://github.com/pmndrs/three-stdlib not examples/jsm. The threejs version you install can still pull the rug but pmndrs works against that with conditionals, shaders for instance are made to function despite three breaking stuff. You can generally rely on it and Fiber + eco system has semantic versioning.

React Three Fiber has been a fantastic way to quickly prototype 3D apps and games, and even efficient enough to carry them through to production. The problem? It’s can be a lot of setup. Just from that last paragraph, you see the string of dependencies R3F uses, and it gets even more complicated from there when you familiarize yourself with the current ThreeJS ecosystem (see: three-stdlib).

three doesn't play well with node and node based environments. poimandres has been building out three's reach more and more, for instance https://github.com/pmndrs/three-stdlib this will all run under next/nuxt or whatever without workarounds.

three is harder to use in next because it doesn't run under node. with three-fiber we have begun to fork some parts of it: https://github.com/pmndrs/three-stdlib that will make it easier to use it under next, even if you use "vanilla" three, stdlib's GLTFLoader will run fine whereas there/jsm won't (without workarounds). is there any reason why you would not want to use react for three though? you're using it for the dom already, r3f is the exact same thing as react-dom, a renderer, it doesn't wrap three.

Same, the pmndrs folks at least pulled some of the examples stuff into https://github.com/pmndrs/three-stdlib which is ESM

you can use the same tools that react users use because we face the same problems. for instance, next/nuxt are running under node, which doesn't understand what "import" means, so you'll not be able to use anything from three/examples/jsm/ (loaders, controls, etc). but we have made solutions for that. for instance https://github.com/pmndrs/three-stdlib generally there is lots on the poimandres github org that is equally valid for vanilla, react, vue and anything else.

don't mix three and react. take an hour to read through react-three-fiber docs and port it. you will be so much better off, 95% of that code will just vanish. poimandres also takes care of all the other parts, for instance three/examples/jsm/* is not node compatible, you can't easily use it in next. but there exists three-stdlib now and many other things that make your life easier.