Refactor user page to conform 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 -
Use the ADG examples where appropriate, see https://www.accessibility-developer-guide.com/examples/ -
Use the Angular CDK a11y where appropriate, e.g. https://material.angular.io/cdk/a11y/api#LiveAnnouncer