a11y e2e tests

[koebel]

Description

setup and implementation of most important accessibility tests using axe-core

• to initial test setup
• create feature with scenarios for login, header, file view, file preview, shares, deleted files
• step implementation
  • login scenario
  • various header features
  • file view scenario
  • file preview (for image files)
  • shares scenario
  • deleted files (trashbin) scenario
• additional page objects?
• axebuilder
• update dependencies
• report accessiblity findings
• change log

Related Issue

• relates to Automated checks for accessibility rules and standards #12018

Motivation and Context

make sure that oCIS web is compliant with the WCAG accessibility standards

As a user with limited accessibility
I want to be able to access all features of oCIS
So that regardless of my abilities and circumstances, I can benefit from oCIS

How Has This Been Tested?

• test cases are passing
• currently some test cases contain excludes for components with know accessibility issues

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests
• Documentation
• Maintenance (e.g. dependency updates or tooling)

Open tasks:

• address the accessibility issues that have been identified by these tests, namely
  • text fields on login page
  • breadcrumbs
  • ...

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.