508 Compliance Scan in CI/CD or in Groundwork Lib Files

[krowvin]

Working on #95 I thought of this:

Should there be some sort of Error system that checks for 508? Either within the lib to make sure various labels are set

OR

Should we write a js script that checks all this in the CI/CD to ensure 508 is met before deployment?
i.e. crawl the various components pre-build using jest or some sort of testing framework/linter to enforce compliance based on set findings we define as we learn what exists out there.

[adamscarberry]

suggest we use eslint-plugin-jsx-a11y and run linter on PR creation (via github workflow).

However first we should resolve issues found with npm run lint before adding this plugin, otherwise we'll have a long laundry list of issues to resolve.

[willbreitkreutz]

so we have it: https://www.digitala11y.com/free-accessibility-linters-to-automate-accessibility-workflow/

[willbreitkreutz]

Lets reassess, I think the href needs removed from the castle when on the home page in the header

[krowvin]

Setup headless Lighthouse scan for groundwork in github actions