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

[SF] [A11y] [ui5-avatar] Avatar is announced as "clickable graphic" even when not interactive #3683

Closed
1 of 4 tasks
Neeeko opened this issue Aug 17, 2021 · 3 comments · Fixed by #3742
Closed
1 of 4 tasks
Assignees
Labels

Comments

@Neeeko
Copy link

Neeeko commented Aug 17, 2021

Bug Description

The ui5-avatar component is announced by screen readers as "clickable graphic" even when the mode is not interactive.

Screenshot 2021-08-17 at 14 44 47

Expected Behavior

When the ui5-avatar is not interactive (focusable/clickable), it shouldn't be announced as "clickable". Only the accessible name should be announced by screen readers.

Isolated Example

https://codesandbox.io/s/ui5-webcomponents-forked-yftf5?file=/index.html

Context

  • UI5 Web Components version: 0.31.9
  • OS/Platform: Windows 10 (using NVDA as screen reader)
  • Browser: Google Chrome
  • Affected component: ui5-avatar

Priority

  • Low
  • Medium
  • High
  • Very High

Stakeholder Info (if applicable)

  • Organization: SuccessFactors
@unazko unazko added bug This issue is a bug in the code Medium Prio TOPIC P labels Aug 17, 2021
@unazko
Copy link
Contributor

unazko commented Aug 17, 2021

Hello @SAP/ui5-webcomponents-topic-p,

The issue is reproducible on all available ui5-webcomponents versions via the provided steps and NVDA screen reader.
Also the issue isn't reproducible by using jaws 2019, jaws 2021 or Windows Narrator as they announce:
"My Avatar graphic".

Not sure, which screen readers are fully supported.

Best Regards,
Boyan Rakilovski

@Neeeko
Copy link
Author

Neeeko commented Sep 9, 2021

Hi,
Thanks for addressing this issue!
If possible, we would appreciate if this fix could be merged and deployed as soon as possible as we have our SF code complete next week.
Thanks!

@fifoosid
Copy link
Contributor

fifoosid commented Sep 9, 2021

Hi @Neeeko

The fix will be available in the next release of the 0.31 branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Completed
6 participants