Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Text has minimum contrast" [afw4f7] and "Text has enhanced contrast" [09o5cg]: updated scenario for non-text content #2155

Conversation

giacomo-petri
Copy link
Collaborator

The current example in Text has minimum contrast and Text has enhanced contrast "----=====++++++++___________***********%%%%%%%%%%%±±±±@@@@@@@@" does not depict a realistic scenario.

I have updated the example by incorporating a button featuring an "X" symbol to enhance clarity regarding the specific test's intention. Additionally, I have included a reference to 1.4.11 Non-Text content for further tests.

Closes issue(s):

Need for Call for Review:
This will require a 1 week Call for Review


Pull Request Etiquette

When creating PR:

  • Make sure you're requesting to pull a branch (right side) to the develop branch (left side).
  • Make sure you do not remove the "How to Review and Approve" section in your pull request description

After creating PR:

  • Add yourself (and co-authors) as "Assignees" for PR.
  • Add label to indicate if it's a Rule, Definition or Chore.
  • Link the PR to any issue it solves. This will be done automatically by referencing the issue at the top of this comment in the indicated place.
  • Optionally request feedback from anyone in particular by assigning them as "Reviewers".

When merging a PR:

  • Close any issue that the PR resolves. This will happen automatically upon merging if the PR was correctly linked to the issue, e.g. by referencing the issue at the top of this comment.

How to Review And Approve

  • Go to the “Files changed” tab
  • Here you will have the option to leave comments on different lines.
  • Once the review is completed, find the “Review changes” button in the top right, select “Approve” (if you are really confident in the rule) or "Request changes" and click “Submit review”.
  • Make sure to also review the proposed Call for Review period. In case of disagreement, the longer period wins.

Copy link
Collaborator

@dan-tripp-siteimprove dan-tripp-siteimprove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In particular I like how you changed the enhanced example's colors so that they pass the minimum rule and fail the enhanced rule.

@Jym77
Copy link
Collaborator

Jym77 commented Jan 25, 2024

Looks good. Not approving since there is already one approval from Siteimprove.

_rules/text-contrast-afw4f7.md Outdated Show resolved Hide resolved
@giacomo-petri
Copy link
Collaborator Author

Call for review ends on February 21st.

@Jym77 Jym77 added Review Call 1 week Call for review for small changes and removed reviewers wanted labels Feb 13, 2024
@Jym77
Copy link
Collaborator

Jym77 commented Feb 29, 2024

@giacomo-petri I seem to be unable to solve the merge conflict myself since the PR is on a fork. Can you fix it (update the sc143 ref to use WCAG 2.2 instead of WCAG 2.1)?

@giacomo-petri
Copy link
Collaborator Author

@giacomo-petri I seem to be unable to solve the merge conflict myself since the PR is on a fork. Can you fix it (update the sc143 ref to use WCAG 2.2 instead of WCAG 2.1)?

Hi @Jym77,
i don't see any WCAG 2.1 reference in the docs I have edited.

@Jym77
Copy link
Collaborator

Jym77 commented Mar 1, 2024

🤔 It looks like I did in fact manage to resolve the merge conflict…

@Jym77
Copy link
Collaborator

Jym77 commented Mar 1, 2024

Call for Review has ended, merging.

@Jym77 Jym77 merged commit 40058d7 into act-rules:develop Mar 1, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Review Call 1 week Call for review for small changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"Text contrast" [afw4f7, 09o5cg]: Should rule apply to X for close?
5 participants