aria-labelledby not respected on any table elements - column headers, row headers, cells

[Epic-Third-Party-Bug-Reporting]

Description

JAWS doesn't appear to be calculating the accessible name for table elements, just reading their contents.
May be related to #656.

Version Info

JAWS version: Tested with JAWS 2024.2411.16 and JAWS 2025.2412.50, both had this problem.
Browsers: Reproduced on Chrome 131.0.6778.266 and Firefox 134.0.1.
OS: Windows 11, version 24H2.

Expected result

Column headers, row headers, and cells would prioritize aria-labelledby when calculating the accessible name and read that.

Actual result

Only reads cell contents.

See this test codepen.

[JAWS-test]

I have tested with the latest Chrome and JAWS 2025. When I use the table navigation (ALT+CTRL+arrow keys), the aria-labelledby is output before the cell content. When reading linearly using only the arrow keys, aria-labelledby is not output.

But I think the main problem here is the ARIA specification, which does not clearly say whether a table row or cell is a container role (like a landmark region, which can be labeled by aria-labelledby and whose content must still be perceptible) or a role for a concrete element (like a button, which can only be explicitly labeled either by aria-labelledby or by text content, but where both are never perceptible).

[JAWS-test]

See: w3c/aria#683

[JAWS-test]

NVDA never outputs the aria-labbeledby, not even for table navigation. This seems even better to me because it is consistent.