fail accessibility tests on any violation

[ScharfViktor]

Now that we fixed all a11y issues (see #889), I switched the test to fail if new a11y issues appear.

[Copilot]

Pull Request Overview

This PR modifies the accessibility testing behavior to fail on any accessibility violation rather than only on critical violations. Previously, the test would only fail for critical accessibility issues, but now it will fail immediately when any violation is detected.

• Removed conditional logic that only failed tests on critical accessibility violations
• Simplified error handling to throw an error for any accessibility violation
• Updated OpenCloud commit ID reference

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
tests/e2e/support/utils/accessibility.ts	Simplified accessibility checking to fail on any violation instead of only critical ones
.woodpecker.env	Updated OpenCloud commit ID reference

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[JammingBen]

Thank you!

[ScharfViktor]

app-provider/secureView.feature does not work because the user cannot open a shared file with the secure view role.
This started happening after updating OpenCloud.

secure view role:

view role:

[JammingBen]

Good catch. It seems to be set to false from the server:

[ScharfViktor]

@micbar suggested to delete FRONTEND_APP_HANDLER_SECURE_VIEW_APP_ADDR env from setup

now locally works fine. waiting CI