[ ViewSettingsDialog ]: accessibility issues it should announce the updated settings

[raoakash01]

Bug Description

[ ViewSettingsDialog / View Columns Settings ]: accessibility issues it should announce the updated settings.

It is observed that Sorting update on table is not announced for screen reader users, there is no indication of current state of sorted column
Column update on table is not announced for screen reader user
This changes are visible for sighted users however there is no invisible notification of the same for screen reader user

Affected Component

ViewSettingsDialog / View Columns Settings/ Table

Expected Behaviour

Where dynamic content is updated either automatically or in response to a user action, make sure that users are notified of this update. Ensure Screen reader users are notified about dynamically added contents on the page.
A invisible success message such as Column added/the current state of the header column (name of column) is sorted in ascending order or descending order should be announced to non-sighted users, will be helpful to screen reader users.

Isolated Example

No response

Steps to Reproduce

...

Log Output, Stack Trace or Screenshots

No response

Priority

None

UI5 Web Components Version

2.22.0

Browser

Chrome

Operating System

No response

Additional Context

No response

Organization

SAP Successfactors

Declaration

• I’m not disclosing any internal or sensitive information.

[plamenivanov91]

Hello Colleagues,

Can you improve the ACC behaviour for the ViewSettingsDialog?

Not sure if this is bug or enhancement.

Here is also the AI recap:

Based on the issue, this is an accessibility bug in the ViewSettingsDialog component (packages/fiori).
The problem is that when a user changes sorting or column visibility via the dialog, screen readers get no announcement of the resulting table state change.

The fix needs to happen in two places:

1. ViewSettingsDialog — after the dialog confirms and fires its confirm event, it should emit a live-region announcement (e.g. "Sorted by Name, ascending" or "Column Supplier added/removed"). This is the primary component responsible for orchestrating the changes.

2. Table (packages/main) — the table's sort header state (aria-sort on <th>) may also need updating so the new column sort state is machine-readable, not just visually indicated. But the proactive announcement belongs in ViewSettingsDialog since that's where the user action originates.

The typical fix pattern in this codebase is to use the announce utility from @ui5/webcomponents-base to inject a visually-hidden message into an aria-live region after the confirm event fires.

Could you please take over?

Regards,
Plamen Ivanov