Screen Reader & BrowserĪt my work place we follow testing on Firefox with NVDA screen reader & if we encounter any bugs related to either screen reader or the browser, we immediately raise the bugs with the vendor.
During my day to day accessibility testing I use NVDA with Firefox & sometimes I also use NVDA with Chrome to see if any ARIA or HTML5 attribute is not being supported by the browser or the screen reader. I personally prefer JAWS with Internet Explorer & JAWS with Chrome as the new version of Firefox doesn’t work with JAWS yet. BrowserĪccording to WebAIM Screen reader survey we can clearly see from the below table that JAWS works great on Internet Explorer followed by NVDA with Firefox. When it comes to IOS & OSx Safari is the most popular browser & on Android Chrome & Firefox both hold a good position. Definitely assistive technology users prefer Firefox over Chrome for their day to day activities. But according to WebAIM screen reader survey7 conducted in 2017, Firefox stands first followed by internet Explorer & in 3rd place is Chrome. These stats are true for both desktop & mobile. Popular BrowsersĪccording to Wikipedia, chrome holds the majority share for the browser market followed by Safari.
Testing with every screen reader on every browser is not feasible if not impossible. Whenever I say that I make web & mobile Apps accessible for the disability groups, the first question some of the educated developers who understand accessibility ask me is, what browsers you test your APP’s on & which screen readers do you use? This is a very interesting question because, there are a wide variety of browsers & screen readers that are available in the market.
0 kommentar(er)
