E-mail List Archives
Re: [EXTERNAL]Why does NVDA concatenate React tabs into a single element?
From: Mark Magennis
Date: May 19, 2020 12:50PM
- Next message: Steve Green: "Re: [EXTERNAL]Why does NVDA concatenate React tabs into a single element?"
- Previous message: joe@a11yeval.com: "Re: Tab panels not reading on Android"
- Next message in Thread: Steve Green: "Re: [EXTERNAL]Why does NVDA concatenate React tabs into a single element?"
- Previous message in Thread: Murphy, Sean: "Re: Why does NVDA concatenate React tabs into a single element?"
- View all messages in this Thread
So I guess what you're all saying is, this is the way NVDA works with this CSS and users can cope with it and get around it? It seems avoidable though and I do think it would be preferable if this didn't happen. I'll talk to my devs and see if they can use alternative CSS.
Thanks guys.
MArk
Mark Magennis
Skillsoft | mobile: +353 87 60 60 162
Accessibility Specialist
- Next message: Steve Green: "Re: [EXTERNAL]Why does NVDA concatenate React tabs into a single element?"
- Previous message: joe@a11yeval.com: "Re: Tab panels not reading on Android"
- Next message in Thread: Steve Green: "Re: [EXTERNAL]Why does NVDA concatenate React tabs into a single element?"
- Previous message in Thread: Murphy, Sean: "Re: Why does NVDA concatenate React tabs into a single element?"
- View all messages in this Thread