Skip to content

ACT 2.4.6 atomic rule Update#2425

Draft
grifare wants to merge 20 commits into
act-rules:developfrom
grifare:grifare-patch-1
Draft

ACT 2.4.6 atomic rule Update#2425
grifare wants to merge 20 commits into
act-rules:developfrom
grifare:grifare-patch-1

Conversation

@grifare

@grifare grifare commented Jun 30, 2026

Copy link
Copy Markdown

<< Describe the changes >>

Closes issue(s):

  • closes #XXX (ADD ISSUE NUMBER HERE)

Need for Call for Review:
<< choose one of the following and remove the rest >>
<< check Process Document on Call for Review >>
This can be merged with 1 approval << choose reason: editorial changes to website/test code, adding new contributor, other (explain). >>
This will not require a Call for Review << choose reason(s): editorial changes (including to the applicability, expectation or examples section), changes to assumptions, background, accessibility support, change to website/test code (not rule), other (explain). >>
This will require a 1 week Call for Review << small changes affecting a small number of examples, if in doubt do not use this. >>
This will require a 2 weeks Call for Review << new rule, or substantial changes affecting a large number of examples, if in doubt, use this. >>


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".
  • If your PR is for a new rule with an Accessibility Support note, or for updating the Accessibility Support note of an existing section, make sure to open a corresponding Accessibility Support issue.

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.

grifare added 8 commits June 29, 2026 11:23
This is work-in-progress still at its early stage, more examples will be added, some may be removed. Everything is open to discussion.
Updated the description and applicability of the heading relevance rule to clarify its requirements and scope.
Added authors to acknowledgments and clarified rule scope.
Updated the description for clarity and improved the explanation of the rule's evaluation criteria. Added sections on assumptions, limitations, and exceptions to provide more context.
@CLAassistant

CLAassistant commented Jun 30, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@netlify

netlify Bot commented Jun 30, 2026

Copy link
Copy Markdown

Deploy Preview for act-rules failed.

Name Link
🔨 Latest commit d97d76d
🔍 Latest deploy log https://app.netlify.com/projects/act-rules/deploys/6a4566fc70136b0007f0428a

@grifare grifare changed the title Grifare patch 1 Update WCAG 2.4.6 atomic rule Jun 30, 2026
@grifare grifare changed the title Update WCAG 2.4.6 atomic rule ACT 2.4.6 atomic rule Update Jun 30, 2026
grifare added 12 commits June 30, 2026 11:02
Examples section (work-in-progress)
Text reviewed until Passed (situation D)
Updated comments in HTML examples for consistency by adding periods at the end of sentences.
Updated comments in HTML examples to remove unnecessary punctuation.
Clarified the definition of 'content' in relation to headings and corrected a comment in the passed example.
Updated the wording and structure of the rule to clarify the applicability and expectations regarding headings. Modified limitations and exceptions.
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.

2 participants