Publishing Accessibility Reports in GitLab Pages

GitLab emphasizes the principle that everyone can contribute and aims to streamline the development process by delivering test data to developers promptly. The introduction of Automated Accessibility testing in GitLab is part of this effort, allowing developers to identify accessibility issues quickly after deploying changes to a review application. A template has been created to simplify the integration of accessibility testing into GitLab pipelines, which can be included in the project's .gitlab-ci.yml file. This setup aims to minimize cycle time by running the accessibility job after deployment to staging. The accessibility scan results are made visible on the Merge Request page using the artifacts:expose_as keyword, providing developers with easy access to detailed reports from the Pa11y engine. To broaden accessibility report sharing across the organization, the GitLab Pages feature can be used to publish the report consistently at the same URL. After some trial and error, adjustments were made to the .gitlab-ci.yml file to successfully deploy and publish the report via GitLab Pages, enhancing visibility and accessibility for team members.

No tracked trend matches for this post yet.