Open JyotiKumari1507 opened 9 months ago
@JyotiKumari1507 Can you provide more information about use-case, scenario, steps, whether you tried using the API for achieving the target?
@droshev Screen reader isn't able to read all element of list while testing by Accessibility team. Its read only few 7-8 row of list which is visible in screen other item which comes after scrolling is missed out. We can have more discussion in next call
@JyotiKumari1507 we need the input written so it will be easier to process
@droshev Attaching screen reader screenshot for more details:
Most of the fields are not filled.
@droshev please let us know what fields are pending to fill from our side
@JyotiKumari1507 did you set all aria attributes needed? If so, can you create a small stackblitz example demonstrating that you cannot set this on the application side?
@divyamalhotra488 please check on this from our side and share stackblitz example
@JyotiKumari1507 any update?
Hi @droshev, Please find the stackblitz example here: https://stackblitz.com/edit/eclhkf?file=package.json
Is this a bug, enhancement, or feature request?
Bug
Describe your proposal.
Component having issue: https://sap.github.io/fundamental-ngx/#/core/list UI element type for all the list item available is not communicated to the user by screen reader
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 list item and try to read its by screen reader. All items of list are not readable by screen reader
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?