Well I am mostly going to use it for Python and React in _javascript_.
On 27/03/21 3:57 am, Jason White via orca-list wrote:
A further limitation is that unless you insert hard line breaks, an entire paragraph of text is treated as a single logical line, and word-wrap is turned off whenever a screen reader is detected. This is a known bug apparently related to their using a textarea element to represent the editor to the screen reader.
VSCode may not be the right choice if you need to edit LaTeX, HTML, Markdown, or other document formats. There is an extension available that can automatically insert hard line breaks as you write a paragraph (similar to fill-mode in Emacs), but I haven't tried it. As I mostly edit document-based formats, I prefer Emacs, which doesn't have the above issue.
On 26/3/21 3:09 am, José Vilmar Estácio de Souza wrote:
The editor accessibility message should only appear when you edit a file for the first time. The rest of the interface is accessible by default.
Another point is that depending on the language to be used in your project, you will need to install some extensions. Generally VSCode usually suggests installing some extensions based on the type of file opened.
On 3/26/21 2:51 AM, Krishnakant Mane wrote:
On 25/03/21 3:54 pm, José Vilmar Estácio de Souza wrote:
It is not necessary to use any parameter to activate accessibility in VSCode.When accessing the editor for the first time, you will be informed that it is not accessible together with some instructions on how to activate accessibility in the editor.I am surprised that I did not hear any such thing.
Almost everything I saw was accessible.
Has there been any recent change that makes it accessible by default?
I am using Ubuntu 20.04
Orca 3.38.2 with latest package of VSCode installed from the apt repository of Microsoft.
Another question, does code navigation and auto complete work well with Orca?
Should I do some specific thing to get it working?
There is also a channel on the gitter where you can ask questions and report problems.
On 3/25/21 6:53 AM, Krishnakant Mane via orca-list wrote:
Thanks a tun for this information.
I guess I have to set some parameter to start chromium with accessibility to work with Orca.
So is there something similar I will have to do with VScode?
Can any one give me all the exact required steps?
On 25/03/21 1:04 pm, Vojtěch Polášek via orca-list wrote:
Hello,
I find Visual studio Code (the new project based on Electron) very accessible and I use it for everyday programming.
If you have latest version of Orca which can handle apps such as Chromium, you probably don't need anything extra.
Just note that the app behaves a bit like web app, so focus mode and browse mode are used. Sometimes, it happens that it switches to browse mode and you think taht you are editing a text but in fact you are not... but this happened to me only few times and with the Insiders version of Visual studio.
I remember you have to enable accessibility in the app but I don't remember the steps, you can Google for it.
Vojta
Dne 25. 03. 21 v 6:42 Krishnakant Mane via orca-list napsal(a):
I wish to try out visual studio for a specific project.
How accessible is it with Orca?
What will I have to do to make it work so?
--
Regards,
Krishnakant Mane,
Project Founder and Leader,
GNUKhata
(Opensource Accounting, Billing and Inventory Management Software)
_______________________________________________ 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--
Regards,
Krishnakant Mane,
Project Founder and Leader,
GNUKhata
(Opensource Accounting, Billing and Inventory Management Software)
_______________________________________________ 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
--
Regards,
Krishnakant Mane,
Project Founder and Leader,
GNUKhata
(Opensource Accounting, Billing and Inventory Management Software)
_______________________________________________ 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--
Regards,
Krishnakant Mane,
Project Founder and Leader,
GNUKhata
(Opensource Accounting, Billing and Inventory Management Software)
_______________________________________________ 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