On Thu, Apr 2, 2020 at 12:24 AM, Shaun Everiss wrote:

just use the stable version like I do.

Or, if you decide you want to be on a beta channel, hold up your end of the bargain:  report bugs.

While it's fine to try out beta software and ditch it if it doesn't work (yet), if something as critical as what has been described here occurs, it's up to you (any you) to file a bug report about it.  Many bugs these days for pre-release software aren't found by in-house testing groups, but are found by the huge numbers of people who signed up to be on any one of a number of pre-release channels for a given piece of software.  A good example of where there are multiple pre-release channels for a piece of software is the new Edge, that has three:  Canary (updated nightly), Dev (updated weeekly), and Beta (updated every six weeks).

If folks using screen readers aren't willing to report accessibility issues when they are using beta software, then who do you think should be?  You are far more likely to run into those issues, and instantly recognize them, than any sighted developer (or end user) is.  For heaven's sake, take the initiative to identify accessibility issues to development teams when you find them, using the appropriate channel to do that.  And if you don't now what that is, ask, or even better, try a web search on "bug report {insert program here}," and then ask if you don't find a useful result in the first 10 results.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna