Skip to content
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

Refactor automated a11y scans #17

Open
pboeder opened this issue Aug 23, 2023 · 1 comment
Open

Refactor automated a11y scans #17

pboeder opened this issue Aug 23, 2023 · 1 comment

Comments

@pboeder
Copy link
Member

pboeder commented Aug 23, 2023

✨ Refactor: A11y scans

The A11y scan runs automatically after each push or manually.
That should be changed, because we need to await the deployment process, before running the a11y tests.
Additionally the paths that shall be tested need to be listed in tests/a11y.spec.ts. With the new blog feature, that should be automated, to include the latest blog posts as well.

Acceptance criteria

  • A11y scans should include all deployed paths automatically
  • The A11y scans should be run after each successful deployment
@itrich
Copy link
Member

itrich commented Nov 6, 2023

As for now, I have disabled the A11y tests for svg elements since https://github.com/Niels-IO/next-image-export-optimizer is not creating a unique id for every blur filter. This needs to be addressed upstream.

See 9a124e4#diff-f5fca1f01ef788e9a4af430797533798b8352aef23031a49446e0beae8361112R17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants