Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Accessibility: ACC-264.1] Icon: UI type not conveyed and info read twice #12603

Open
divyamalhotra488 opened this issue Oct 18, 2024 · 1 comment
Labels
accessibility use this label for any issue or enhancement related to screenreader/keyboard/etc support

Comments

@divyamalhotra488
Copy link

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 and all info must be conveyed only once 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.

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

If this is a bug, please provide steps for reproducing it; the exact components you are using;

Component used: Icon
On accessing the ‘More info’ icon within the section ‘Communication’ the UI type ‘Button is not conveyed and information within the icon is conveyed twice to the user.
image

Please provide relevant source code (if applicable).

Please provide stackblitz example(s).

You can try ngx examples, issue is reproducible there.

In case this is Accessibility related topic, did you consult with an accessibility expert? If not, please do so and share their recommendations.

Yes, issue is raised by an accessibility expert.

Did you check the documentation and the API?

Yes

Did you search for similar issues?

Yes

Is there anything else we should know?

IMPORTANT: Please refrain from providing links or screenshots of SAP's internal information, as this project is open-source, and its contents are accessible to anyone.

@droshev
Copy link
Contributor

droshev commented Oct 18, 2024

@divyamalhotra488 the screenshots shows an application. Can you create a stackblitz example so we can provide you with the right support?

@droshev droshev added the accessibility use this label for any issue or enhancement related to screenreader/keyboard/etc support label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility use this label for any issue or enhancement related to screenreader/keyboard/etc support
Projects
None yet
Development

No branches or pull requests

2 participants