Open JyotiKumari1507 opened 5 months ago
@JyotiKumari1507 Can you provide more context, specific examples, and what your expectation would be?
@droshev While testing Accessibility found that Screen reader isn't able to find type of component being used. Ex: If i use tiles with header 'Key Management' then Screen Reader is only able to recognise it as 'Key Management' . As per accessibility team Screen reader should able to read its UI type as 'Tiles' also. We can have more discussion about this 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 share stackblitz example
@JyotiKumari1507 any update?
Hi @droshev, please find stackblitz example: https://stackblitz.com/edit/afrcak?file=src%2Fapp%2Fclickable-example.component.html
Is this a bug, enhancement, or feature request?
Bug
Describe your proposal.
UI elements type for all the UIs should be communicated to the user. Providing all the information about the UI on all user interface components enables compatibility with assistive technology, such as screen readers, screen magnifiers, and speech recognition software, used by people with disabilities. UI created by NGX core and Platform, Not able to read its UI type like its Tiles.
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 easily can check NGX core and platform component.
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?