[SF][A11y][Popover] Content isn't read by screen reader when popover contains text only

[Neeeko]

Bug Description

When opening a ui5-popover which contains text only and no focusable element, the content of this popover is not announced by most screen readers. (NVDA will read it properly but not VoiceOver or JAWS).

Expected Behavior

When opening a popover which doesn't contain focusable element but textual content only, the content of the popover should be announced by the screen reader

Steps to Reproduce

1. Using JAWS or VoiceOver (as NVDA announces it properly)
2. Open: https://codesandbox.io/s/ui5-webcomponents-forked-ys6b7?file=/index.html
3. Navigate to the button and use keyboard to open the popover
4. Content is not read

Context

• UI5 Web Components version: 1.1.0
• OS/Platform: MacOS
• Browser: Google Chrome
• Affected component: Popover

Priority

• Low
• Medium
• High
• Very High

The priority indicates the severity of the issue. To set the appropriate priority consider the following criteria:

• Breaks entire application or system - High or Very High
• Accessibility issue - Medium or High
• Functional issue - Medium or High
• Visual issue - Low or Medium

Note: The priority might be re-evaluated by the issue processor.

Stakeholder Info (if applicable)

• Organization: SuccessFactors

[ivoplashkov]

Hello @SAP/ui5-webcomponents-topic-rd, the issue is reproducible as described.
Could you please have a look?

Best regards,
Ivaylo

[rchrdchn]

Hey guys – just following up on this issue. When could we expect the fix for this issue?

[rchrdchn]

Following up here. Any updates?

[georgimkv]

Hi,
We're currently working on this issue. We'll let you know when there's an update on the matter.

[GerganaKremenska]

Hello Neeeko,

Pull request 4517 intoroduces the way for static content to be read out by screen readers.

This functionality does not come out of the box as a WC can not know what is it in its content, we have provided accessibile-name-ref, so developers can link static content.

The feature is available from v1.1.0.

Here is an updated code sample to use as a refferance.

Best Regards,
Gergana

[Neeeko]

Hi @GerganaKremenska,

The issue still seems to exist with JAWS where the content of the popover isn't read even with the accessible-name-ref attribute or using the code sample you provided - though it works with NVDA.

Can you please try to reproduce with JAWS?

Thanks!

[Neeeko]

Hi @gmkv and @ivoplashkov, can you please reopen this issue? As mentioned in my previous comment, the issue is still reproducible using JAWS.
Thanks!

[ilhan007]

Hello @GerganaKremenska @SAP/ui5-webcomponents-topic-rd can you reiterate over the issue, the author has put some new comments after the provided solution.

[GerganaKremenska]

@Neeeko,

We are looking into the issue. As all accessibility standarts are met, this may take some time resolving.

--Gery

[GerganaKremenska]

Hello @Neeeko,

After a lot of investigation we found the "issue".
NVDA, Narattor and JAWS 2021 reads out everything as expected.

JAWS 2022 does not read out the content and that is an issue that we can not handle, because it comes from the vendor of the screen reader.

I am closing the issue as there is nothing on our side that we can do.

--Gery