sap.m.Dialog title renders role="heading" without aria-level, failing WCAG 1.3.1

[boydlaw80-byte]

What is the issue and how can we reproduce it?

sap.m.Dialog renders its title property internally as a element without an aria-level attribute. This is flagged by accessibility scanners (e.g. Axe, WAVE) as a violation of WCAG 1.3.1 (Info and Relationships) since headings must have a defined level to convey structure to screen reader users.

Steps to reproduce:

Create a sap.m.Dialog with a title property set
Open the dialog in the browser
Inspect the DOM — the title renders as with no aria-level
Run an accessibility scan (Axe or WAVE) — it reports "No heading level defined"
Expected: The dialog title includes aria-level="2" (or a titleLevel property is exposed so developers can control it, similar to sap.m.Panel and sap.m.Page)

Actual: is rendered without aria-level

Which OpenUI5 version is your project targeting?

Latest (no pinned version, loaded from ui5.sap.com CDN)

Is the issue device- or browser-specific?

Not device- or browser-specific, reproducible across all browsers and devices.

Confirmation

• I have searched the existing issues and reviewed the relevant documentation as well as the API reference.
• I am not disclosing any internal or sensitive information.

[unazko]

Hello @boydlaw80-byte,

I've tried to reproduce the issue in the demokit samples: https://ui5.sap.com/#/entity/sap.m.Dialog/sample/sap.m.sample.Dialog
but wasn't able to.

That sap.m.Dialog's title is rendered as h1 element so it doesn't need aria-level attribute to indicate a heading semantics as it already has such.

I've tried with AMP and AXE tool with best practices turned on and I didn't receive a report for the heading levels.
Can you provide a screenshot with the AXE tool report and a sample to reproduce the issue if such exists in the demokit: https://ui5.sap.com/#/entity/sap.m.Dialog/sample/sap.m.sample.Dialog

Best regards,
Boyan

[didip1000]

Hi @boydlaw80-byte,

Since this ticket has been in author-action with no reply for over a month, I will be closing the ticket. If this issue is still relevant, please don't hesitate to re-open the issue.

Best,
Diana