locked Re: Updated Firefox to version 89, can no longer use w/NVDA
I found the setting in about:config that does what the old setting in advanced options used to do. it says something like accessibility.force.disabled. I set it to 1 from 0 and the result was a complete loss of access to the program. But this isn’t like what those reporting the problem have evidently described. I saw no menus, no dialogs, when I tabbed, nothing was spoken nor could I read anything. I heard no unknown nor any other speech. So my idea, while interesting, appears not to be related to the problem unless those with the problem report what I am reporting. If they have access to the interface of the program, dialogs, menus, then this appears not to be the problem. However, it might be useful for people who have the problem to look at accessibility settings in about:config if they can, it may well not be possible without sighted help, to see if accessibility.force.disabled is set to 0 or some other number. It should be 0.
I’ll explain how to have only accessibility settings displayed in about.config if people want to know.
I’ll add that since I use Firefox portable, I copied the program to another location, experimented with that copy, then deleted it and went back to using my unchanged copy of the program. I consider running firefox portable to be far preferable to running the installed version.
I'm not at all sure this has anything to do with the ;problem but Ron's
comments about accessibility blocking may have something to do with it. I
had initially said that you would have to have no access to the program for that
to be the case but I wonder if that is still true.
After seeing Ron's comments, I looked for the block accessibility setting that used to be in Firefox Advanced settings. there is no Advanced settings category in Firefox any longer, at least none I can find. There are also no accessibility settings in the settings dialog. I searched for accessibility in settings and got a no results message. I looked in about:config and found nothing that looked like the block accessibility setting. I wonder if it is there at all anymore.
However, according to a discussion on the Superuser site, accessibility is disabled unless a screen-reader is detected to make the browser faster. Could the problem be that for some people, the screen-reader isn't being detected or if it is, it isn't causing accessibility to turn on in the browser? I have no idea. But it is a question that may be relevant.
On 6/3/2021 12:41 AM, Ron Canazzi wrote: