Issue Summary

The "Story Points" header is not programmatically associated with sub-column data cells.

Steps to Reproduce

1. Open the Jira Cloud homepage.
2. Select any Scrum board, then navigate to and activate the "Reports" tab within the Space navigation.
3. Now activate "More reports" button and select "Burndown chart".
4. Activate the "More reports" button and choose the "Burndown chart" option.
5. Using a screen reader, navigate to the "Sprint scope change event breakdown" table.
6. Navigate to the "Inc", "Dec", and "Remaining" cells.
7. Observe that the data within these cells is not associated with their respective headers.

Screenshot

Actual Results

The table structure of the "Sprint scope change event breakdown" table is inappropriate:

• The data values for Inc., Dec., and Remaining are placed as <div> elements within a single <td> cell, making them indistinguishable to screen readers.
• The "Story Points" header spans three columns using colspan="3", but the data cells are not programmatically associated with both the parent header ("Story Points") and their respective sub-headers (Inc./Dec./Remaining).

As a result, screen reader users cannot interpret the table's sub-columns or understand which value belongs to which column.

Expected Results

The content of the table should be correctly announced by screen reader for their users.

Ensure that each value (Inc., Dec., Remaining) is contained in its own <td> cell with a "headers" attribute referencing both the parent "Story Points" header and the respective sub-column header. 

Code Snippet:

<table>
<thead>
<tr>
...
<th colspan="3" id="series-field_customfield_10033" class="">Story Points</th>
</tr>
<tr> 
...
<th id="series-field_customfield_10033-inc" ...>Inc.</th>
<th id="series-field_customfield_10033-dec" ...>Dec.</th>
<th id="series-field_customfield_10033-value" ...>Remaining</th>
</tr>
</thead>

<tbody>
...
<td headers="series-field_customfield_10033 series-field_customfield_10033-inc">5</td>
...
</tbody>
</table>

Note: This code example is intended only as a general illustration of how to address the violation and should not be considered a complete or production-ready solution. If you have any questions, please attach this ticket to a #help-accessibility request.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.

Environment

MacBook Pro (16 inch, 2021)
macOs 26.5.1
Windows - 11 pro
Chrome - Version 148.0.7778.97 (Official Build) (arm64)
Safari - Version 26.5 (21624.2.5.11.4)
JAWS - Version 2026
NVDA - Version 2024.4.2.35031
Voiceover - Version Latest