Skip to content

Lighthouse CI for 508/performance/best practices #561

@krowvin

Description

@krowvin

Is your feature request related to a problem? Please describe.
To help prevent regressions in future updates, ensure OpenDCS web UI is 508/accessible, performant, and following best practices. We would need some way to scan.

Currently if we view the site we find performance issues and/or have trouble viewing certain text if it does not have high enough contrast for example.

Describe the solution you'd like
Suggest we add the Lighthouse CI to the CI/CD pipeline with Github Actions.

Describe alternatives you've considered
We may want to do this until we have some time to really set this up. But manually perform Lighthouse scans in the dev tools. There's a tab in there to do it per page.

Run the site against 3rd party checkers on some schedule.

Additional context

Suggest we go through the getting started for Lighthouse CI. There's some key points about starting slow and not trying to do it all at once due to a steep learning curve:

https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/getting-started.md

Metadata

Metadata

Labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions