PR related to #2119. As has been discussed a few times in TF and CG, empty headings is not a failure of 1.3.1, at least not anymore as far as we know. Assistive technologies consistently ignore empty headings now.
However there is a requirement in ARIA that says headings, among various other things require an accessible name. As part of #2119 we'd like to add such a rule. This would be a more generic rule covering all cases where accessible names are required. Instead of deprecating this rule and adding it back in later, at TPAC we talked about changing the Heading not empty rule to map exclusively to ARIA, and deprecating it once the broader rule is completed.
Need for Call for Review: 2 weeks
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.
PR related to #2119. As has been discussed a few times in TF and CG, empty headings is not a failure of 1.3.1, at least not anymore as far as we know. Assistive technologies consistently ignore empty headings now.
However there is a requirement in ARIA that says headings, among various other things require an accessible name. As part of #2119 we'd like to add such a rule. This would be a more generic rule covering all cases where accessible names are required. Instead of deprecating this rule and adding it back in later, at TPAC we talked about changing the Heading not empty rule to map exclusively to ARIA, and deprecating it once the broader rule is completed.
Need for Call for Review: 2 weeks
How to Review And Approve