Support customizing ARIA role for DynamicSideContent main area

[sleric1024]

Is your feature request related to a problem?

Description

Currently, the main area of DynamicSideContent always has role="main" and this role cannot be customized.

However, in some use cases, DynamicSideContent is rendered inside an existing page content container that already defines a main landmark. In such cases, this results in multiple role="main" landmarks on the same page, which violates ARIA landmark best practices and causes accessibility issues.

At the moment, the accessibilityAttributes property only supports setting aria-label, but does not allow customization of the ARIA role.

Use Case

DynamicSideContent is used as a nested layout component, not as the top-level page container

The parent page already defines a

landmark

Screen readers encounter multiple main roles, leading to confusing navigation

Describe the solution you'd like

Proposed Enhancement
Extend accessibilityAttributes to support configuring the ARIA role of the main area, for example:

accessibilityAttributes={{
  role: "region",
  ariaLabel: "Search Results"
}}

This would give application developers more flexibility to ensure correct ARIA landmark structure in complex layouts.

Describe alternatives you've considered

or introduce a dedicated property such as:

mainAreaRole="region"

Additional Context

Benefits

Prevents invalid ARIA landmark duplication

Improves accessibility compliance

Makes DynamicSideContent more flexible when used in nested layouts

Organization

SAP-SF

Declaration

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

[Lukas742]

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.

[ndeshev]

Hello @UI5/ui5-team-ctr-bal could you please evaluate this feature request for customizable main area role of the ui5-dynamic-side-content component?