Re: [orca-list] VSCode now is using electron 7

[Andy Borka <sonfire11 gmail com>]

Hi,

Even though the editors work, it is very slow, sometimes fails to let me stop speech when I want, and has major areas of accessibility problems. At this point, the terminal is a large problem. The explorer section is OK, but it is slow and not intuitive. Otherwise, the editor itself is nice because it is the only 'accessible' editor that gives accessible autocomplete.

On Fri, Feb 7, 2020 at 3:29 PM José Vilmar Estácio de Souza <vilmar informal com br> wrote:

In general I download from the following link:


https://code.visualstudio.com/docs/?dv=linux64&build=insiders


On 2/7/20 4:59 PM, Nolan Darilek wrote:
> Google for vscode insiders, download the latest build. I get the
> .tar.gz packages which just untar into a directory, but feel free to
> grab distro packages if you like.
>
>
> Be sure to use the --force-renderer-accessibility flag. I wrote a
> script, which I'll include below, that does this for you. It's pretty
> simple but it helps. Edit accordingly, of course.
>
>
> VSCode has good online documentation. I found this in particular
> helpful when I got started under Windows a while back:
>
>
> https://code.visualstudio.com/docs/getstarted/userinterface
>
>
> The command pallet is useful. It's kind of like Emacs' command buffer,
> or whatever the area is called where you can manually enter commands.
> Access it via Ctrl-p or F1. This lists all commands, bound and
> unbound, with their keyboard shortcuts and an autocomplete search. I
> think there are other menus listing keyboard shortcuts but I don't
> know them off-hand.
>
>
> You'll want to go into user settings and enable editor accessibility,
> since screen reader detection doesn't pick up Orca yet. I won't give
> detailed instructions because you requested basic, and I'm too lazy to
> do the legwork. But essentially you want to press Ctrl-, to access
> preferences, click the User button to be sure you're editing global
> user preferences, then tab around/navigate through the tree until you
> find accessibility settings. I think it may be in the common settings
> group, and searching may also work. Switch it from auto/autodetect to on.
>
>
> Hope that helps. Here's my shell script, in ~/bin/code-insiders:
>
>
> #!/bin/sh
>
> exec ~/opt/VSCode-linux-x64/code-insiders
> --force-renderer-accessibility $@
>
> On 2/7/20 1:52 PM, John G Heim via orca-list wrote:
>> Can I get some basic instructions on how to try this?
>>
>>
>>
>>
>> On 2/7/20 7:13 AM, José Vilmar Estácio de Souza wrote:
>>> Hi all.
>>>
>>> Electron 7 is back in the latest versions of code-insiders.
>>>
>>>
>>> This allows for reasonable accessibility in VSCode, with a tendency
>>> to improve.
>>>
>>> Thanks.
>>>
>>> _______________________________________________
>>> orca-list mailing list
>>> orca-list gnome org
>>> https://mail.gnome.org/mailman/listinfo/orca-list
>>> Orca wiki: https://wiki.gnome.org/Projects/Orca
>>> Orca documentation: https://help.gnome.org/users/orca/stable/
>>> GNOME Universal Access guide:
>>> https://help.gnome.org/users/gnome-help/stable/a11y.html
>> _______________________________________________
>> orca-list mailing list
>> orca-list gnome org
>> https://mail.gnome.org/mailman/listinfo/orca-list
>> Orca wiki: https://wiki.gnome.org/Projects/Orca
>> Orca documentation: https://help.gnome.org/users/orca/stable/
>> GNOME Universal Access guide:
>> https://help.gnome.org/users/gnome-help/stable/a11y.html
_______________________________________________
orca-list mailing list
orca-list gnome org
https://mail.gnome.org/mailman/listinfo/orca-list
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html