# Bug: `aria-required-children` incorrectly flags WAI-ARIA 1.2 `table` example with `caption`

### Product

axe Extension

### Product Version

4.12.1

### Latest Version

- [x] I have tested the issue with the latest version of the product

### Issue Description

## Expected Behavior

The following example should not trigger an `aria-required-children` violation.

The markup is taken directly from the WAI-ARIA 1.2 specification for the `caption` role:

https://www.w3.org/TR/wai-aria-1.2/#caption

The `table` contains the required `rowgroup`, `row`, `columnheader`, and `cell` roles, and also includes a `caption` as shown in the specification.

## Actual Behavior

axe-core reports an `aria-required-children` violation on the element with `role="table"`.

We first encountered this while investigating a customer-reported accessibility issue. To verify whether the issue was specific to our implementation, we recreated the example directly from the WAI-ARIA specification. The same violation was reported.

## Reproduction

1. Create a page containing the following markup.
2. Run axe DevTools or axe-core.
3. Observe that `aria-required-children` reports a violation on the `role="table"` element.

```html

Does this issue happen with every page?
No.
The issue appears when a role="table" contains a role="caption" as demonstrated in the WAI-ARIA 1.2 specification.
Additional Information
Based on the WAI-ARIA 1.2 specification, caption appears to be a valid structural component of an ARIA table. Because the example above is copied directly from the specification, we expected it to pass the aria-required-children rule.
If this behavior is intentional, clarification on how the specification example should be interpreted would be appreciated. Otherwise, this appears to be a potential false positive in the aria-required-children rule.
z

Start with the aria-required-children rule and reproduce the provided WAI-ARIA 1.2 table and caption markup in axe-core. Trace why role="caption" is reported under role="table", then add coverage showing the specification example is accepted and verify that the violation no longer occurs.

Written by the indexing model from the issue text.