[Sourcing-2][Accessibility: ACC-264.1][WIP] Table: Row details not associated to header

[divyamalhotra488]

Is this a bug, enhancement, or feature request?

Bug

Describe your proposal.

Component having issue: https://sap.github.io/fundamental-ngx/#/platform/table/basic
When the user access a single row of the table , it is observed that the row values are not associated to its header and only the cell values are mentioned. The row values of the table should always be associated to header to get the complete information.

Can you handle that on the application side

No

Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)

All versions.

If this is a bug, please provide steps for reproducing it; the exact components you are using;

Using Screen reader can check by implementing similar case. Just use table and access a single row of the table , it will be observe that the row values are not associated to its header and only the cell values are mentioned by screen reader

Please provide relevant source code (if applicable).

Please provide stackblitz example(s). here

Open the app with screen reader and try to read the table values.
It is observed that the row values are not associated to its header. As per accessibility team row values of the table should always be associated to header to get the complete information

In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.

Yes we have got this bug from Accessibility expert only.

Did you check the documentation and the API?

Yes

Did you search for similar issues?

Yes

Is there anything else we should know?

Creating new defect since previous defect was closed without fix: #11266

IMPORTANT: Please refrain from providing links or screenshots of SAP's internal information, as this project is open-source, and its contents are accessible to anyone.

[droshev]

@divyamalhotra488 What has changed from what you reported in the original issue?

[divyamalhotra488]

Hi @droshev, I have created the issue again since #11266 was closed by you and we again got same defect in recent accessibility scan.
I will ask an accessibility team expert to comment here.

[droshev]

For us (as documented here and here) there is no issue. If you need us to do something you would need to provide different example where the is reproduced.