[ ViewSettingsDialog ]: accessibility issues it should announce the updated settings
@plamenivanov91 is already working on this.
Since Jun 18, 2026.
Assessment
This issue has not been assessed yet.
Description
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.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 285
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 59
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from UI5/webcomponents
-
bug Low Prio TOPIC B
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UI5/webcomponents#14061 · 1 comment ·
-
ACC TOPIC RD
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
UI5/webcomponents#14004 · 2 comments ·
-
bug TOPIC B
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UI5/webcomponents#13888 · 2 comments ·
-
bug High Prio TOPIC Core
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UI5/webcomponents#13661 · 1 comment ·
-
feature request Medium Prio TOPIC RL
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UI5/webcomponents#4619 · 3 comments ·
All issues in UI5/webcomponents
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·