[b49b2e] Heading is descriptive -- Remove inapplicable examples of empty headings#2405
Open
daniel-montalvo wants to merge 1 commit intodevelopfrom
Open
[b49b2e] Heading is descriptive -- Remove inapplicable examples of empty headings#2405daniel-montalvo wants to merge 1 commit intodevelopfrom
daniel-montalvo wants to merge 1 commit intodevelopfrom
Conversation
✅ Deploy Preview for act-rules ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Jym77
requested changes
Apr 16, 2026
Collaborator
Jym77
left a comment
There was a problem hiding this comment.
Can you add a Background note to explain this? (lack of consensus, so not taking a stance)
giacomo-petri
approved these changes
Apr 16, 2026
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.
Removes inapplicable examples of this rule where there's empty headings as there's no consensus on whether or not they should fail WCAG and, if they should fail, under wihch SC
Closes issue(s):
Need for Call for Review:
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