Perspective: Open Source WebAssembly-Powered BI (opens in new tab)

Yep. I actually guessed it was Business Intelligence before I posted but I play dumb on things like this as a matter of principle.

We shouldn't have to guess.

What does that mean or imply?

I don't see why rendering this in Electron (which is essentially just a bundled Chromium browser) would perform differently than in a standalone browser. Neither do I see how projects like Tauri or WebView2 which just embed the system webview would give better rendering performance. Microsofts webview is even using the same rendering engine as Electron - Blink. What you'd get is significantly smaller binary size but most people don't care much about that.

I'm building something similar to this and going down the Tauri route

I had no performance problems, but right on the first demo each scrollbar is broken in it's own unique way.

The main area with the sparkgrid has good horizontal and vertical scrollbars, but they are nearly invisible, being dark grey on slightly lighter dark grey, and only visible if you hover in the area they scroll. Also the vertical scroll bar doesn't take you to the very bottom.

Then there's the top right area, which has a normal looking scrollbar (good), but once you scroll it changes the size of the entire right panel (weird), and if you drag it past the point where it has reached the bottom (really easy to do accidentally) it starts spasming uncontrollably. If you instead use the scroll wheel, you can scroll to the bottom, but if you scroll a bit further you are back on the top? None of the other scrollbars has either of those issues.

Then there's the bottom right, where the scrollbar is visible, takes you all the way to the bottom, and neither spasms nor resets, but just to be special in its own way it starts out as a big bar as if there was little content below the fold, but the further you scroll the smaller the bar gets. As you scroll up, it grows again. It's also stuttering a bit while making these size changes.

Another example besides scroll bars is the lack of tool tips on the UI (they do exist on data though!), which makes for a weird toolbar that moves its content all over the place on hover. And I guess you're supposed to guess that check boxes are delete buttons.

This doesn't take away from the app, it's still cool and useful, but little annoyances like that add up to make it feel weird and un-native (I guess foreign is the word).

If we are going to go this way: You previously commented that something doesn't work on Firefox, do all your project superior browser support? That doesn't make sense does it? What does my website which I updated 6 years ago (and created more than a decade ago) have anything to do with the validity of my comment? It just has a contrast issue (let me fix that BTW [edit: done]), a criteria that was set way later than I built that site. Also this is a component library aimed at businesses, not a personal website that I'm commenting about. Please stop trying to poison the well (going as far as hunting a11y issues on my personal site) and argue on merits.

I do it from a position of support, which I had the chance of developing by observing the users of the apps I created, and I made a giant software suit (more than 1000 views) pass an accessibility audit in my current company.

This is not just a charting library, see the examples down the page. Also, see: https://www.highcharts.com/blog/tutorials/best-chart-accessi...

auctioneer voice plugin

What are your eyes going to do with such a table? People pause right? So it would be nice to have some help to navigate. aria-sort in that example would help a lot, also some menus usable with a keyboard, and not disabling outlines.

I was looking at the datagrid. I can't use the menus with the keyboard. I can't select columns. I can't see the currently focused element. My screen reader does not inform me of the menus, nor can I interact with them. Inputs have outline: none. Labels are not connected to the inputs.

In this example: https://perspective.finos.org/block/?example=superstore

I can't use the tree with the keyboard. From the patterns page I linked, you can see an implementation example for an accessible tree element.

I mean, I can continue. I'm not saying this to devalue your work, and I wish I had the time to go in depth and analyze all the components and give you more feedback, but I don't. So I humbly suggest you do a bit research about the topic and improve the product some.

Perhaps my original comment sounded too dismissive and therefore got many negative feedback, but I'm sincerely concerned. I wanted to hint at this as this is a tool that may be used by businesses and some people cannot do their job because of inaccessible tooling.

I do like what you are doing and the components do look cool - nothing to take away from that. Please take my comment as constructive as you can take it to be because I was trying to go for that, and perhaps my frustration in the last few years with this topic made me also whine a little bit :)

I just commented about something I found lacking, it's not a hostile comment, and suggested improvements to the authors who seem to be hanging out here. I think if they have interest, they can add these as an issue, or choose not to.

To the downvoters: Do you really think I should open issues for every critic I place to open source projects here and otherwise not mention anything? I also love and contribute to open-source but this feels like too demanding.