Skip to content

Decide on the target we want to have for accessibility and lighthouse checks #793

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

Open
choldgraf opened this issue Apr 10, 2025 · 0 comments

Comments

@choldgraf
Copy link
Collaborator

In #792 we lowered the threshold for our lighthouse checks in order to un-break our CI/CD and avoid the "expected failures" anti-pattern. This is a follow-up issue to recognize the fact that we want to set targets for accessibility and jobs like lighthouse that balance realistic and also solve the most important accessibility problems.

The crux of the matter is that we have very limited resources, so we need to choose targets for accessibility that are realistic given these resources. We also need to decide that lighthouse scores are a "good" reflection of our targets (maybe based on best practices for how a11y experts recommend using lighthouse).

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

No branches or pull requests

1 participant