BlockNote can be setup to use different UI libraries. We have setup initially with [Mantine](https://www.blocknotejs.org/docs/getting-started/mantine), but we have the option of using [Ariakit](https://www.blocknotejs.org/docs/getting-started/ariakit).

The reason to do so, is that Ariakit is focused on Accessibility. But we have to take into account that the editor and it's blocks might look different than the current implementation.

Research on the topic needs to be done. Do we get any real benefit of such change? Begin of the insertion

<br>

### Question asked to BlockNote

####

#### Question

We are doing an effort in OpenProject towards accessibility and I am wondering if it is worth using Ariakit instead of Mantine.

So the questions would be:

* how interchangeable are the frontend toolkits? After we pick up one are we forever locked in? 😅

* and how much does this choice affect building custom blocks?


<br>

#### Answer

I think the answer more depends on your design than your accessibility requirements. The UI library you use should not have too much of an effect on this as we use the libraries pretty much only for the menus and chrome around the editor. The editor content itself does not make use of these libraries.

So if you build a custom block, it shouldn’t be tied to any library. They are easily swappable if you use our defaults but if you go and change out components (sort of “ejecting” as you will) then that’s when you’ll be locked in.

Mantine is our flagship integration and as far as I know, the La Suite Docs guys have put in a good bit of effort around accessibility in their implementation which also uses Mantine. But yousefed can correct me here if I’m wrong

<br>

### Result

We&#39;ll continue with Mantine for now.End of the insertion