Updated ARIA state or property is permitted [5c01ea]: clarified global property is allowed except when prohibited and added examples

[giacomo-petri]

Closes: #2191

Updates:

• I've amended examples like "The aria-label property is a global property. It is allowed on any semantic role," adding "except where specifically prohibited". This clarification was necessary because certain semantic roles, such as caption, code, deletion, emphasis, generic, insertion, paragraph, presentation, strong, subscript, and superscript, prohibit the use of aria-label.
• I've included a passed example demonstrating the inheritance of properties from a superclass role, as it was absent.
• I've included a failed example showcasing a prohibited global property to underscore the significance of the edit mentioned in the first bullet point.
• I've included an interesting example (both passing and failing) of the separator role, illustrating that it supports a specific property when focusable but not when static.

Need for Call for Review:
This will require a 2 weeks Call for Review

---

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.

[WilcoFiers]

I agree that ARIA says this is not allowed, but I feel there is a logical inconsistency in ARIA which makes that a questionable decision. Separators are allowed to be disabled. And when elements are disabled, ARIA says you're allowed to remove them from the focus order. But if you do that, you're suddenly no longer allowed to have these separator widget properties on it, including aria-disabled itself!

The problem is broader than just this role too. The spec says aria-disabled is applied to all focusable descendants. But then if you make an element not focusable because its disabled, according to the spec it then doesn't qualifies for inheriting that disabled state!

It's all a little too messy for my taste. I'd prefer we leave this example out. I for one wouldn't be comfortable failing this example.

[giacomo-petri]

Call for review ends January 9th 2025