🦾 Accessibilty & UX

[BOHEUS]

When browsing the source code of pages in Twenty, one can notice that most of elements are divs even though they shouldn't be like buttons or tables. If Twenty wants to be accessible according to WCAG, a11y, i18n/i10n and other accessibility guidelines, necessary changes must be made in codebase.

### Tasks
- [ ] https://github.com/twentyhq/twenty/issues/7281
- [ ] twentyhq/twenty#7289
- [ ] https://github.com/twentyhq/twenty/issues/7356
- [ ] https://github.com/twentyhq/twenty/issues/7575
- [ ] https://github.com/twentyhq/twenty/issues/7577
- [ ] https://github.com/twentyhq/private-issues/issues/103
- [ ] https://github.com/twentyhq/twenty/issues/7817
- [ ] https://github.com/twentyhq/twenty/issues/7854
- [ ] https://github.com/twentyhq/twenty/issues/7855
- [ ] https://github.com/twentyhq/twenty/issues/8435

[Bonapara]

Thanks for gathering these issues @BOHEUS

[lucasbordeau]

What about relying on something like https://www.npmjs.com/package/react-aria for this ? @charlesBochet @Devessier

[SNIDGHA]

/assign

[oss-gg[bot]]

This issue is not part of oss.gg hackathon. Please pick a different one or start with a side quest