[Sourcing][Accessibility][Multi input Mobile mode dialog]Popup contains unnecessary regions

[I543348]

Is this a bug, enhancement, or feature request?

Bug

Briefly describe your proposal.

The popup contains unnecessary regions (e.g.

at the end): It was not error, only a note and good to have. Regions should only be used to structure large content areas. Regions are output by the screen reader. In a small pop-up, it is rather annoying if the button is focused at the end and a region is also output.

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

If this is a bug, please provide steps for reproducing it.

Regions should only be used to structure large content areas. Regions are output by the screen reader. In a small pop-up, it is rather annoying if the button is focused at the end and a region is also output. tested on multi input value help dialog footer area

Please provide relevant source code if applicable.

Is there anything else we should know?

reported by customer

[droshev]

@I543348 Can you provide more context information and screenshots?

[I543348]

Hi @droshev ,This is a customer testing issue. We had discussed this and triaged the issue along with ATL. Could you please connect with them for more details?

Thanks.

[droshev]

@I543348 The agreement is that you provide us with all the input so we can work on the issue.

[nikolay-kolarov]

Hi,

I checked the dialog (MultiInput on Mobile -> value help) and there is a footer element, which is a landmark element and forms a region for Jaws https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA11. In this case the header even is missing otherwise the customer might have complained that there are two regions.

Still, this is an on-purpose decision to have a header and footer in the dialogs in order to have a common consistent structure. And this is used across UI5 and UI5 WebComponents dialogs.

So I think we can close this one.

Best Regards, Nikolay

[I543348]

ATL Re-verification needed

[sagar7259]

Hello,

This can be documented as a note and close this issue has this is an on-purpose decision to have a header and footer in the dialogs in order to have a common consistent structure. And this is used across UI5 and UI5 WebComponents dialogs has per the comment from Nikolay.

Regards, Sagar