[Accessibility] : Menu component does not support correct aria-posinset and aria-setsize for grouped items

[paresh-singh]

Bug Description

Bug Description

In LWV (Lightweight Viewer), the bookmark menu is implemented using UI5WCR Menu / MenuItem components.

We observed that the rendered menu items do not expose correct accessibility attributes such as:

aria-posinset
aria-setsize

As a result, screen readers are unable to correctly interpret:

1. the total number of items in the menu
2. the position of each item within the set

This leads to incorrect or incomplete accessibility announcements.

Actual Behavior

1. Menu items rendered via UI5WCR do not provide correct positional metadata
2. No clear way to control or override these attributes at application level
3. Grouped menu structures are not reflected properly in accessibility tree

Impact

1. Accessibility compliance issue (screen reader usability degraded)
2. Affects bookmark menu in LWV
3. Cannot be resolved at application level due to framework abstraction

Observe missing or incorrect:
aria-posinset
aria-setsize

Observed Limitation
The UI5WCR Menu abstraction does not allow:
manual control over positional ARIA attributes
proper grouping semantics required for accessibility

Affected Component

No response

Expected Behaviour

Menu items should:

1. correctly expose aria-posinset and aria-setsize
2. support logical grouping so screen readers can interpret item hierarchy and count accurately

Isolated Example

No response

Steps to Reproduce

1. Create a menu using UI5WCR Menu and MenuItem
2. Add multiple items (optionally grouped logically)
3. Inspect DOM tree

Log Output, Stack Trace or Screenshots

No response

Priority

None

UI5 Web Components Version

1.24.24

Browser

Chrome

Operating System

No response

Additional Context

This limitation blocks fixing accessibility issues in LWV bookmark menu at application level.

Organization

SAP Analytics Cloud

Declaration

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

[didip1000]

Hey @UI5/ui5-team-ctr-bal,

The ACC don't mention the attributes but the menu items in OpenUI5 do have those attributes set, so they probably need to be applied here as well.

Best,
Diana

Edit: I was looking at the old specifications, the newest IDx specs do mention everything

[didip1000]

Hey @paresh-singh,

Initially, we considered explicitly applying the ARIA attributes you listed. After testing, we did not observe any missing or inaccurate item-count or position announcements for the ui5-menu. We also consulted our a11y expert, who confirmed that screen readers derive this information from the menu’s native accessibility semantics, so additional attributes are not required.

Could you confirm whether the issue is reproducible only for ui5-menu-items in a ui5-menu-item-group? Additionally, is the version you mentioned accurate? For reference, MenuGroupItems were introduced in version 2.12.0?

If possible, please provide a minimal sample demonstrating the issue. For your convenience, you can modify this StackBlitz example: https://stackblitz.com/edit/js-vsrpnb

Thanks & Best Regards,
Diana

[paresh-singh]

Hi @didip1000,

The reason I raised this request is to address an accessibility issue identified by our QA team.

Expected behavior:

Under each header, only actionable bookmarks should be included in the item count.
Headers themselves should not be part of the list count.
Each group of actionable bookmarks under a header should be treated as a separate list, with its own correct count.

Observed behavior:
Currently, the count includes all items—actionable bookmarks, non-actionable items, and headers—rather than just the actionable ones.

I’ve also attached a screenshot to better illustrate the issue.

From an implementation perspective, I’m not sure how this can be achieved using the current setup, especially with the posinset and setsize attributes, as they seem to include all items in the calculation.

Could you please let me know if there is a recommended workaround for this? Alternatively, if this is something that can be addressed on your side, that would be very helpful.

Thanks & Regards,
Paresh