Issue Summary

The sortable functionality provided on the page which is not defined programmatically.

Steps to Reproduce

1. Navigate to the "Plans" dropdown and select any plan.
2. Navigate to the table section using screen reader.
3. Ensure that sort functionality is not getting identified.

Screenshot

Actual Results

On activating the "Target start", "Target end", "Status", and "Assignee", the content within the table gets sorted dynamically.
Although the dynamic change in the content is easier to understand for sighted users, it is not intuitive for screen reader users.

Expected Results

Ensure that the sort state is programmatically defined for the sortable columns.
Apply the following changes: * Provide the sort state using the "aria-sort" attribute on the <th> element.

• Set the value of "aria-sort" to "ascending" when the content is sorted in ascending order.
• Set the value to "descending" when the content is sorted in descending order.
• If no sorting is applied on the content, set the value to "none".
• Ensure that the sort state is updated on user interaction.

 
For information on accessible sort controls, visit https://www.w3.org/WAI/ARIA/apg/example-index/table/sortable-table
 
Code Snippet

<th aria-sort="none">
<div role="button" data-name="section-none" class="_3WCnc" style="width: 176px;"> tabindex="0"(...)<span class="_Mq3F">Target start</span>(...)</th>

Workaround

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

Environment

MacBook Pro (16-inch, 2019)
macOS Ventura Version 13.6.1
Chrome - Version 120.0.6099.234 (Official Build) (x86_64)
Firefox- Version 112.0.1 (64-bit)
Safari- Version 17.3 (18617.2.4.11.9, 18617)
JAWS- Version 2022
NVDA- Version 2020.3