axe-core: Question: Radio inputs with the same name attribute value must be part of a group (false positive?)

https://dequeuniversity.com/rules/axe/1.1/radiogroup

We have some markup with nested radio buttons that are generating the above error using the Chrome extension. The only way we have found to resolve it is to add an identical aria-labelledby attribute to each radio button in the group referencing a common label. However, our belief is that this does not give a good experience as we would like to include more contextual information for each radio button by using an aria-label or unique aria-labelledby attribute for each radio.

The example that demonstrates our issue is a slightly modified version of this WCAG role=“radiogroup” example, which has been modified to include additional input type=“text” fields in each sub group which matches our requirements.

https://www.w3.org/WAI/WCAG20/Techniques/working-examples/ARIA17/grouping-roles-example.html

The first version shown is the WCAG example with input type=“text” fields added. It is using span’s with role=“radio” and interestingly this passes the aXe validation.

<div role="radiogroup" aria-labelledby="alert2">
    <p id="alert2">Send an alert when a charge exceeds $ 250</p>
    <div>
      <input type="text" name="text1" aria-label="text1">
      <span role="radio" aria-labelledby="a2r1" name="a2radio" tabindex="0" aria-checked="false"></span>
      <span id="a2r1">Yes</span>
    </div>

    <div>
      <input type="text" name="text2" aria-label="text2">
      <span role="radio" aria-labelledby="a2r2" name="a2radio" tabindex="-1" aria-checked="false"></span>
      <span id="a2r2">No</span>
    </div>
</div>

However, if you change the example to use actual radio buttons which more closely matches our desired markup, it fails with the error listed in the title. If you remove the additional input type="text fields, then it successfully passes aXe validation.

<div role="radiogroup" aria-labelledby="alert2">
    <p id="alert2">Send an alert when a charge exceeds $ 250</p>
    <div>
      <input type="text" name="text1" aria-label="text1">
      <input type="radio" aria-labelledby="a2r1" name="a2radio" tabindex="0" aria-checked="false"></input>
      <span id="a2r1">Yes</span>
    </div>

    <div>
      <input type="text" name="text2" aria-label="text2">
      <input type="radio" aria-labelledby="a2r2" name="a2radio" tabindex="-1" aria-checked="false"></input>
      <span id="a2r2">No</span>
    </div>
</div>

I understand that this markup might be questionable, given the nesting and different types of inputs in the role=“radiogroup” grouping element. I’ve seen other scenarios where aXe flags an error in situations like that due to unassociated inputs or something. However, NVDA recognises the radio button grouping still in the second example. Also it seems inconsistent at least that aXe does not treat the above two scenarios the same?