Update the aria-required-owned rule [bc4a75] to include the elements with implicit roles

[shunguoy]

The original description limits the rule to the elements with explicit semantic roles only. The rule should apply to elements with either explicit or implicit roles.
The changes include the following updates: (1) the description of implicit roles; (2) test cases accordingly; and (3) other minor code cleanups.

Need for Call for Review:
This can be merged with 1 approval

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.

[CLAassistant]

All committers have signed the CLA.

[netlify]

✅ Deploy Preview for act-rules ready!

Name	Link
🔨 Latest commit	488c53a
🔍 Latest deploy log	https://app.netlify.com/sites/act-rules/deploys/681e1125244ab900085c6d4f
😎 Deploy Preview	https://deploy-preview-2318--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 site configuration.

[daniel-montalvo]

Thanks @shunguoy

Approving. Except that I think this does require a regular 2-week Call for review period.

[WilcoFiers]

I see no reason to change this. This is an important example to demonstrate explicit roles override implicit ones.

[shunguoy]

This change was in the original suggestion, I didn't hear objection during the discussion (I could be wrong). Per HTML 5, the li can only be used as a child of ul, ol, or menu. Otherwise, no list relationship is defined:

The li element represents a list item. If its parent element is an ol, ul, or menu element, then the element is an item of the parent element's list, as defined for those elements. Otherwise, the list item has no defined list-related relationship to any other li element.

This change is to make sure no confusion on the relationship, and maintain the purpose of the example at the same time.

[shunguoy]

@WilcoFiers added more Pass/Fail test cases for native elements. Please review again.

[giacomo-petri]

The applicability now includes implicit roles, but we currently lack any failing examples of them. IMO, if we intend this new applicability to focus on "semantic roles" rather than "explicit roles" only, we should include additional examples that illustrate implicit roles.

[shunguoy]

@giacomo-petri if you review the changes for the rule, I added a few examples with implicit roles: Passed Examples 7 - 9, Failed Examples 8 & 9, some with mixed explicit and implicit roles.

[giacomo-petri]

@shunguoy, yes, I've noticed the improvements. I was specifically talking and curious if we could have something similar to the Passed Example 9:

<table>
	<tr>
		<td>Item 1</td>
		<td>Item 2</td>
		<td>Item 3</td>
	</tr>
</table>

but for failing examples.

For instance, this scenario is now matching the applicability (and previously it wasn't):

<ul>
    <div></div>
    <div></div>
</ul>

however, we don’t have any examples with this kind of issue.

[shunguoy]

@giacomo-petri added this as Failed Example 10. Also added a note Note that this example is for demonstration purpose only because it's not a valid HTML 5 structure.