UI5 / UI5/webcomponents

[Popover]: Improve Accessibility of Popover Component for Screen Readers

Open
#11,211 4 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

feature request TOPIC RD
Dominant language
TypeScript
Stars
1.8k
Forks
285
Avg merge
3d 2h
Merged PRs (30d)
59

Description

Describe the bug

The current implementation of the Popover component is not accessible for screen reader users. Screen readers are unable to detect or read the content displayed inside the Popover, which results in a poor user experience for users relying on assistive technologies.

Note: Issue is only reproducible via JAWS. MacOS screen readers work properly

Isolated Example

https://stackblitz.com/edit/github-o8ow4gct?file=src%2FApp.tsx

Reproduction steps

...

Expected Behaviour

When the Popover is opened, screen readers should be notified and able to read its content in full.

The Popover content should be semantically structured and navigable (e.g., sections, headings, forms, lists).

Focus should be properly managed when the Popover opens and closes (e.g., focus is trapped inside while open and returns to the triggering element on close).

Appropriate ARIA roles and attributes should be used to convey the role and structure of the Popover content.

Screenshots or Videos

No response

UI5 Web Components for React Version

2.8

UI5 Web Components Version

2.8

Browser

Chrome

Operating System

Windows

Additional Context

No response

Relevant log output

Organization

No response

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.