Skip to content

A11y ratchet gate - #18513

Draft
rak-phillip wants to merge 7 commits into
rancher:masterfrom
rak-phillip:a11y-ratchet-gate
Draft

A11y ratchet gate#18513
rak-phillip wants to merge 7 commits into
rancher:masterfrom
rak-phillip:a11y-ratchet-gate

Conversation

@rak-phillip

Copy link
Copy Markdown
Member

Summary

Fixes #

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

Checklist

  • The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
  • The PR has a Milestone
  • The PR template has been filled out
  • The PR has been self reviewed
  • The PR has a reviewer assigned
  • The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
  • The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
  • The PR has been reviewed in terms of Accessibility
  • The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

This introduces Introduce a ratchet mechanism for the accessibility suite. The suite already records violations via `cy.checkA11y(..., skipFailures=true)` but never enforces them. These scripts allow known failures to pass while we work on fixing known issues.

Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
This adds a ledger of accepted a11y violations for the gate to reference. It is seeded from a real a11y-test run rather than a local render.

The file lives next to the spec because `cypress/accessibility/` is gitignored.

`yarn a11y:compare` reports 102 baselined and 0 new.

Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
This runs the ratchet after the accessibility suite so new violations are surfaced on every PR.

- Upload report now runs `if: always()`, so the artifact is captured even when a test step or the gate itself fails. Without it, a failing run loses the report needed to triage it
- The new "A11y ratchet" step also runs `if: always()` and reads the `A11Y_RATCHET_ENFORCE` repo variable. Setting it to 'true' turns on hard failure for new A11y violations

Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
@github-actions

Copy link
Copy Markdown
Contributor

🔄 Auto-Retry Failed Run

The Tests workflow run 30306984849 failed and has been automatically retried.

Follow up on the retried run here if needed: https://github.com/rancher/dashboard/actions/runs/30306984849

@github-actions

Copy link
Copy Markdown
Contributor

🔄 Auto-Retry Failed Run

The Tests workflow run 30309596667 failed and has been automatically retried.

Follow up on the retried run here if needed: https://github.com/rancher/dashboard/actions/runs/30309596667

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant