-
Notifications
You must be signed in to change notification settings - Fork 315
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
{Linked:Bug3432717}[BUG] Voiceover does not announce the Person component if present in List component #2120
Comments
Hello saahilchawande123, thank you for opening an issue with us! I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌 |
Thank for raising this @saahilchawande123 do you have a code reproduction available that we can use to start investigating this issue? |
I don't have a stand-alone code representation but this issue also happens when the Person component is rendered in a standard html ul list. Do let me know if it is still unclear and the reproduction is still needed. Thanks. |
I understood the description, I asked if there was an available reproduction to save time on building one. |
Alright, is there a canvas link that I can create and share? Because it is very difficult to write the code on mobile and copy/pasting is not working. |
Describe the bug
This bug is happening when the component from Microsoft Graph Toolkit is used inside a list item of the and component from React Northstar (Link to doc: https://fluentsite.z22.web.core.windows.net/0.66.2/components/list/definition)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Voiceover should read the contents displayed by the component.
Screenshots
(Video Recording)
https://user-images.githubusercontent.com/116312427/223588456-6b46b44a-13ff-401b-b6dc-d5c725029c9d.mp4
Code Snippet causing the issue:

Environment (please complete the following information):
Additional context
I also tried to check if this issue is caused due to the or component from react-northstar by changing the component to component and the Voiceover was announcing the contents perfectly fine (meaning voiceover was reading the contents and not "menu item").
The text was updated successfully, but these errors were encountered: