Screen readers aren't an integral part of the browser: they simply 'sit' on top of it, announcing the available contents to the user. Otherwise just skip the rest of this page. If you are interested to find out more about the reasoning behind this, continue reading. Notice: an exception from this rule is valid in closed environments, where only specific browsers or screen readers are available.
We have had good experiences with taking the following pragmatic approach, namely aiming at the most widely used combinations (newest stable versions): Mobile screen readers It is impossible to develop and test for dozens of possible combinations of browsers and screen readers. Adding screen readers to the mixture does not make things easier: a long list of screen readers can potentially be combined with another long list of browsers, each combination possibly having its own characteristics.
Other requirements may only apply in closed environments that are only open to a specific, deterministic group of users. To reach as many users as possible, it's a pragmatic approach to support the most widely used combinations of browsers and screen readers. Relevant combinations of screen readers and browsers
