Closed bonniegso closed 2 years ago
Dear Colleagues,
I have corrected the example: https://stackblitz.com/edit/js-w8ckdd?file=index.js,index.html
The issue is reproducible only with NVDA, not with JAWS. I did not find any problem with the coding and this is probably a NVDA limitation.
Could you please with your ACC expert that the markup is correct and close this?
Regards, Martin
Hi @MapTo0,
It is only reproducible on NVDA, however, I think this issue might be fixable. NVDA reads "clickable" if there is a click handler on the element. Can you please verify that there is no click hander for the dialog header?
Thanks, Bonnie
@bonniegso
In my opinion, it would be super strange if click handlers (javascript) affect the behaviour of a tool that reads just the markup (html). I believe this should not be the case here.
Regards!
Hi,
Please check the answer here: https://github.com/SAP/ui5-webcomponents/issues/5601#issuecomment-1223939324
Best, Teo
Bug Description
When navigating in browse mode with the screen reader, NVDA, the header text is read as "clickable heading level 2" when the header text is not clickable.
Expected Behavior
The screen reader should only read "heading NVDA should announce"heading level 2" when user navigates to the header text in screen reader browse modes.
Steps to Reproduce
Isolated Example
https://stackblitz.com/edit/js-34awxd
Context
Priority
The priority indicates the severity of the issue. To set the appropriate priority consider the following criteria:
Note: The priority might be re-evaluated by the issue processor.
Stakeholder Info (if applicable)