General accessibility audit

[bmlancien]

Description of the issue

The platform needs an accessibility audit in order to see how good/bad the platform ranks in that matter, as this is an important topic and there hasn't been a real focus on accessibility until now.

Open questions

• Does the platform need to comply to the European Accessibility Act directives?
  • If yes, it needs to conform to EN 301 549, meaning it should rely on WCAG 2.1 Level AA standards (maybe WCAG 2.2 in the future).
  • It doesn't look like it does, though, but it is still recommended to follow these guidelines
• Do will still develop the platform from a desktop-first perspective? Does mobile view also have to be included in the audit?

Ideas of solution

• [ ] Add accessibility page to documentation (with assessment section). See #1709
• [ ] Conduct general audit on the whole platform
• [ ] Fix quick issues
• [ ] Open issues for more complicated problems

Workflow checklist

• [x] I am aware of the workflow in CONTRIBUTING.md