It is much easier to be critical than to be correct. Sometimes doing diagnostics surrounding NVDA issues requires things that are not a part of NVDA at all. When that's the case, have a look at the article noted in the topic title, linked here, for some alternatives you could use to test with a non-Chromium-based browser: What are the best browsers not based on Chromium? Then again, sometimes it's not, as the issue sticks with any browser that has Chromium as its base. Sometimes, it's enough to try another browser that uses the Chromium code base because it's possible that the customizations made by the company that produces your favorite are the problem. For any issue you have with NVDA when it comes to the web, the first thing you should do in an attempt to rule NVDA itself in or out as the root cause is to try doing exactly what you're doing with a different web browser. And because Chromium has come to dominate the market as the code base for all of the most popular browsers, including the king of the hill, Chrome, it's important to know the alternatives besides Firefox that exist that you can use for testing. First, I know that this topic is not NVDA-centric, but as recent topics have shown, figuring out what the root cause of an issue when using NVDA with a web browser is a non-trivial task.
0 kommentar(er)
