Does anyone have any tips for making the PowerShell ISE more usable with a screen reader? I am using PS version 4 and Jaws 18. The main problem I have found with the ISE is that I can't find a way to review the results of my commands. If I run a command I can hear Jaws speaking the output, but if I then want to go back and review that output, I can't find it. The only way around this seems to be to pipe every command to a text file and then review the output there, which isn't ideal. Thanks, Caroline. This e-mail expresses the opinion of the author and is not necessarily the view of the Council. Please be aware that anything included in an e-mail may have to be disclosed under the Freedom of Information Act and cannot be regarded as confidential. This communication is intended for the addressee(s) only. Please notify the sender if received in error. All Email is monitored and recorded. Please think before you print- North Lincolnshire Council greening the workplace.
I am usually able to review Power Shell output when I switch to the JAWS
cursor. Then I can use my arrow keys to review the output. Up and Down
arrow moves by line, Left or Right Arrow by character, Control Left or
Right Arrow moves by word.
-----Original Message-----
From: Blind-sysadmins
[mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of
Caroline Ford via Blind-sysadmins
Sent: Friday, February 10, 2017 3:56 AM
To: blind-sysadmins@lists.hodgsonfamily.org
Cc: Caroline Ford
If you can install NVDA ... you might have better luck.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Mann
Sent: Friday, February 10, 2017 7:50 AM
To: Blind sysadmins list
If you can install NVDA ... you might have better luck.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Mann
Sent: Friday, February 10, 2017 7:50 AM
To: Blind sysadmins list
You can use the jaws cursor or the "speech history" feature of JAWS. This
feature is accessed by "JawsKey+SpaceBar" then press the "h" key. A
virtual buffer of all that has been spoken will appear.
Mitchell Green
Information Technology Facilitator
o | 402-614-3331 x226 c | 402-871-1063 f | 402-933-1616
mgreen@outlooknebraska.com
4125 S. 72nd Street | Omaha, NE 68127
NOTICE: The information contained in this e-mail transmission and any
attachment is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon, this information by persons or entities other
than the intended recipients is prohibited. If you have received this
communication in error, please contact the sender and destroy any copies
of this document.
-----Original Message-----
From: Blind-sysadmins
[mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of
Caroline Ford via Blind-sysadmins
Sent: Friday, February 10, 2017 2:56 AM
To: blind-sysadmins@lists.hodgsonfamily.org
Cc: Caroline Ford
Speech history does work although it is a little slow to refresh. Thank you for the suggestion. I can't see any text with the Jaws cursor though. As you and Ryan are able to, I wonder whether I have something configured incorrectly, but I'm not sure what that might be.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Mitchell Green
Sent: 10 February 2017 15:09
To: Blind sysadmins list
Subject: Re: [Blind-sysadmins] PowerShell ISE
You can use the jaws cursor or the "speech history" feature of JAWS. This
feature is accessed by "JawsKey+SpaceBar" then press the "h" key. A
virtual buffer of all that has been spoken will appear.
Mitchell Green
Information Technology Facilitator
o | 402-614-3331 x226 c | 402-871-1063 f | 402-933-1616
mgreen@outlooknebraska.com
4125 S. 72nd Street | Omaha, NE 68127
NOTICE: The information contained in this e-mail transmission and any
attachment is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon, this information by persons or entities other
than the intended recipients is prohibited. If you have received this
communication in error, please contact the sender and destroy any copies
of this document.
-----Original Message-----
From: Blind-sysadmins
[mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of
Caroline Ford via Blind-sysadmins
Sent: Friday, February 10, 2017 2:56 AM
To: blind-sysadmins@lists.hodgsonfamily.org
Cc: Caroline Ford
What version of windows are you using?
Have you tried to unload and reload JAWS? Sometimes this helps.
Mitchell Green
Information Technology Facilitator
o | 402-614-3331 x226 c | 402-871-1063 f | 402-933-1616
mgreen@outlooknebraska.com
4125 S. 72nd Street | Omaha, NE 68127
NOTICE: The information contained in this e-mail transmission and any
attachment is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon, this information by persons or entities other than
the intended recipients is prohibited. If you have received this
communication in error, please contact the sender and destroy any copies of
this document.
-----Original Message-----
From: Blind-sysadmins
[mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of
Caroline Ford via Blind-sysadmins
Sent: Friday, February 10, 2017 9:16 AM
To: Blind sysadmins list
I'm using Windows 7 SP1. I've tried several versions of Jaws, all with the same results. Even with NVDA I couldn't find any text when reviewing the screen, but when pressing Ctrl+R to move from the script pane to the console, NVDA says "The view provides a visual presentation of the text contained in the editor" which indicates that the text probably cannot be read. I can't find a setting which would alter this behaviour though.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Mitchell Green
Sent: 10 February 2017 23:46
To: Blind sysadmins list
Subject: Re: [Blind-sysadmins] PowerShell ISE
What version of windows are you using?
Have you tried to unload and reload JAWS? Sometimes this helps.
Mitchell Green
Information Technology Facilitator
o | 402-614-3331 x226 c | 402-871-1063 f | 402-933-1616
mgreen@outlooknebraska.com
4125 S. 72nd Street | Omaha, NE 68127
NOTICE: The information contained in this e-mail transmission and any
attachment is intended solely for the person or entity to which it is
addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon, this information by persons or entities other than
the intended recipients is prohibited. If you have received this
communication in error, please contact the sender and destroy any copies of
this document.
-----Original Message-----
From: Blind-sysadmins
[mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of
Caroline Ford via Blind-sysadmins
Sent: Friday, February 10, 2017 9:16 AM
To: Blind sysadmins list
Hello:
Our team reached out to the Powershell ISE team, and we have a response from them below. This being said, a few points of my own. We are working to address the accessibility in Powershell ISE, but for now, I really find it so inconvenient to use that I just use Notepad, save my code as a .PS1 file and manually run it at the prompt. Is it as nice as the ISE, no but it works. I found even tracking the cursor in the ISE to be an issue. The other thing to mention is I get why you're using Windows 7 SP1, a lot of organizations are still sticking with it for a variety of reasons. And I'm not by anymeans saying we have no plans for accessibility on Windows 7. However, Windows 10 is the future and where things are going, so all the cool accessibility fixes will be there going forward. That said, here's the response from the product team:
There are 2 approaches to work around this by having the user switch the window focus themselves before running the code. This is less convenient than simply pressing F5, but certainly works. The core issue is that using F5 will run the commands in the console pane, while the focus is maintained in the edit window (by design).
Approach 1 is to save the file being edited in the ISE as a PS1, then switch to the script window and run that script. This is consistent with the primary purpose of the ISE, which is editing a script file.
The sequence of keystrokes would be:
Ø In the ISE enter the code
Ø Ctrl-s saves the file as some name (say: c:\testing\testscript.ps1)
Ø Ctrl-d switches to the ISE's console pane. The user then types the name of the script from the PS> prompt, and should be able to review the output displayed.
Ø Ctrl-i switches back to the script pane / editing window.
(note that the s, d, and i above are not case sensitive).
Approach 2 is to copy everything from the script pane, switch to the console and run the commands. Sequence of keystrokes would be
Ø In the ISE enter the code
Ø Ctrl-a, Ctrl-c selects and copies everything in the script pane.
Ø Ctrl-d switches to the ISE's console pane
Ø Ctrl-v pastes the buffer into the console pane, but doesn't run it. User must hit Enter, and then the script runs
Ø Ctrl-i switches back to the script pane / editing window.
The difference & advantage to this approach is that the user can hit up-arrow to review each individual line.
Ryan
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Caroline Ford via Blind-sysadmins
Sent: Monday, February 13, 2017 6:49 AM
To: Blind sysadmins list
Ryan,
Thank you for your detailed response. Up until now I have also been writing my scripts in Notepad and running them from the command line, but I was hoping to be able to make use of the ISE to take advantage of auto-completion and intellisense. I will be moving to Windows 10 in the next three months or so, but have to soldier on with Windows 7 for now.
Following the details provided by the ISE team, I still am unable to review the output of my commands in the console pane. I have no trouble reviewing output from the usual command-line, but once I have loaded the ISE, the only thing which ever appears in the console pane is the window title.
I think I am going to have to write my code in the script pane, save it as a ps1 file and then run it from the command-line (not from the command pane within the ISE). This will at least enable me to take advantage of the ISE to some extent, but it won't help with debugging which is something else I was hoping to be able to use the ISE for.
Caroline.
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart via Blind-sysadmins
Sent: 13 February 2017 20:47
To: Blind sysadmins list
Cc: Ryan Shugart
Subject: Re: [Blind-sysadmins] PowerShell ISE
Hello:
Our team reached out to the Powershell ISE team, and we have a response from them below. This being said, a few points of my own. We are working to address the accessibility in Powershell ISE, but for now, I really find it so inconvenient to use that I just use Notepad, save my code as a .PS1 file and manually run it at the prompt. Is it as nice as the ISE, no but it works. I found even tracking the cursor in the ISE to be an issue. The other thing to mention is I get why you're using Windows 7 SP1, a lot of organizations are still sticking with it for a variety of reasons. And I'm not by anymeans saying we have no plans for accessibility on Windows 7. However, Windows 10 is the future and where things are going, so all the cool accessibility fixes will be there going forward. That said, here's the response from the product team:
There are 2 approaches to work around this by having the user switch the window focus themselves before running the code. This is less convenient than simply pressing F5, but certainly works. The core issue is that using F5 will run the commands in the console pane, while the focus is maintained in the edit window (by design).
Approach 1 is to save the file being edited in the ISE as a PS1, then switch to the script window and run that script. This is consistent with the primary purpose of the ISE, which is editing a script file.
The sequence of keystrokes would be:
Ø In the ISE enter the code
Ø Ctrl-s saves the file as some name (say: c:\testing\testscript.ps1)
Ø Ctrl-d switches to the ISE's console pane. The user then types the name of the script from the PS> prompt, and should be able to review the output displayed.
Ø Ctrl-i switches back to the script pane / editing window.
(note that the s, d, and i above are not case sensitive).
Approach 2 is to copy everything from the script pane, switch to the console and run the commands. Sequence of keystrokes would be
Ø In the ISE enter the code
Ø Ctrl-a, Ctrl-c selects and copies everything in the script pane.
Ø Ctrl-d switches to the ISE's console pane
Ø Ctrl-v pastes the buffer into the console pane, but doesn't run it. User must hit Enter, and then the script runs
Ø Ctrl-i switches back to the script pane / editing window.
The difference & advantage to this approach is that the user can hit up-arrow to review each individual line.
Ryan
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Caroline Ford via Blind-sysadmins
Sent: Monday, February 13, 2017 6:49 AM
To: Blind sysadmins list
Hello:
Our team reached out to the Powershell ISE team, and we have a response from them below. This being said, a few points of my own. We are working to address the accessibility in Powershell ISE, but for now, I really find it so inconvenient to use that I just use Notepad, save my code as a .PS1 file and manually run it at the prompt. Is it as nice as the ISE, no but it works. I found even tracking the cursor in the ISE to be an issue. The other thing to mention is I get why you're using Windows 7 SP1, a lot of organizations are still sticking with it for a variety of reasons. And I'm not by anymeans saying we have no plans for accessibility on Windows 7. However, Windows 10 is the future and where things are going, so all the cool accessibility fixes will be there going forward. That said, here's the response from the product team:
There are 2 approaches to work around this by having the user switch the window focus themselves before running the code. This is less convenient than simply pressing F5, but certainly works. The core issue is that using F5 will run the commands in the console pane, while the focus is maintained in the edit window (by design).
Approach 1 is to save the file being edited in the ISE as a PS1, then switch to the script window and run that script. This is consistent with the primary purpose of the ISE, which is editing a script file.
The sequence of keystrokes would be:
Ø In the ISE enter the code
Ø Ctrl-s saves the file as some name (say: c:\testing\testscript.ps1)
Ø Ctrl-d switches to the ISE's console pane. The user then types the name of the script from the PS> prompt, and should be able to review the output displayed.
Ø Ctrl-i switches back to the script pane / editing window.
(note that the s, d, and i above are not case sensitive).
Approach 2 is to copy everything from the script pane, switch to the console and run the commands. Sequence of keystrokes would be
Ø In the ISE enter the code
Ø Ctrl-a, Ctrl-c selects and copies everything in the script pane.
Ø Ctrl-d switches to the ISE's console pane
Ø Ctrl-v pastes the buffer into the console pane, but doesn't run it. User must hit Enter, and then the script runs
Ø Ctrl-i switches back to the script pane / editing window.
The difference & advantage to this approach is that the user can hit up-arrow to review each individual line.
Ryan
-----Original Message-----
From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Caroline Ford via Blind-sysadmins
Sent: Monday, February 13, 2017 6:49 AM
To: Blind sysadmins list
participants (5)
-
Caroline Ford -
Katherine Moss -
Mitchell Green -
Ryan Mann -
Ryan Shugart