I was going to write a lot of these suggestions but this Email lists them perfectly. I'd expand on item 17 just a little. Powershell presents things in columns quite a bit. OR maybe that's just the way I tend to output my commands. I would really like to be able to move around these columns with standard table reading commands. But the main thing about the console is: Keep it simple. There's usually a lot of text flying around in a console window. One of the reasons I like to use the CLI still is it's flat. There's no messing around. The text is just there and hopefully it's accessible. This is why I now use secure CRT for everything. -----Original Message----- From: mhysnm1964@gmail.com <mhysnm1964@gmail.com> Sent: Wednesday 17 July 2019 02:23 To: 'Blind sysadmins list' <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Re: the ultimate terminal experience Ryan, This is good to see the reach-out from a vendor before release of a updated or new feature. My wish list and I have not reviewed the other responses. My responses are based for a CLI (Command Line Interface) terminal with a screen reader. The comments are really quick notes. 1. Correct cursor tracking with all screen readers. I can navigate the command line by char, word, beginning and end of line, delete from cursor to end of line, etc. The screen reader announces all this information correctly. Speakup on Linux does this brillently. Thus if in Emacs for example. A shortcut command is used to open a search edit area. Then the cursor moves to this edit area and reads out the labels (name) or prompt, plus follows the cursor. 2. Ability of scrolling back the buffer for text which has scrolled off the page. This should be a shortcut key which places the terminal in a history mode. Then the screen reader can use the normal navigation commands like moving by character (left/right arrows), by word (ctrl left and ctrl right arrow), line, etc. selecting and Copying text out of the history is a must. The current information on the screen must be able to reviewed by the screen reader by the methods available. Under the Mac and Linux, the screen reader does this without the need of a special history buffer. But I cannot think of a generic way to do this under windows due to multiple screen readers that are available. 3. Being able to correctly scroll forward and back the command history. Being able to perform reverse search as well. Similar to how Linux works. 4. If a text menu UI appears as you are using another OS ;via ssh or telnet. Being able to correctly follow the focus indicator. Reading out the content when the page is updated. Filtering out decorative characters used in such a menu UI construct. This touches upon VI, Emacs and similar text console apps. 5. Full vt100 and higher support. The issue here with screen readers is when new information is received such as the colour changes from phrase 1 to phrase 2. Most screen readers I have used read both phrases. This links back to the prior point. 6. Titles of tabs which work with screen readers. So you can jump between the tabs and know which terminal session is open. Shortcut keys must be available to support quick jumping. 7. Status bar, being able to move focus to the status bar and interrogate the information. Also the screen reader must be able to detect the status bar and read out the information by using screen reader commands. The status bar should not interfere with normal behaviour. 8. Report of system errors related to the terminal session. Such as the session has disconnected. 9 Support of custom colours for users with low vision. 10 being able to paste, copy and cut information from the command line. 11. All the UI's which are available within the terminal app are accessible. Menus, dialogs, etc.This is outside the CLI console screen. 12. supporting magnification technology. 13. If the size of the window is changed, does not impact the screen reader in any fashion. 14. Using Windows CLI, supporting the option of opening files using the default app would be nice. 15. Launching web pages from the CLI. 16. Being able to open sub-shells like Bash when you are within the windows CLI. This might be outside your scope. 17. Handling multiple column text. That is, if you are in a router like Cisco's iOS-Xe. Some commands list the information in columns. Being able to navigate this effectively would be great. Currently you have to remember the columns and headings. 18. Stopping duplicate text being spoken when information is updated. 19. Supporting Linux Cursers in Windows CLI. So when I write python or other scripting languages. I can use this library. Now I am not sure if this is a limitation of Python or the CLI. 20. Handling full screen text based apps such as VI Emacs is the area of challenge as I see it. As screen readers come in all sizes. How is this done is the challenge area as some screen readers might not have the capability to handle multiple focuses, track text updates, etc. As I understand terminal programs that uses vt100 or other similar terminal protocols. There are codes which are sent with the text to perform specific actions on the screen. Such as changing colours, moving cursor, etc. If the terminal could understand these codes and convert them into a meaningful way to a screen reader if is important. This would be great. Such as the current colour, cursor location, reading out a panel of text, etc. -----Original Message----- From: Billy Irwin <billy.irwin@outlook.com> Sent: Wednesday, 17 July 2019 8:49 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Re: the ultimate terminal experience Ryan, I want to sincerely thank you and your team for the work you are doing and for reaching out to all of us! Best, Billy -----Original Message----- From: Ryan Shugart via Blind-sysadmins <blind-sysadmins@lists.hodgsonfamily.org> Sent: Tuesday, July 16, 2019 6:28 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Cc: Ryan Shugart <ryshugar@microsoft.com> Subject: [Blind-sysadmins] Re: the ultimate terminal experience Hi: Good question. Technically I guess I'm asking both questions as the new Windows Terminal will be used in both rolls. It will serve as a replacement for the conhost process in Windows which handled command prompt, powershell, Windows Subsystem for Linux, and any console app window. So, at some future point when you bring up a cmd prompt or a bash shell in Windows, instead of the existing console window opening, the new Windows Terminal application will open and manage the session. Since Windows now also includes the OpenSSH client, and you can use Powershell remoting to bring up remote command prompts, those situations will be covered here as well. Thanks. Ryan -----Original Message----- From: philrigby62@gmail.com <philrigby62@gmail.com> Sent: Tuesday, July 16, 2019 2:05 PM To: 'Blind sysadmins list' <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Re: the ultimate terminal experience Hi Ryan, Just trying to clarify what you are asking about here since terminology is often interpreted in different ways by different people. Do you mean the command line on a Windows machine here or do you mean accessing remote machine command lines or something else? I'm from the Linux/Unix world so I'm a bit dumb when it comes to Windows terminology. Cheers, Phil. -----Original Message----- From: Ryan Shugart via Blind-sysadmins <blind-sysadmins@lists.hodgsonfamily.org> Sent: 16 July 2019 19:49 To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Cc: Ryan Shugart <ryshugar@microsoft.com> Subject: [Blind-sysadmins] the ultimate terminal experience Hello everyone: I wanted to throw a question out to everyone. As we are working with the new Windows Terminal product to insure it is accessible and works well with assistive technologies, I wanted to reach out to this list and find out what would be the ideal terminal experience for you? What would you be looking for and want in a new terminal program from an accessibility standpoint, something that would set it aside from the rest and really make it an enjoyable experience to use, not just something you can use? I'm definitely going to bring the feedback to the Windows Terminal team, and while I can't guarantee it will all be acted on, it will certainly help set a direction and way to move forward. Thanks much. Ryan Ryan Shugart Program Manager II, Cloud+AI Accessibility Microsoft Corporation 425-705-1262 _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org _______________________________________________ Blind-sysadmins mailing list -- blind-sysadmins@lists.hodgsonfamily.org To unsubscribe send an email to blind-sysadmins-leave@lists.hodgsonfamily.org