react-arborist VS aria-practices

Compare react-arborist vs aria-practices and see what are their differences.

react-arborist

The complete tree view component for React (by brimdata)
UI Components Tree arborist React Treeview treeview-component
Source Code
Suggest alternative
Edit details

aria-practices

WAI-ARIA Authoring Practices Guide (APG) (by w3c)
aria CSS HTML
Source Code
w3.org
Suggest alternative
Edit details
SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
surveyjs.io
featured
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
react-arborist aria-practices
13 4
2,772 1,159
2.6% 0.9%
6.7 8.0
14 days ago about 23 hours ago
TypeScript HTML
MIT License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

react-arborist

Posts with mentions or reviews of react-arborist. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-27.

aria-practices

Posts with mentions or reviews of aria-practices. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-13.
  • Here are the 10 projects I am contributing to over the next 6 months. Share yours
    13 projects | dev.to | 13 Apr 2024
    W3C Aria Practices
  • React Arborist – A full-featured tree component for React
    7 projects | news.ycombinator.com | 21 Mar 2022
    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 :).

  • Custom JavaScript controls can't capture the nuance of form fields (2021)
    4 projects | news.ycombinator.com | 24 Feb 2022
    Yep I totally agree with this.

    There are however a bunch of ARIA tags & best practices etc (https://w3c.github.io/aria-practices/) that exist to make popups and dialogs (and other things e.g. tree views or "email-inbox-style" "treegrids" etc) accessible (if implemented correctly).

    I am conflicted about these - it is nice that there are ARIA tags for this, but it would also be nice if browsers "understood" aria tags and added some default behaviors (e.g. keyboard navigation). As it is, ARIA tags are essentially "pointless" to anyone who doesn't use an assistive technology, and so non-assitive-technology users nor developers benefit from using ARIA tags so they are often forgotten. If the browsers saw that there was an A11y-tree that matched a treeview or a treegrid, it would be really really nice if they applied some default common keyboard navigation implementation, rather than do nothing and leave it up to the developer to decide what keys do what on each and every site. .... Or on the other hand, is that too prescriptive and should we give developers and UX designers more leeway to design something better, rather than rely on browser-enforced defaults? I guess we are happy with browser defaults for basic inputs, but would we be for a treegrid?

  • 4 takeaways from axe-con 2021
    2 projects | dev.to | 29 Mar 2021
    The ARIA practices GitHub is a good resource to see where certain patterns fall short.

What are some alternatives?

When comparing react-arborist and aria-practices you can also consider the following projects:

react-treebeard - React Tree View Component. Data-Driven, Fast, Efficient and Customisable.

react-table-library - :bento: React Table Library

monaco-tree - Curiosity hacks with Monaco Editor's tree component

bootstrap-select - :rocket: The jQuery plugin that brings select elements into the 21st century with intuitive multiselection, searching, and much more.

react-complex-tree - Unopinionated Accessible Tree Component with Multi-Select and Drag-And-Drop

standards-support - Contains documentation for Vispero software support of Web standards

react-treeview - Easy, light, flexible tree view made with React.

gecko-dev - Read-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html

aktenkoffer - 💼 Personal document management made easy.

axe-core - Accessibility engine for automated Web UI testing

react-arborist vs react-treebeard aria-practices vs react-table-library react-arborist vs monaco-tree aria-practices vs bootstrap-select react-arborist vs react-complex-tree aria-practices vs standards-support react-arborist vs react-treeview aria-practices vs monaco-tree react-arborist vs gecko-dev aria-practices vs aktenkoffer react-arborist vs react-table-library aria-practices vs axe-core