[Issue #677]: Add accessibility checks against pr preview env

[rylew1]

Ticket

Resolves #677

Changes

• Add accessibility checks

Run of accessibility job:

Run set -e # Ensure the script fails if any command fails

> app@0.1.0 test:pa11y-desktop
> pa11y-ci --config .pa11yci-desktop.json

Running Pa11y on 1 URLs:
 > http://p-84-app-dev-[10](https://github.com/navapbc/platform-test-nextjs/actions/runs/9812208957/job/27095994046?pr=84#step:10:11)41375336.us-east-1.elb.amazonaws.com/ - 0 errors

✔ 1/1 URLs passed

> app@0.1.0 test:pa11y-mobile
> pa11y-ci --config .pa11yci-mobile.json

Running Pa11y on 1 URLs:
 > http://p-84-app-dev-104[13](https://github.com/navapbc/platform-test-nextjs/actions/runs/9812208957/job/27095994046?pr=84#step:10:14)75336.us-east-1.elb.amazonaws.com/ - 0 errors

✔ 1/1 URLs passed
pa11y-ci tests finished.

Preview environment

• Service endpoint: http://p-84-app-dev-1041375336.us-east-1.elb.amazonaws.com
• Deployed commit: af8e2bd

[github-actions]

Coverage report for app

St.❔	Category	Percentage	Covered / Total
🟢	Statements	93.1%	81/87
🟢	Branches	82.35%	14/17
🟢	Functions	93.33%	14/15
🟢	Lines	93.59%	73/78

Test suite run success

16 tests passing in 5 suites.

Report generated by 🧪jest coverage report action from af8e2bd

[lorenyu]

Take a look at this comment on the e2e PR. I'd think that we'd want to do something similar here in order to support multiple apps and in order to be able to support running the accessibility scans outside the context of a PR environment. In other words, I think we'll want to have this workflow take an app_name input in addition to a service_endpoint input, then use that to load app-specific configurations (since different apps will have different sets of URLs).

[rylew1]

Added a quick if/else statement in the workflow

[lorenyu]

🚢

[rylew1]

I think we can close this but keep it as a reference - we moved to e2e playwright a11y instead for the platform : #85