RE: Electron accessibility

Léonie wrote:

> I ask because I'm trying (and failing) to find a screen reader accessible code editor. 
> Atom and VS Code are both Electron based, and neither seems usefully accessible. 
> Much the same seems to be true of Slack, 
> another Electron based tool I'd very much like to be usable with a screen reader.

Léonie, I feell the pain. This kind of searching is so time consuming and can be very frustrating. I'd love to have an editor where more of the advanced features are usable with a screen reader.

I still use Eclipse. The basics are quite accessible. I really like how you can set up hotkeys to do just about anything. It's outline view of code is super helpful. Although, with html and js, not quite as useful as with other languages like java where I used to use the outline to move blocks of code around. But, there are similarly powerful selection features inside the editor itself.

JAWS works very well. I have only minor, light-weight scriptping for keys like reading the currunt line/column number. One annoyance  ... In JAWS enhanced edit mode, JAWS reads indentation but only the visible text so does not  completely read long lines. In JAWS standard edit mode, JAWS reads the entire line but not indentation.

The biggest downside to Eclipse is that it is rather heavy. It is an IDE. It takes a while to load. And, you can't just load a file from the file system into the editor. You have to open the Eclipse platform to do any work. So, it is better for projects. It is not so great for quick experimentation with random snippets of code.

Also, the plugin for editorconfig files doesn't seem to work for html and js.

For fast light-weight stuff, I sometimes use Notepad++, but it has too many accessibility issues to use extensively. For example, I often have to re-read lines because JAWS can't accurately track the cursor. You press down arrow, and it may read the line the cursor just left instead of the line it moved to.

I would love to have some good alternatives.

Matt

-----Original Message-----
From: Léonie Watson [mailto:tink@tink.uk] 
Sent: Friday, January 19, 2018 3:08 PM
To: Markku Hakkinen <mhakkinen@acm.org>; Sean Murphy (seanmmur) <seanmmur@cisco.com>
Cc: w3c-wai-ig@w3.org
Subject: Re: Electron accessibility

On 15/01/2018 01:42, Markku Hakkinen wrote:
> Electron is a wrapper around the Chrome (Chromium) browser.  The 
> accessibility support native to the version of Chromium used to build 
> Electron is what is exposed.   Cautionary note is that Electron 
> releases typically lag several releases behind the current Chrome 
> release, meaning bugs fixed in newer releases of Chrome will not be 
> present in the “current” Electron release.

It seems from what you've said, that Electron can be accessible - with the caveat that there may be some lag before issues are resolved there. 
Does that mean Electron in and of itself is capable of a reasonable degree of accessibility?

I ask because I'm trying (and failing) to find a screen reader accessible code editor. Atom and VS Code are both Electron based, and neither seems usefully accessible. Much the same seems to be true of Slack, another Electron based tool I'd very much like to be usable with a screen reader.

As an aside, I know VS Code has an accessibility mode, but when it's enabled you lose basic features like word wrapping and line numbering, and I can't write code without those two basic features!

Léonie.




> 
> Mark
> 
> On Sun, Jan 14, 2018 at 7:13 PM Sean Murphy (seanmmur) 
> <seanmmur@cisco.com <mailto:seanmmur@cisco.com>> wrote:
> 
>     All,____
> 
>     __ __
> 
>     https://electronjs.org/ ____
> 
>     __ __
> 
>     I am starting to see more and more applications built using this
>     framework. Anyone know if any work has been do for accessibility? 
> ____
> 
>     __ __
> 
>     
> https://www.cisco.com/c/dam/m/en_us/signaturetool/images/banners/stand
> ard/08_standard_graphic.png____
> 
>      
> 
>     *Sean Murphy*____
> 
>     ENGINEER.CUSTOMER SUPPORT____
> 
>     seanmmur@cisco.com <mailto:seanmmur@cisco.com>____
> 
>     Tel: *+61 2 8446 7751*____
> 
>     ____
> 
>     __ __
> 
>     ____
> 
>     ____
> 
>      
>     <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065%0D+Australia&entry=gmail&source=g>
>     <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065%0D+Australia&entry=gmail&source=g>
>     
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065
> %0D+Australia&entry=gmail&source=g>
> 
>     Cisco Systems, Inc.____
> 
>     The Forum 201 Pacific Highway
>     
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065
> %0D+Australia&entry=gmail&source=g>____
> 
>     ST LEONARDS
>     
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065
> %0D+Australia&entry=gmail&source=g>____
> 
>     2065
>     
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065
> %0D+Australia&entry=gmail&source=g>____
> 
>     Australia
>     
> <https://maps.google.com/?q=201+Pacific+Highway%0D+ST+LEONARDS%0D+2065
> %0D+Australia&entry=gmail&source=g>____
> 
>     cisco.com <http://cisco.com>____
> 
>     http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif____
> 
>       
> 
>     Think before you print.____
> 
>     This email may contain confidential and privileged material for the
>     sole use of the intended recipient. Any review, use, distribution or
>     disclosure by others is strictly prohibited. If you are not the
>     intended recipient (or authorized to receive for the recipient),
>     please contact the sender by reply email and delete all copies of
>     this message.____
> 
>     Please click here
>     <http://www.cisco.com/c/en/us/about/legal/terms-sale-software-license-agreement/company-registration-information.html>
>     for Company Registration Information.____
> 
>      
> 
>     __ __
> 
>     __ __
> 
> --
> Sent from iPad

--
@LeonieWatson @tink@toot.cafe Carpe diem

Received on Monday, 22 January 2018 16:20:56 UTC