fundamental-ngx
fundamental-ngx copied to clipboard
[Sourcing-2][Accessibility: ACC-264.1] List Item: Value count not read.
Is this a bug, enhancement, or feature request?
Bug
Describe your proposal.
Component having issue: https://sap.github.io/fundamental-ngx/#/core/select Item/Value count i.e. ‘1 of 15 etc’ is not being read out, on navigating between the drop-down using arrow keys. Item count for 'Number' drop-down should be read to screen reader users
Can you handle that on the application side
No
Which versions of Angular and Fundamental Library for Angular are affected? Please, specify the exact version. (If this is a feature request, use current version.)
All latest version
If this is a bug, please provide steps for reproducing it; the exact components you are using;
Using Screen reader can check by implementing similar case. Just use any iSelect Dropdown. Item/Value count i.e. ‘1 of 15 etc’ will not being read out, on navigating between the drop-down using arrow keys.
Please provide relevant source code (if applicable).
Please provide stackblitz example(s).
In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.
Yes we have got this bug from Accessibility expert only.
Did you check the documentation and the API?
Yes
Did you search for similar issues?
Is there anything else we should know?
Hi @JyotiKumari1507,
I assume you mean when the popover with the items is not opened, right? This is the same in UI5 and for me, it is expected as the list is not visible and the announcement is made in a different way. The sighted users also do not understand how many items are in the list. https://ui5.sap.com/#/entity/sap.m.Label/sample/sap.m.sample.Label
So I think we can close this one.
Best Regards, Nikolay
@droshev Its defect as per me. Issue is when user slide down in list and can see completed list but not read out by screen reader after sliding down also. Please re-open this defect
@droshev use any dropdown using keyboard, sroll down it using keyboard down arrow. Screen reader is able to read only start few records which was visible in starting. Its not able to read which comes after scrolling down by keyboard. Attaching screenshot for same. We had syncup with Accessibility team today. As per them its defect, Please re-open this defect. Still any query please let me know we can have call
Hello @JyotiKumari1507,
I am not able to reproduce the things you are talking about on the given page: https://sap.github.io/fundamental-ngx/#/core/select
Please check my experience on this video: https://github.com/SAP/fundamental-ngx/assets/17043004/6f992f9f-f1aa-44e2-916d-c49b146b8d39
In order to be able to work on the issue, please provide information which sample you are using and exact steps how to reproduce and exact info what is your expectation for the announcement.
Thanks, Nikolay
@nikolay-kolarov In this video we can see only 4 item in dropdown list. To reproduce this issue we need more item in dropdown like in our case its min 15-20. so that scroll comes in to picture. Issue is only with long list. which item is starting not visible but comes later after scrolling down using keyboard arrow. I have asked Accessibility team also to share video which they recorded while testing this senario. If i get those video will upload here
@droshev Please use below Select Max Height case to reproduce this issue. In this case last item is Melon which doesn't appear in starting but comes after scrolling down. Please use keyboard arrow to move down. Screen reader shouldn't readout Melon
Hello @JyotiKumari1507,
To be honest this issue does not have any relation with the initially reported issue. It is also reproducible without screen reader.
@droshev - the last comments and the last discussed issue here: when the user uses the arrow keys to navigate in the picker with items, the scroll position is not adjusted and the focus goes out of the visible screen. Please check what is the issue causing this.
https://github.com/SAP/fundamental-ngx/assets/17043004/cbe2d129-86f5-44ac-a787-9c45a935be12
Best Regards, Nikolay
@nikolay-kolarov lets wait for recording by Accessibility team
Hello All,
Retested the issue and issue is resolved. Value count conveyed for list items. Evidence attached.
Regards, Meghana
Can you open a new ticket and creating a stackblitz with the issue?
Hi @droshev, issue is fixed as mentioned by @MeghanaVernekar.