-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[tests-only] accessibility test for basic functionalities of file view #12155
base: master
Are you sure you want to change the base?
Conversation
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. |
…ns for single exclude and 2 exclude
async function (this: World, stepUser: string): Promise<void> { | ||
const { page } = this.actorsEnvironment.getActor({ key: stepUser }) | ||
|
||
const a11yObject = new objects.a11y.Accessibility({ page }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
confused about the name of the pageObject
…e exclude or array with multiple excludes
…onger, remove unused selector
|
@@ -54,6 +55,7 @@ | |||
"@vue/compiler-dom": "3.5.13", | |||
"@vue/compiler-sfc": "3.5.13", | |||
"@vue/test-utils": "2.4.6", | |||
"axe-core": "^4.10.2", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should not be required when using @axe-core/playwright
"axe-core": "^4.10.2", |
Description
setup axe core and implementation of a basic accessibility test for the basic functionalities for file view (personal space, without sidebar) as an example for what aspects of accessibility can be tested in an automatic fashion using the axe-core plugin
Related Issue
Motivation and Context
make sure that oCIS web is compliant with the WCAG accessibility standards in light of European Accessibility Act (EAA) being implemented in June 2025
User Story
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?
Screenshots (if appropriate):
Types of changes
Open tasks / next steps (won't be covered in this PR):
see also #12018 (comment)