[Object Page]: [A11y] Invisible heading needs to be present visually.
Describe the bug
In JAWS browse mode, invisible headings are announced after the tab section, but they remain hidden from view.
In the UI5 framework, however, the invisible headings are visible. For reference, you can view the UI5 documentation here: UI5 Reference.
Consistency is crucial for accessibility (A11y), so I am raising this issue to request an alignment with the UI5 design. It is important to provide a visible heading instead of an invisible one.
Isolated Example
No response
Reproduction steps
- Go to https://ui5.github.io/webcomponents-react/v2/?path=/docs/layouts-floorplans-objectpage--docs
- Check that tab section's first section heading is invisible.
Expected Behaviour
An invisible heading needs to be present visually. As per the UI5 ref : https://ui5.sap.com/#/entity/sap.uxap.HeaderFacetPattern/sample/sap.uxap.sample.ObjectPageWithLinksAndObjectStatus
Screenshots or Videos
No response
UI5 Web Components for React Version
2.14.1
UI5 Web Components Version
2.14
Browser
Chrome
Operating System
No response
Additional Context
No response
Relevant log output
Organization
No response
Declaration
- [x] I’m not disclosing any internal or sensitive information.
Hi @VidhiNPatel
the current specifications show the behavior that is currently implemented (no visible heading for the first section). You can see this here as well: https://www.sap.com/design-system/fiori-design-web/page-types/floorplans/object-page/?external
I can send you the ressources internally, if you're interested. In case you're aware of updated specs, please let me know, otherwise this request would need to go through the Inner Source process and be synchronised with the SAP Central Design team first. In this case, please post the ticket number here for reference.
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Inactive issues will be closed after 7 days. Thanks.
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please first check to see if the maintainers have requested additional input and provide it if necessary, or post a detailed description of why this issue is still a problem.
@Lukas742 In FIORIDESIGN-11392 design has decided for a visible title. Please implement the latest specs.