[b49b2e] Accessibility support note on empty headings being exposed

[daniel-montalvo]

<< Describe the changes >>

Adds a note to explain that empty headings are exposed in a screen reader / browser combination, and corrects a typo on a success criteria name.
Closes issue(s):

• closes [b49b2e] Heading is descriptive - Inapplicable examples #2258

Need for Call for Review:
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). >>

---

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.

[netlify]

✅ Deploy Preview for act-rules ready!

Name	Link
🔨 Latest commit	85dd9cb
🔍 Latest deploy log	https://app.netlify.com/projects/act-rules/deploys/6904ad4bb8eff100087d6b9c
😎 Deploy Preview	https://deploy-preview-2351--act-rules.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[WilcoFiers]

This is fine, but can you also open an accessibility support issue related to this with the test information showing what the problem was so we can re-test it in the future?

Opened #2361

[daniel-montalvo]

@WilcoFiers

I Opened #2361. Can we proceed with this now?

[Jym77]

Call for Review ends on January 15th.

[giacomo-petri]

This PR is not solving the original issue I raised. I'd like to discuss it more during our CG meeting because, although we now have an accessibility support note, the inapplicable examples 3 and 4 still fail WCAG for certain UA/AT combinations. With this rule, we are effectively forcing authoring tools not to report the issue, since an inapplicable result cannot fail for consistency.

[WilcoFiers]

@giacomo-petri The group has discussed this and concluded that this is not a failure of 2.4.6. It is appropriate to and necessary to have these as inapplicable examples. Arguably these can be a 1.3.1 issues, but since the rule does not map to 1.3.1 there is no reason tools couldn't fail it there.

See the conclusion here: #2258 (comment)

If you feel strongly we need to discuss this again I think we can, but the task force came to this conclusion unanimously, so I'm personally not very keen to reopen that conversation again.

[giacomo-petri]

I see that the request related to this in WCAG 2.x is still open and marked as "in progress". Based on the discussion, it seems anything but resolved. Additionally, the last draft response (neither approved not confirmed - but still the unique there) states the opposite of what we are saying here. Given this, I'm not comfortable closing this issue in its current state.