ACT 2.4.6 atomic rule Update#2425
Draft
grifare wants to merge 20 commits into
Draft
Conversation
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.
Edits made until Passed example 6
❌ Deploy Preview for act-rules failed.
|
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
<< Describe the changes >>
Closes issue(s):
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:
developbranch (left side).After creating PR:
Rule,DefinitionorChore.When merging a PR:
How to Review And Approve