[ui5-carousel]: [a11y] heading levels within carousel are not being announced by screenreader
Bug Description
Child items that either have a section heading tag, or an element with both role = "heading" and aria-level set do not have their heading level announced by a screen reader when placed in a carousel.
Affected Component
ui5-carousel
Expected Behaviour
All items with a section heading tag or with role = "heading" and aria-level set should be announced as a header with their heading level by the screenreader.
Isolated Example
https://codesandbox.io/p/sandbox/laughing-browser-l72jfg?file=%2Fsrc%2FApp.js%3A18%2C18
Steps to Reproduce
- Open JAWS or NVDA screenreader and navigate to https://codesandbox.io/p/sandbox/laughing-browser-l72jfg?file=%2Fsrc%2FApp.js%3A18%2C18
- if using JAWS press the h button to loop through all the headers. Verify that the headers within the carousel aren't read out.
- Then, tab to the carousel items.
- Verify that the carousel items aren't announced as headers or with a heading level ...
Log Output, Stack Trace or Screenshots
No response
Priority
None
UI5 Web Components Version
1.23.0
Browser
Chrome
Operating System
Mac OS
Additional Context
No response
Organization
No response
Declaration
- [X] I’m not disclosing any internal or sensitive information.
Hello @SAP/ui5-webcomponents-topic-rd team,
Could you check this issue about the carousel and the heading levels not announced by screen readers (using PC cursor)?
https://stackblitz.com/edit/js-ddvktp?file=index.js,index.html
Thanks and Best Regards, Dobrin
<div role="listbox" tabindex="0" aria-activedescendant="lvl4">
<div role="option" aria-posinset="1" aria-setsize="2">
<h2>hello world</h2>
</div>
<div id="lvl4" role="option" aria-posinset="2" aria-setsize="2">
<h4>hello wolrd</h4>
</div>
</div>
Hello @I585157,
This issue will be handled with this backlog item - FIORITECHE1-8307 - Follow for updates here.
As this is not an issue, but needs an accessibility redesign i am closing the github issue.
Best Regards, Gergana
:tada: This issue has been resolved in version v2.9.0-rc.0 :tada:
The release is available on v2.9.0-rc.0
Your semantic-release bot :package::rocket: