Refactor creator/room page to comply with a11y requirements
-
Make the page strictly HTML valid - Use aXe Coconut and TotalValidator for a11y checking
-
Revise the page so that only semantic HTML is used -
Make every UI component accessible for Screen Readers - Compare with the recommendations of the Swiss Accessibility Developer Guide (ADG), the documentation of the Angular Material Components (a11y sections), and the WAI-ARIA Authoring Practices 1.1
-
Make the page navigable with the keyboard for screen readers