E-mail List Archives
Re: Is VoiceOver more similar to NVDA or JAWS with respect to the accessibility tree?
From: Steve Green
Date: Jun 4, 2020 9:07AM
- Next message: Steve Green: "Re: Is VoiceOver more similar to NVDA or JAWS with respect to the accessibility tree?"
- Previous message: Birkir R. Gunnarsson: "Re: conveying expand/collapse state with details/summary elements"
- Next message in Thread: Steve Green: "Re: Is VoiceOver more similar to NVDA or JAWS with respect to the accessibility tree?"
- Previous message in Thread: John Hicks: "Re: Is VoiceOver more similar to NVDA or JAWS with respect to the accessibility tree?"
- View all messages in this Thread
It's not just Chrome - Firefox has similar issues. As I recall, you get no matches if you include "equals" signs or quotation marks in the search term, but there are other reasons too. Sometimes the tool can't find matches in <iframe> elements. Ironically, Internet Explorer performs better insofar as you can include "equals" signs or quotation marks in the search term.
I also recall that you get no matches if the search term includes a no-break space.
Steve
- Next message: Steve Green: "Re: Is VoiceOver more similar to NVDA or JAWS with respect to the accessibility tree?"
- Previous message: Birkir R. Gunnarsson: "Re: conveying expand/collapse state with details/summary elements"
- Next message in Thread: Steve Green: "Re: Is VoiceOver more similar to NVDA or JAWS with respect to the accessibility tree?"
- Previous message in Thread: John Hicks: "Re: Is VoiceOver more similar to NVDA or JAWS with respect to the accessibility tree?"
- View all messages in this Thread