Allow previous jobs to define the a11y_urls
Problem to solve
As a developer using GitLab with Review Apps, I want to be able to define the URL to scan for a11y issues through a CI job, so that I can check for accessibility issues before merging a new feature.
Intended users
When working on a new feature deployed to a Review location, accessibility issues are spotted before merging it in to the main branch and being Continuously Delivered.
Proposal
In addition to relying on an a11y_urls
environment variable, allow the pipeline to define the relevant URLs using environment_url.txt
like DAST (or through a different file if there might be use cases where a given URL needs to be scanned by DAST but not for a11y issues or vice versa).
Further details
Permissions and Security
I presume that, since this is consistent with the DAST setup, the same considerations should apply.
Documentation
It should be mentioned here, I guess: https://docs.gitlab.com/ee/user/project/merge_requests/accessibility_testing.html
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
\label feature