Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

React Arborist – A full-featured tree component for React

github.com

Post reply on HN
Print view View original

11–20 of 57 posts

Re: React Arborist – A full-featured tree component for React

#11

Post by citelao »

I should apologize off-the-bat for not digging in too deeply, but how does this handle keyboard and screenreader accessibility?

W3C has some in-depth list of expected keyboard interactions, though I'm not sure how complete they are:

https://w3c.github.io/aria-practices/#TreeView

https://w3c.github.io/aria-practices/examples/treeview/treev...

I ask because I've tried to implement a [TreeGrid](https://w3c.github.io/aria-practices/#treegrid) myself before and... it's a lot of work. I'd love an accessible, keyboard-friendly React tree :).

Re: React Arborist – A full-featured tree component for React

#12

Post by ctoth »

citelao wrote: post #11

I should apologize off-the-bat for not digging in too deeply, but how does this handle keyboard and screenreader accessibility? W3C has some in-depth list of expected keyboard interactions, though I'm not sure how complete they are: https://w3c.github.io/aria-practices/#TreeView https://w3c.github.io/aria-practices/examples/treeview/treev... I ask because I've tried to implement a [TreeGrid]( https://w3c.github.io/ar…

Just tried it with NVDA on Windows and it appears that it does not handle keyboard accessibility at all and does not communicate the relationships between nodes.

Re: React Arborist – A full-featured tree component for React

#13

Post by jameskerr »

citelao wrote: post #11

I should apologize off-the-bat for not digging in too deeply, but how does this handle keyboard and screenreader accessibility? W3C has some in-depth list of expected keyboard interactions, though I'm not sure how complete they are: https://w3c.github.io/aria-practices/#TreeView https://w3c.github.io/aria-practices/examples/treeview/treev... I ask because I've tried to implement a [TreeGrid]( https://w3c.github.io/ar…

Thank you for bringing this up. It's I who apologize for being ignorant of these expected keyboard interactions. I'll make an issue in the repo to address this.

Re: React Arborist – A full-featured tree component for React

#14

Post by jameskerr »

yuchi wrote: post #10

Very sad to discover that this is NOT a ready made component to display actual trees. What a deceitful name! Jokes apart, nice library. Will try it out sooner or later. May I suggest to not use children as the prop to Ps the Node component? Maybe a more explicit NodeComponent prop would have been better imho.

Dang it, I can see how the title was deceptive. This is headless component, leaving the markup and styling completely up to the user. Many of the tree components I looked at before building this didn't let me do exactly what I wanted with the style like this one does. However, I was thinking of shipping a default "" component that comes with some default styling to get people up and running quickly. I've just made an issue for this.

Re: React Arborist – A full-featured tree component for React

#16

Post by eurasiantiger »

jameskerr wrote: post #13
citelao wrote: post #11

I should apologize off-the-bat for not digging in too deeply, but how does this handle keyboard and screenreader accessibility? W3C has some in-depth list of expected keyboard interactions, though I'm not sure how complete they are: https://w3c.github.io/aria-practices/#TreeView https://w3c.github.io/aria-practices/examples/treeview/treev... I ask because I've tried to implement a [TreeGrid]( https://w3c.github.io/ar…

Thank you for bringing this up. It's I who apologize for being ignorant of these expected keyboard interactions. I'll make an issue in the repo to address this.

Thank you! Don’t sweat not knowing, but without 100% accessibility coverage, the component might as well not exist — it could not be used in any publicly funded project in EU/USA or any commercial project in the EU, because it would be against the law to do so.

Re: React Arborist – A full-featured tree component for React

#18

Post by lelandfe »

eurasiantiger wrote: post #16
jameskerr wrote: post #13

Earlier quoted context omitted.

Thank you for bringing this up. It's I who apologize for being ignorant of these expected keyboard interactions. I'll make an issue in the repo to address this.

Thank you! Don’t sweat not knowing, but without 100% accessibility coverage, the component might as well not exist — it could not be used in any publicly funded project in EU/USA or any commercial project in the EU, because it would be against the law to do so.

> without 100% accessibility coverage

If that's the standard for open-source projects, it's a wonder any FE components get used

Re: React Arborist – A full-featured tree component for React

#19

Post by fleddr »

eurasiantiger wrote: post #16
jameskerr wrote: post #13

Earlier quoted context omitted.

Thank you for bringing this up. It's I who apologize for being ignorant of these expected keyboard interactions. I'll make an issue in the repo to address this.

Thank you! Don’t sweat not knowing, but without 100% accessibility coverage, the component might as well not exist — it could not be used in any publicly funded project in EU/USA or any commercial project in the EU, because it would be against the law to do so.

Nonsense. A deep study about web accessibility some 2 years ago revealed that 98.8% of web pages have accessibility issues. So saying "might as well not exist" is a dramatization of reality.
Post reply on HN