You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VidhiNPatel
changed the title
[ObjectPage]: [[a11y]Heading levels should only increase by one, and Heading hierarchy is not correctly defined on the page]
[ObjectPage]: [a11y]Heading levels should only increase by one, and Heading hierarchy is not correctly defined on the page
Mar 5, 2025
VidhiNPatel
changed the title
[ObjectPage]: [a11y]Heading levels should only increase by one, and Heading hierarchy is not correctly defined on the page
[SF][ObjectPage]: [a11y]Heading levels should only increase by one, and Heading hierarchy is not correctly defined on the page
Mar 25, 2025
If a form is configured inside a subsection, its title is assigned an H6 heading, skipping the H5 heading.
There's currently no API to change the heading level of FormGroups. Please open a feature request for this in the ui5-webcomponents repo, as the component is developed there.
When Tabstrip Is NOT Present:
This is not supported. An ObjectPage should always implement ObjectPageSections (except when a placeholder is rendered), if this is not required the DynamicPage can be used.
Additionally you can define the heading levels of sections and subsections yourself by setting the titleTextLevel prop.
Describe the bug
Incorrect Heading Levels in Different Scenarios
When Tabstrip Is Present for Multiple Sections Navigation:
When Tabstrip Is NOT Present:
Isolated Example
No response
Reproduction steps
1.Go to https://sap.github.io/ui5-webcomponents-react/v2/?path=/story/layouts-floorplans-objectpage--default
2. Turn on screen reader
3. Focus to Object status
4. Check the announcement
Expected Behaviour
Heading levels should only increase by one
Ensure the order of headings is semantically correct.
Screenshots or Videos
UI5 Web Components for React Version
2.7.2
UI5 Web Components Version
2.7.3
Browser
Chrome
Operating System
No response
Additional Context
No response
Relevant log output
Organization
Successfactors
Declaration
The text was updated successfully, but these errors were encountered: