E-mail List Archives
Re: Working around flaky browser accessibility tree
From: Glen Walker
Date: Apr 6, 2018 9:45AM
- Next message: Glen Walker: "Re: 4.1.1 Parsing > nested elements"
- Previous message: Steve Faulkner: "Re: Working around flaky browser accessibility tree"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Working around flaky browser accessibility tree"
- Previous message in Thread: Steve Faulkner: "Re: Working around flaky browser accessibility tree"
- View all messages in this Thread
In this particular case, it sounds like you're ok, but it's a good general question. If my site works well with browser A and screen reader X, do I have to worry about browser B or screen reader Y? I think a common practice is for companies to have an accessibility statement that says something like, "For the best user experience, we recommend using jaws with ie or nvda with firefox", with possible details about browser or AT version numbers. VO is usually included too. I don't see chrome mentioned very often in those statements, fwiw.
- Next message: Glen Walker: "Re: 4.1.1 Parsing > nested elements"
- Previous message: Steve Faulkner: "Re: Working around flaky browser accessibility tree"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Working around flaky browser accessibility tree"
- Previous message in Thread: Steve Faulkner: "Re: Working around flaky browser accessibility tree"
- View all messages in this Thread