User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

1. Open the attached file with a screen reader running (I used JAWS 2022).
2. Tab to the <article elements and listen to the announcement of the accessible name (you can also view the accessible name using the dev tools in firefox).

Actual results:

The name is "some text" for both <article> elements.

Expected results:

The contents of the <figure> and <article contained inside the other article should have been part of the name.
Specifically, on the first <article> with the <figure>
The name should be:
some text test caption some image

On the second <article> the name should be:
some text some image

I originally reported this as a bug to Chrome here https://bugs.chromium.org/p/chromium/issues/detail?id=1357221 but after some back and forth in this bug I am convinced this is a Firefox issue.

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0

I am able to reproduce the issue in Release 104, Beta 105.0 and Nightly 106.0a1 (2022-09-14) using Windows 10 with JAWS 2022. Note that the issue is not reproducible using NVDA. If this is not the correct component please feel free to change it to a more appropriate one.
Not a regression, I can reproduce the issue in fx66 as well.

Thanks for the report.

Just wanted to add that I can also reproduce on VoiceOver on the mac.

Similar to bug 1616851 and will have a very similar fix: change eNoNameRule to eNameFromSubtreeIfReqRule for the FIGURE role.

Just wanted to highlight the discussion in the chrome issue I linked.
https://bugs.chromium.org/p/chromium/issues/detail?id=1357221
It looks like the accessible name spec was updated and I am now back to thinking this is a chrome bug rather than a firefox bug.